Back to MCP Trust Indexm8ven
C
Emerging
74/100
8 days ago

mcp-server

→ hummbl-dev/mcp-server· listed on modelscope

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

hummbl-dev

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 →

⚡ Connect GitHub for Live Monitored

Install from

modelscope

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

// key findings
🚨
Secret credentials may flow to a network call
2 flows detected: GITHUB_CLIENT_SECRET. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 2 credentials: GITHUB_CLIENT_SECRET, HUMMBL_API_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies4 low

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

lowhono@4.12.28GHSA-54fx-42gc-7vw4

Hono: Algorithmic Complexity DoS in Language Middleware

lowhono@4.12.28GHSA-79qm-7rj5-m7r9

Hono: Proxy Helper does not remove response headers listed in the `Connection` header

lowhono@4.12.28GHSA-8j4g-w8fx-2239

Hono: ReDoS in CORS middleware via Access-Control-Request-Headers

lowhono@4.12.28GHSA-f23p-vx2j-j53r

Hono: `memo()` retains SSR output across requests, leading to cross-user data disclosure

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.
configALLOW_UNAUTHENTICATED_MCP_HTTP
configCLOUDFLARE_ACCOUNT_ID
configENVIRONMENT
configGITHUB_CLIENT_ID
🔐 secretGITHUB_CLIENT_SECRET
configGITHUB_REDIRECT_URI
🔐 secretHUMMBL_API_KEY
configHUMMBL_API_URL
configMCP_HTTP_ALLOWED_ORIGINS
configMCP_HTTP_PORT
configBIF_SESSIONS_DIR
configGOVERNANCE_STATE_DIR
configGOVERNANCE_DB_PATH
configGOVERNANCE_AUDIT_DIR
configMONITOR_STATE_DIR
configSANDBOX_STATE_DIR
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
// quality suggestions

Tool annotations

11/16 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

16/16 tools missing one or more hints — export_models (missing: destructiveHint, idempotentHint, openWorldHint); get_methodology (missing: destructiveHint, idempotentHint, openWorldHint); audit_model_references (missing: destructiveHint, idempotentHint, openWorldHint), +13 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.

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/hummbl-dev-mcp-server-x97ae3)](https://m8ven.ai/mcp/hummbl-dev-mcp-server-x97ae3)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 5cc6b5b0eb22cebb1cbd7fffeffcf237744fa204
code hash: 540ab5777c9525e5731bef325c0dcc12bb6ba93e2aa35827197f546fa7f60094
verified: 8/13/2026, 9:11:42 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