flarum-mcp (ReverserID/flarum-mcp) is an MCP server listed on the M8ven Trust Index. It scores 60 out of 100, grade C. It declares 20 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Caution
60/100

flarum-mcp

MCP server for Flarum forums that enables searching, reading, and posting discussions through Flarum's REST API.

→ ReverserID/flarum-mcp· listed on glama

Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

ReverserID

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

Glamanot scored here

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
⚠️
Known vulnerabilities in dependencies: 3 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
✅
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 4 credentials: FLARUM_API_TOKEN, FLARUM_PASSWORD, REVERSER_API_TOKEN, REVERSER_PASSWORD
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// tools this server exposes20 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

list_tags
search_discussions

Full-text search discussions on the forum. Returns matching titles with id, author, and tags.

recent_discussions

List the most recently active discussions on the forum.

discussions_by_tag

List discussions filed under a given tag (category), by tag slug — e.g. 'malware-analysis'.

get_discussion

Fetch a discussion by id, including its posts rendered as plain text.

create_discussion
reply_to_discussion
upload_file
get_post

Fetch one post by id, with its author and a permalink.

whoami

Show which user the configured credentials authenticate as.

search_users

Find users by username/name — handy for mentions or moderation.

like_post

Like or unlike a post (flarum/likes).

subscribe_discussion

Set your subscription to a discussion (flarum/subscriptions).

edit_post

Replace the content of an existing post (requires permission). Content is Markdown.

rename_discussion

Change a discussion's title.

set_tags

Replace the tags on a discussion (needs ≥1 primary tag id — see list_tags).

sticky_discussion

Sticky (pin) or unsticky a discussion (flarum/sticky).

lock_discussion

Lock or unlock a discussion (flarum/lock).

delete_discussion

Permanently delete a discussion (and its posts). Requires permission. Irreversible.

delete_post

Permanently delete a single post. Requires permission. Irreversible.

// known CVEs in dependencies3 high

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

high@modelcontextprotocol/sdk@1.12.0GHSA-345p-7cg4-v4c7

@modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse

high@modelcontextprotocol/sdk@1.12.0GHSA-8r9q-7v3j-jr4g

Anthropic's MCP TypeScript SDK has a ReDoS vulnerability

high@modelcontextprotocol/sdk@1.12.0GHSA-w48q-cv73-mx4w

Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
🔐 secretFLARUM_API_TOKENoptional alternative to the above –
configFLARUM_BASE_URLno https://reverser.id
configFLARUM_EMAILFLARUM_USERNAME (or ) write tools –
configFLARUM_IDENTIFICATION
🔐 secretFLARUM_PASSWORDwrite tools –
configFLARUM_USERNAME(or FLARUM_EMAIL) write tools –
🔐 secretREVERSER_API_TOKENREVERSER_PASSWORD, ) are still read as fallbacks.
configREVERSER_BASE_URLLegacy REVERSER_ names (, REVERSER_USERNAME,
🔐 secretREVERSER_PASSWORD, REVERSER_API_TOKEN) are still read as fallbacks.
configREVERSER_USERNAMELegacy REVERSER_ names (REVERSER_BASE_URL, ,
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

20/20 tools missing one or more hints — list_tags (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); search_discussions (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); recent_discussions (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +17 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool inputs are validated

18/20 tool handlers declare input schemas (90%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tests exist

No test files found

Add tests that exercise each declared tool.

Production dependencies are patched

0 critical, 3 high severity in production deps — @modelcontextprotocol/sdk@1.12.0 (high), @modelcontextprotocol/sdk@1.12.0 (high)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 5 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/reverserid/flarum-mcp?variant=verified)](https://m8ven.ai/mcp/reverserid/flarum-mcp)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 50ff139e8eee6f3170d00c7abbfa594cc37bfbab
code hash: 737a9b310620e81a4ea022af9c3974e79d6133d4fdef93bd67bd88e67cefd16f
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client