blocksnetwork/blocks-sdk (blocksnetwork/blocks-sdk) is an MCP server listed on the M8ven Trust Index. It scores 89 out of 100, grade B. It declares 15 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
B
Emerging
89/100
2 months ago

blocksnetwork/blocks-sdk

MCP server for Blocks Network consumer operations

→ blocksnetwork/blocks-sdk· npm: @blocks-network/mcp-server· listed on npm

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

blocksnetwork

Source: npm

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

npm

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

// key findings
🚨
Secret credentials may flow to a network call
1 flow detected: BLOCKS_API_KEY. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 9 credentials: ANTHROPIC_API_KEY, BLOCKS_API_KEY, BLOCKS_PUBLISH_KEY, BLOCKS_SUBSCRIBE_KEY, BLOCKS_TOKEN, PUBNUB_PUBLISH_KEY, PUBNUB_SECRET_KEY, PUBNUB_SUBSCRIBE_KEY, TEST_GET_ENV_KEY
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.
🔐 secretANTHROPIC_API_KEY
🔐 secretBLOCKS_API_KEY
configBLOCKS_BACKEND_URL
configBLOCKS_CDM_URL
configBLOCKS_DEBUG_INTERNAL
configBLOCKS_MCP_FILE_ROOT
configBLOCKS_ORG_ID
🔐 secretBLOCKS_PUBLISH_KEY
🔐 secretBLOCKS_SUBSCRIBE_KEY
🔐 secretBLOCKS_TOKEN
configBLOCKS_TOKEN_ENDPOINT
configCLAUDE_ALLOWED_PATHS
configCLAUDE_ALLOWED_TOOLS
configCLAUDE_BASH_BLOCKLIST
configCLAUDE_BASH_SAFETY
configCLAUDE_DISALLOWED_TOOLS
configCLAUDE_MAX_BUDGET_USD
configCLAUDE_MODEL
configINSTANCE_ID
configLOG_LEVEL
configPUBNUB_LIVE_TEST
🔐 secretPUBNUB_PUBLISH_KEY
🔐 secretPUBNUB_SECRET_KEY
🔐 secretPUBNUB_SUBSCRIBE_KEY
configSHELL
🔐 secretTEST_GET_ENV_KEY
// 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 — send_task (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_task (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_tasks (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

12/15 tool handlers declare input schemas (80%)

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

Tool handlers catch errors

Only 0/15 tool handlers wrap calls in try/catch (0%)

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

Shell command execution

1 child_process call — runs shell commands

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

Domain consistency

npm scope @blocks-network doesn't match GitHub owner blocksnetwork

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 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 Score](https://m8ven.ai/badge/mcp/blocksnetwork/blocks-sdk)](https://m8ven.ai/mcp/blocksnetwork/blocks-sdk)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 3511b34feed663848c9c9d5b5a37c7e57a89dac1
code hash: 83cac7eddbe0eb10d0560e29717d439271b632932f338d628bc285802ff9b119
verified: 6/13/2026, 10:06:18 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