D
Caution
40/100
11 days ago

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

tokamak-network

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

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: OPENAI_API_KEY, ETHERSCAN_API_KEY. We can’t prove the destination matches the brand the credential belongs to.
⚠️
Known vulnerabilities in dependencies: 10 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
🔐
You'll be asked for 4 credentials: ANTHROPIC_API_KEY, ETHERSCAN_API_KEY, MCP_API_KEY, OPENAI_API_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies10 high5 medium28 low

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.1GHSA-345p-7cg4-v4c7

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

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

Anthropic's MCP TypeScript SDK has a ReDoS vulnerability

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

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

highhono@4.7.0GHSA-3vhc-576x-3qv4

Hono JWK Auth Middleware has JWT algorithm confusion when JWK lacks "alg" (untrusted header.alg fallback)

highhono@4.7.0GHSA-88fw-hqm2-52qc

hono: CORS Middleware reflects any Origin with credentials when `origin` defaults to the wildcard

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.
configALCHEMY_RPC_URLYes Ethereum mainnet RPC
configALLOWED_ORIGINS
🔐 secretANTHROPIC_API_KEYNo Anthropic API (alternative provider)
configANTHROPIC_BASE_URL
configARBITRUM_RPC_URL
configBASE_RPC_URL
configCHAT_MODEL
configDB_PATH
configELIZAOS_URL
configETHEREUM_RPC_URL
🔐 secretETHERSCAN_API_KEY
configFORUM_BASE_URL
configGOVLENS_MODEL
🔐 secretMCP_API_KEY
configMCP_SSE_PORT
🔐 secretOPENAI_API_KEYFor Web UI OpenAI-compatible API access
configOPENAI_BASE_URL
configOPINION_MODEL
configOPTIMISM_RPC_URL
configPOLYGON_RPC_URL
configQOC_MODELNo Model for QOC evaluation (default: gpt-5.2)
configSUMMARY_MODEL
configTRANSLATE_MODEL
configVALIDATION_MODEL
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployDATABASE_URL
deployPORT
// 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

15/15 tools missing one or more hints — analyze_agenda (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_contract_info (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); read_contract_source (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +12 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

11/15 tool handlers declare input schemas (73%)

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

Tool handlers catch errors

12/15 tool handlers wrap calls in try/catch (80%)

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

Tool test coverage

Only 0/15 tools referenced in tests (0%)

Write tests that reference each tool by name so every tool has at least one test.

Shell command execution

7 child_process calls — runs shell commands

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

Secrets stay with their owner

1 secret/sensitive value flow into network calls (OPENAI_API_KEY → dynamic) (1 other flows matched canonical API hosts)

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

Secrets not logged

3 secret values sent to console.log

Redact or omit secret values from log output.

Production dependencies are patched

0 critical, 8 high severity in production deps — @modelcontextprotocol/sdk@1.12.1 (high), @modelcontextprotocol/sdk@1.12.1 (high)

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

Dev dependencies

2 critical/high in dev-only deps (does not ship to users)

Upgrade dev dependencies when convenient.

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 10 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/tokamak-network-tokamak-dao-agent-y6t5gc?variant=verified)](https://m8ven.ai/mcp/tokamak-network-tokamak-dao-agent-y6t5gc)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 189ca28e369dcf2177f87c3d1f4158fff131e2dc
code hash: d4f6c8b28eae92cfc249a734f417e3e322b3553af7ceb6c6e6a4393a7923a383
verified: 8/8/2026, 7:43:31 AM
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