fluffos-mcp (gesslar/fluffos-mcp) is an MCP server listed on the M8ven Trust Index. M8ven has not graded it: we have no way to read this server ourselves. No publisher has claimed this listing.

C
Emerging
74/100
15 days ago

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. 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

gesslar

Source: modelscope

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

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
4 tools verified — handlers match their declared behaviour
3 read-only tools verified — handlers contain no write/delete/exec
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.
// 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.
configFLUFFOS_BIN_DIRDirectory containing FluffOS binaries (symbol, lpcc, and optionally lpcshell)
configFLUFFOS_DOCS_DIRfluffos_doc_lookup is only registered when the server is started with set. fluffos_eval is only registered when FLUFFOS_ENABLE_EVAL is set.
configFLUFFOS_ENABLE_EVALfluffos_doc_lookup is only registered when the server is started with FLUFFOS_DOCS_DIR set. fluffos_eval is only registered when is set.
configFLUFFOS_EVAL_MAX_BYTES
configFLUFFOS_EVAL_MAX_CONCURRENT
configFLUFFOS_EVAL_TIMEOUT_MS(Optional) Wall-clock cap in milliseconds for a single fluffos_eval run before the lpcshell child is killed. Defaults to 30000 (30s); ignored unless fluffos_eval is enabled.
configMUD_RUNTIME_CONFIG_FILEPath to your FluffOS config file (e.g., /mud/lib/etc/config.test)
// quality suggestions

All four hints declared on every tool

3/4 tools missing one or more hints — fluffos_validate (missing: destructiveHint); fluffos_disassemble (missing: destructiveHint); fluffos_doc_lookup (missing: destructiveHint). 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.

Shell command execution

5 child_process/subprocess calls in production code — runs shell commands (src/index.js:97, src/index.js:378, src/index.js:415)

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

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 2 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 Score](https://m8ven.ai/badge/mcp/gesslar-fluffos-mcp-0t4wi7)](https://m8ven.ai/mcp/gesslar-fluffos-mcp-0t4wi7)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 4abe60410fdd6ed990fc0147192092af244d4382
code hash: 8a4285df33ad4b63b8e049f1e0570bcd08cce304cb9cb70949c44d0d2e84882e
verified: 8/13/2026, 9:19:16 PM
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