Bsv (b-open-io) MCP Server

bsv-mcp npm v0.3.4

Published by b-open-io — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

A collection of Bitcoin SV (BSV) tools for the Model Context Protocol (MCP) framework

Trust grade
A
96/100
Last scanned get badge →
Trust
A · 96/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 96/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 4 = 96. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 7

medium Hardcoded egress to an external endpoint (index.ts)MTC-SRC-003

In the server's implementation (`index.ts:339`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: const res = await fetch( `https://junglebus.gorillapool.io/v1/transaction/get/${txid}`, ); if (!re

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server index.ts

medium Hardcoded egress to an external endpoint (resources/brcs.ts)MTC-SRC-003

In the server's implementation (`resources/brcs.ts:93`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: ; const resp = await fetch( `https://raw.githubusercontent.com/bitcoin-sv/BRCs/master/${path}`, ); if (!re

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server resources/brcs.ts

low Hardcoded egress to an external endpoint in packaging/dev tooling (tools/bsv/decodeTransaction.ts)MTC-SRC-003

In a packaging/dev/install script (shipped, but not the server runtime) (`tools/bsv/decodeTransaction.ts:95`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: const response = await fetch( `https://junglebus.gorillapool.io/v1/transaction/get/${txid}`, ); if (!response.ok

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server tools/bsv/decodeTransaction.ts

low Hardcoded egress to an external endpoint in packaging/dev tooling (tools/bsv/getPrice.ts)MTC-SRC-003

In a packaging/dev/install script (shipped, but not the server runtime) (`tools/bsv/getPrice.ts:23`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: rice const res = await fetch( "https://api.whatsonchain.com/v1/bsv/main/exchangerate", ); if (!res.ok) throw new Er

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server tools/bsv/getPrice.ts

low Hardcoded egress to an external endpoint in packaging/dev tooling (tools/wallet/fetchPaymentUtxos.ts)MTC-SRC-003

In a packaging/dev/install script (shipped, but not the server runtime) (`tools/wallet/fetchPaymentUtxos.ts:36`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: const response = await fetch( `https://api.whatsonchain.com/v1/bsv/main/address/${address}/unspent`, ); if (!re

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server tools/wallet/fetchPaymentUtxos.ts

low Hardcoded egress to an external endpoint in packaging/dev tooling (tools/wallet/purchaseListing.ts)MTC-SRC-003

In a packaging/dev/install script (shipped, but not the server runtime) (`tools/wallet/purchaseListing.ts:58`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: const response = await fetch( `https://ordinals.gorillapool.io/api/txos/${listingOutpoint}?script=true`, )

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server tools/wallet/purchaseListing.ts

low Shell/command execution in packaging/dev tooling (tools/utils/installAgentMaster.ts)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`tools/utils/installAgentMaster.ts:1`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: rt { spawn } from "node:child_process"; import { z } from "zod"; const installAgentMasterSchema = z.object({ method: z

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server tools/utils/installAgentMaster.ts

Tools 87

Each tool and what it can reach — statically extracted from the published source.

  • bmap_readPostsingests untrusted input
  • bsocial_readPostsingests untrusted input
  • a2b_discoverno sensitive capability
  • bap_friendno sensitive capability
  • bap_generateno sensitive capability
  • bap_getCurrentAddressno sensitive capability
  • bap_getIdno sensitive capability
  • bmap_readFollowsno sensitive capability
  • bmap_readLikesno sensitive capability
  • bsocial_createPostno sensitive capability
Show 77 more tools ↓
  • bsv_decodeTransactionno sensitive capability
  • bsv_exploreno sensitive capability
  • bsv_getPriceno sensitive capability
  • bsv_toBitcoinno sensitive capability
  • bsv_toSatoshino sensitive capability
  • bsv_toTokenno sensitive capability
  • bsv_toTokenSatoshino sensitive capability
  • droplit_discoverno sensitive capability
  • droplit_fundno sensitive capability
  • droplit_getAccessno sensitive capability
  • droplit_pushno sensitive capability
  • mnee_getBalanceno sensitive capability
  • mnee_parseTxno sensitive capability
  • mnee_sendMneeno sensitive capability
  • ordinals_getInscriptionno sensitive capability
  • ordinals_getTokenByIdOrTickerno sensitive capability
  • ordinals_marketListingsno sensitive capability
  • ordinals_marketSalesno sensitive capability
  • ordinals_searchInscriptionsno sensitive capability
  • utils_convertDatano sensitive capability
  • wallet_a2bPublishMcpno sensitive capability
  • wallet_abortActionno sensitive capability
  • wallet_acquireCertificateno sensitive capability
  • wallet_cancelListingno sensitive capability
  • wallet_checkDroplitFaucetStatusno sensitive capability
  • wallet_createActionno sensitive capability
  • wallet_createDroplitFaucetno sensitive capability
  • wallet_createHmacno sensitive capability
  • wallet_createOrdinalsno sensitive capability
  • wallet_createSignatureno sensitive capability
  • wallet_decryptno sensitive capability
  • wallet_discoverByAttributesno sensitive capability
  • wallet_discoverByIdentityKeyno sensitive capability
  • wallet_encryptno sensitive capability
  • wallet_gatherCollectionInfono sensitive capability
  • wallet_getAddressno sensitive capability
  • wallet_getBalanceno sensitive capability
  • wallet_getBsv21Balancesno sensitive capability
  • wallet_getHeaderForHeightno sensitive capability
  • wallet_getHeightno sensitive capability
  • wallet_getLockDatano sensitive capability
  • wallet_getNetworkno sensitive capability
  • wallet_getOrdinalsno sensitive capability
  • wallet_getPublicKeyno sensitive capability
  • wallet_getVersionno sensitive capability
  • wallet_internalizeActionno sensitive capability
  • wallet_isAuthenticatedno sensitive capability
  • wallet_listActionsno sensitive capability
  • wallet_listCertificatesno sensitive capability
  • wallet_listOrdinalno sensitive capability
  • wallet_listOutputsno sensitive capability
  • wallet_listTokensno sensitive capability
  • wallet_lockBsvno sensitive capability
  • wallet_mintCollectionno sensitive capability
  • wallet_opnsDeregisterno sensitive capability
  • wallet_opnsRegisterno sensitive capability
  • wallet_proveCertificateno sensitive capability
  • wallet_purchaseListingno sensitive capability
  • wallet_refreshUtxosno sensitive capability
  • wallet_registerDroplitKeyno sensitive capability
  • wallet_relinquishCertificateno sensitive capability
  • wallet_relinquishOutputno sensitive capability
  • wallet_revealCounterpartyKeyLinkageno sensitive capability
  • wallet_revealDelegationno sensitive capability
  • wallet_revealSpecificKeyLinkageno sensitive capability
  • wallet_sendAllBsvno sensitive capability
  • wallet_sendBsvno sensitive capability
  • wallet_signActionno sensitive capability
  • wallet_signBsmno sensitive capability
  • wallet_sweepBsvno sensitive capability
  • wallet_sweepBsv21no sensitive capability
  • wallet_sweepOrdinalsno sensitive capability
  • wallet_transferOrdTokenno sensitive capability
  • wallet_unlockBsvno sensitive capability
  • wallet_verifyHmacno sensitive capability
  • wallet_verifySignatureno sensitive capability
  • wallet_waitForAuthenticationno sensitive capability

What this scan could not see

Versions 3

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.3.4 latest A 96/100 7 1.13.0 2026-09-07
v0.3.0 A 96/100 7 1.13.0 2026-09-06
v0.2.15 A 96/100 7 1.12.1 2026-07-29

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 96/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/bsv-mcp/badge.svg)](https://mcptrustchecker.com/registry/bsv-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/bsv-mcp"><img src="https://mcptrustchecker.com/registry/bsv-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/bsv-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan bsv-mcp --online

Use the free API → How scoring works

Other implementations of Bsv 1

Independent packages implementing the same tool, scanned with the same engine. Compare all 2 side by side →

More in Other