C
Warning
68/100
3 days ago

bsv-mcp

An MCP Server for Bitcoin SV

Warning. Serious findings were identified. Review the full report before connecting. 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

b-open-io

Source: github_code · also listed on PulseMCP, mcp.so

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
1 flow detected: OAUTH_ISSUER. We can’t prove the destination matches the brand the credential belongs to.
⚠️
Known vulnerabilities in dependencies: 14 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
// known CVEs in dependencies14 high10 medium7 low

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

highmcp-handler@1.0.7GHSA-w2fm-25vw-vh7f

mcp-handler has a tool response leak across concurrent client sessions ('Race Condition')

highnext@16.1.6GHSA-267c-6grr-h53f

Next.js has a Middleware / Proxy bypass in App Router applications via segment-prefetch routes

highnext@16.1.6GHSA-26hh-7cqf-hhc6

Next.js has a Middleware / Proxy bypass in App Router applications via segment-prefetch routes - Incomplete Fix Follow-Up

highnext@16.1.6GHSA-36qx-fr4f-26g5

Next.js has a Middleware / Proxy bypass in Pages Router applications using i18n

highnext@16.1.6GHSA-492v-c6pp-mqqv

Next.js has a Middleware / Proxy bypass through dynamic route parameter injection

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.
configBSV_CHAIN
configDISABLE_BAP_TOOLS
configDISABLE_BROADCASTINGfalse Set to true to disable transaction broadcasting; returns raw transaction hex instead - useful for testing and transaction review before broadcasting
configDISABLE_BSOCIAL_TOOLS
configDISABLE_BSV_TOOLSfalse Set to true to disable BSV blockchain tools
configDISABLE_MNEE_TOOLSfalse Set to true to disable MNEE token tools
configDISABLE_ORDINALS_TOOLSfalse Set to true to disable Ordinals/NFT tools
configDISABLE_PROMPTSfalse Set to true to disable all educational prompts
configDISABLE_RESOURCESfalse Set to true to disable all resources (BRCs, changelog)
configDISABLE_TOOLSfalse Set to true to disable all tools
configDISABLE_UTILS_TOOLSfalse Set to true to disable utility tools
configDISABLE_WALLET_TOOLSfalse Set to true to disable Bitcoin wallet tools
configDROPLIT_API_URL
configDROPLIT_FAUCET_NAMEnot set Name of the faucet to use (required when USE_DROPLIT_API is true)
configENABLE_A2B_TOOLS
configENABLE_OAUTH
configIDENTITY_KEY_WIFclaude mcp add bsv-mcp "bunx bsv-mcp@latest" -e PRIVATE_KEY_WIF=your_key -e =your_identity_key
configOAUTH_ISSUER
configPRIVATE_KEY_WIFclaude mcp add bsv-mcp "bunx bsv-mcp@latest" -e =your_key -e IDENTITY_KEY_WIF=your_identity_key
configREMOTE_STORAGE_URL
configRESOURCE_URL
configTRANSPORTstdio MCP transport mode (stdio/http) - automatically set to stdio for Claude Code compatibility
configUSE_DROPLIT_APIfalse Set to true to enable Droplit API mode for remote wallet operations
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
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

85/85 tools missing one or more hints — utils_installAgentMaster (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); utils_convertData (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); wallet_a2bPublishMcp (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +82 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

Only 30/85 tool handlers declare input schemas (35%)

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

Tool test coverage

Only 4/85 tools referenced in tests (5%)

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

Shell command execution

1 child_process/subprocess call in production code — runs shell commands (utils/passphrasePrompt.ts:143)

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 (OAUTH_ISSUER → dynamic)

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

Secrets not logged

1 secret value sent to console.log

Redact or omit secret values from log output.

Production dependencies are patched

0 critical, 1 high severity in production deps — mcp-handler@1.0.7 (high)

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

Dev dependencies

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

Upgrade dev dependencies when convenient.

Dependency freshness

1/20 production deps stale: @gorillapool/js-junglebus@2024-05-06 (2.3y)

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 9 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/b-open-io-bsv-mcp-1454z9?variant=verified)](https://m8ven.ai/mcp/b-open-io-bsv-mcp-1454z9)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 1e11ca6993047a614d16c3ffc8da976237543c26
code hash: 09fa9f7a998ccb70c1809fc4306565ed290759f0f838fc9a6b7730a7a3b35f99
verified: 8/16/2026, 9:04:19 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