fabushi (bhrumom/fabushi) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 60 tools. No publisher has claimed this listing.

C
Caution
74/100

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

bhrumom

Source: github_code

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
🚨
Secret credentials may flow to a network call
7 flows detected: DEEPSEEK_API_KEY, LIBRECHAT_AGENT_API_KEY, OPENCLAW_GATEWAY_TOKEN. We can’t prove the destination matches the brand the credential belongs to.
⚠️
Tests do not pass
Either the test suite is broken or the code regressed. Either way the published behaviour can’t be verified by the publisher’s own tests.
🔐
You'll be asked for 6 credentials: CODEX_DEEPSEEK_ADAPTER_SECRET, DEEPSEEK_API_KEY, FABUSHI_MARKETPLACE_REVIEW_TOKEN, LIBRECHAT_AGENT_API_KEY, OPENCLAW_GATEWAY_TOKEN, TEST_ACCOUNT_TOKEN
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.
configBOT_FATHER_MAX_COMPLETION_TOKENS
configCBETA_API_ROOT
🔐 secretCODEX_DEEPSEEK_ADAPTER_SECRET
configCODEX_DEEPSEEK_ADAPTER_TOKEN_TTL_MS
configCODEX_DEEPSEEK_RESPONSES_BASE_URL
configCODEX_HOME
configCODEX_TMPDIR
configCORS_ORIGIN
configDATA_DIR
🔐 secretDEEPSEEK_API_KEY, the installer copies it locally into LibreChat's .env
configDEEPSEEK_BASE_URL
configDEEPSEEK_MAX_COMPLETION_TOKENS
configDEEPSEEK_MODEL
configDEEPSEEK_MODELS
configENABLE_CODEX_SDK_CHAT
configENABLE_LIBRECHAT_AGENT_CHAT
configENABLE_OPENCLAW_AGENT_CHAT
configFABUSHI_API_BASE_URL
🔐 secretFABUSHI_MARKETPLACE_REVIEW_TOKEN
configFABUSHI_MINIAPP_MARKETPLACE_PATH
configFABUSHI_PUBLIC_BASE_URL
configFREE_MONTHLY_TOKEN_LIMIT
configLIBRECHAT_AGENTS_BASE_URL
🔐 secretLIBRECHAT_AGENT_API_KEY
configLIBRECHAT_AGENT_ID
configLOG_LEVEL
configMAX_RESOURCE_TEXT_CHARS
configMCP_INTERNAL_BASE_URL
configMEMBER_MONTHLY_TOKEN_LIMIT
configOPENCLAW_AGENT_ID
🔐 secretOPENCLAW_GATEWAY_TOKEN
configOPENCLAW_GATEWAY_URL
configOPENCLAW_RUNS_ENDPOINT
configOPENCLAW_RUNTIME_ENABLE_MACOS_UPDATES
configOPENCLAW_RUNTIME_MANIFEST_PATH
configOPENCLAW_RUNTIME_PUBLIC_BASE_URL
configOPENCLAW_RUNTIME_UPDATES_DIR
configRATE_LIMIT_PER_MINUTE
configREQUIRE_MEMBER_FOR_AI
configSQLITE_PATH
🔐 secretTEST_ACCOUNT_TOKEN
configTRUST_PROXY_HOPS
configXDG_RUNTIME_DIR
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
// quality suggestions

Tool annotations

55/60 tools have annotations

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

All four hints declared on every tool

60/60 tools missing one or more hints — search_dharma_resources (missing: idempotentHint); download_dharma_resource (missing: idempotentHint); prepare_dharma_share_text (missing: idempotentHint), +57 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

45/60 tool handlers declare input schemas (75%)

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

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

Tests pass

npm test failed — tests do not pass

Make sure npm test runs cleanly. Common cause: missing build step or missing env vars.

Secrets stay with their owner

7 secrets sent to a request target we could not resolve (DEEPSEEK_API_KEY → dynamic, DEEPSEEK_API_KEY → dynamic) — often a configured endpoint, not necessarily third-party

Audit where credentials are sent. A NOTION_TOKEN should only reach api.notion.com — never a third-party host.

Secrets not written to files

2 secret values written to files

Avoid persisting secrets to disk. Keep them in memory or your secret manager.

Domain consistency

npm scope @fabushi doesn't match GitHub owner bhrumom

Use the same org name across GitHub, npm, and your homepage so users can verify the publisher.

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 8 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/bhrumom/fabushi?variant=verified)](https://m8ven.ai/mcp/bhrumom/fabushi)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 77f72b13304b75a45530de03fb807f52c3624be1
code hash: 7635576f520ccfe930074f73c44ba174ddb7f0cc472bb369084ee2b9e3ea4c42
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