bsv.cx MCP Server

by bsv Your server? Claim it

answering

bsv.cx is answering right now. Last checked moments ago. It exposes 9 tools.

Timestamp & verify evidence on-chain, free. Proofpack: a portable BEEF+BUMP proof bundle per txid.

Uptime history 53 days of history · worst day 78%

53 days agonow

96.7%

Uptime 24h

88 of 91 checks

Tools

read from the server

591 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 6

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 21 August 2026. No other catalogue keeps this.

31 Aug a tool appeared proofpack

31 Aug a tool changed version

27 Aug a tool appeared spv_verify

21 Aug 3 tool descriptions were rewritten batch_timestamp, service_status, verifiable_fetch

bsv.cx does not always answer

Over the last week it answered 98.3% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 0 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add bsv-cx --transport http https://bsv.cx/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "bsv-cx": {
      "url": "https://bsv.cx/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.bsv-cx]
url = "https://bsv.cx/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "bsv-cx": {
      "url": "https://bsv.cx/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "bsv-cx": {
      "url": "https://bsv.cx/mcp"
    }
  }
}

Available tools 9

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

archive

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.

batch

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).

notarize

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 same record.

proofpack

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 over the BSV P2P network BEFORE serving, so you receive a bundle that already confirms — verifiable by any @bsv/sdk client with no bsv.cx-specific code. Verification itself is free at /spv/verify; this does the fetch + fold + package for you and is priced per call (pay over HTTP with an x402 payment — see /pay).

service

service_status

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

spv

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 / inconclusive. This is the trustless core: you send only the proof (never the root), we fold the root ourselves and check it against a header we hold — so you never have to trust bsv.cx. Works for ANY txid's proof, not just bsv.cx's own anchors. Free.

verifiable

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).

verify

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. A hash anchored by any of these counts as found. Free, and never rate-limited into unavailability.

Endpoints

URL	Transport	State	Latency	Checked
https://bsv.cx/mcp	streamable-http	answering	429 ms	0 min ago

Alternatives to bsv.cx

same job, measured the same way

verify-proof

by csolomon0704-prog

Verify blockchain timestamp proofs offline, or anchor a new one through ProofLedger.

348 installs/wk local only

Vtimestamp

by vdappdev2

MCP server for verifying and querying vtimestamp proofs on the Verus blockchain

27 installs/wk local only

GENESIS ProofRelay MCP Verifier

by genesisre

Read-only verifier for 25 ProofRelay MCP tools and non-confidential evidence bundles.

26 tools answering

Runvouch

by runvouch

Watchdog for unattended AI agents: alerts, evidence checks and a verifiable proof per run.

7 tools answering

TrustNotch

by trustnotch

Tamper-evident audit logs for AI agents: submit, fetch, and verify cryptographic proof bundles.

122 installs/wk local only

RunOnProof — Payment Decision and Agent ID

by runonproof

Free agent identity and signed US supplier-payment decisions. Inspect first; verify portable proof.

answering

Vtimestamp Write

by vdappdev2

MCP server for creating vtimestamp proofs on the Verus blockchain via a local or remote daemon

36 installs/wk local only

Provider Trust — Verify a Source or Provider

by scriptmasterlabs

Verify a source or provider before an AI agent trusts it. Evidence only; unknown stays unknown.

6 tools answering

bsv.cx — questions

Answers built from our own checks of this server.

What can bsv.cx do?

It exposes 9 tools, read directly from the server on our last check. Among them: archive_url, batch_timestamp, get_archive, notarize_hash, proofpack, service_status and 3 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is bsv.cx working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 88 of 91 checks got a reply (96.7%), average response time 591 ms. The bar chart above shows every period we have measured.

How do I connect bsv.cx?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does bsv.cx need an API key?

No. bsv.cx completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 9 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is bsv.cx?

It answers our handshake in 591 ms on average, which is faster than 25% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.