ffl-mcp (nuwainfo/ffl-mcp) is an MCP server listed on the M8ven Trust Index. It scores 54 out of 100, grade D. It declares 10 tools. No publisher has claimed this listing.

D
Caution
54/100

ffl-mcp

MCP server for ffl. Let AI share anything for you.

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

nuwainfo

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 →

Install from

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
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 1 credential: FFL_HOOK_PASSWORD
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// 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.
configXDG_CONFIG_HOME
configCLAUDE_CLI_PATH
configCLAUDE_BIN
configNVM_DIR
configCODEX_CLI_PATH
configCODEX_BIN
configFFL_MCP_BINARY
configFFL_WAIT_LINK_SECONDS
configALLOWED_BASE_DIRexport ="$HOME/Downloads"
configFFL_RUN_MODEpython runs the Core.py CLI (requires FFL_CORE_PATH).
configFFL_BINexport ="$HOME/bin/ffl.com"
configFFL_PYTHON
configFFL_CORE_PATHFFL_RUN_MODE=python runs the Core.py CLI (requires ).
configFFL_COMMAND
configFFL_USE_STDIN1 avoids writing text/base64 payloads to disk.
configFFL_SHELL
configFFL_USE_HOOK1 starts a local webhook server and passes it to ffl for real-time link/progress events.
configFFL_HOOK_HOST
configFFL_HOOK_PATH
configFFL_HOOK_USERNAME
🔐 secretFFL_HOOK_PASSWORD
configFFL_HOOK_MAX_EVENTS
configFFL_DEBUG1 saves ffl output to a temp log file; path returned as debugLogPath. Set FFL_DEBUG=/path/to/log.txt to use a fixed path.
configPYAPP
// 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

10/10 tools missing one or more hints — fflShareText (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); fflShareBase64 (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); fflShareFile (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +7 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.

Destructive tools are labelled

2 tools perform destructive updates without destructiveHint — fflDownload deletes at line 1689 (os.remove(logPath)); fflKeygen deletes at line 1795 (os.remove(logPath))

Add destructiveHint:true to any tool whose handler calls .delete(), .upsert(), .update(), unlink, rm, DELETE, DROP, REPLACE INTO, or any operation that overwrites existing data.

Tool inputs are validated

9/10 tool handlers declare input schemas (90%)

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

Tool handlers catch errors

Only 2/10 tool handlers wrap calls in try/catch (20%)

Wrap each tool handler body in try/catch and return a structured error response.

Tests exist

No test files found

Add tests that exercise each declared tool.

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 6 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/nuwainfo/ffl-mcp?variant=verified)](https://m8ven.ai/mcp/nuwainfo/ffl-mcp)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: f229534e553b742982e91e4a082688458a385a79
code hash: c76484ec6c053a9ce89cc75539df1da3d3f6a36cbc20d23f8b66eb29d748fed4
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