Bsv MCP server

• Registry namecx.bsv/bsv-cxverified in the MCP registry

The registry name sits under bsv.cx. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-26
• Tools9
• Server calls itselfbsv.cx
• Server version0.1.1
• Protocol version2025-06-18

On 2026-10-26 the server answered initialize and tools/list without a sign-in. First answer in 94 ms.

• Its tools do every use case we checked: timestamp a file, contract, or photo on chain without uploading it; verify a Bitcoin inclusion proof against block headers; archive a web page with its hash anchored on chain.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP score96 of 100answers 100 · does the job 100 · definitions 83 · context 100 · connects 100
• What an agent can do with it3 of 3 use cases
• Answered100% of days9 of 9 daily checks
• Median first answer290 ms
• Space in an agent's context≈ 1,426 tokensthe definitions of all its tools (9), which an agent carries on every turn
• Tool definitionsB · 83 of 100
• Typed results0 of 9 toolsdeclared outputSchema: results come typed, read once

• Not saying whether it only reads or can destroy: 9 of 9

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• notarize_hash

  Anchor a sha256 digest in a Bitcoin SV transaction, proving the content existed at this time. Send ONLY the hash — the content never leaves your machine, and bsv.cx cannot see what was hashed. Free. Idempotent: the same hash returns the…

• verify_hash

  Look up a sha256 across EVERY bsv.cx protocol — notary timestamps, verifiable-fetch receipts, notarized captures, web-page archives, Merkle batch roots and attestations — and return when it was anchored and the transaction that proves it…

• spv_verify

  Verify ANY Bitcoin (BSV) Merkle inclusion proof — a BEEF envelope (BRC-62), a BUMP (BRC-74), or a raw TSC proof — against block headers bsv.cx syncs itself over the BSV P2P network, NOT an explorer. Returns confirmed / rejected /…

• proofpack

  For any CONFIRMED BSV transaction id, get a freshly SPV-verified bundle: BEEF (BRC-62) and BUMP (BRC-74) plus bsv.cx's own self-synced header-tip attestation. bsv.cx fetches the Merkle proof and folds it against block headers it syncs…

• archive_url

  Capture a web page as it looks right now — screenshot and text — and anchor a hash of that capture on-chain. Use this before relying on a page you cite, so a later edit or deletion cannot be denied. Free.

• get_archive

  Fetch the manifest for a previous archive_url capture: when it was taken, and its proof. Free.

• verifiable_fetch

  Fetch a URL as readable text AND get a receipt anchoring a hash of the exact bytes returned, so you can later prove what the page said when you read it. Priced per call (pay over HTTP with an x402 payment — see /pay).

• batch_timestamp

  Anchor a Merkle root over many sha256 digests in a single transaction — far cheaper per item than notarizing each one. Each hash gets an inclusion proof. Priced per call (pay over HTTP with an x402 payment — see /pay).

• service_status

  Report whether anchoring is currently working. Call this if a tool reports something stored but not anchored.