The bsv.cx MCP server,
connected in one click.
Timestamp & verify evidence on-chain, free. Proofpack: a portable BEEF+BUMP proof bundle per txid. Connect the official bsv.cx MCP server to Claude, ChatGPT, or Cursor through gate — one gateway URL, no config files, security-checked.
Free to start · No credit card · No hosting needed
Add bsv.cx to your AI in one minute
Pick your client. Copy, paste, done — or let gate handle sign-ins and policies for you.
claude mcp add --transport http bsv-cx https://bsv.cx/mcpRun in your terminal, then restart Claude Code.
bsv.cx · https://bsv.cx/mcp
What your AI can do with bsv.cx
Real prompts you can type the moment it's connected — no setup, no docs to read.
“Use “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.”
“Use “verify_hash”: Look up a sha256 across EVERY bsv.cx protocol — notary timestamps, verifiable-fetch receipts, notarized captures, web-page archives, Merkle.”
“Use “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.”
“Use “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 heade.”
How secure is the bsv.cx MCP server?
Every server in the gate directory has to pass the same four checks before your AI can touch it. Here's how bsv.cx holds up.
Security grade A
gate scanned 9 tools on Sep 6, 2026 for prompt injection and risky tool definitions — nothing to flag.
- lowproofpack: Autonomous payment capability without explicit user confirmation cue
- lowverifiable_fetch: Autonomous payment capability without explicit user confirmation cue
- lowbatch_timestamp: Autonomous payment capability without explicit user confirmation cue
Official endpoint
Operated by bsv.cx (bsv.cx) at its documented MCP endpoint — not a third-party mirror or community re-host.
No sign-in needed
This server only exposes public data — no account and no credentials are involved when you connect.
Scanned before it goes live
gate checks every tool for prompt injection, hidden instructions, data-exfiltration hints, and over-broad permissions before the server is available through your gateway.
Watched for drift
If bsv.cx adds or changes tools later, gate re-scans and alerts you — before your AI acts on the change.
Connected in three steps
Connect your gate
Add one gateway URL to Claude, ChatGPT, or any MCP client. One-time setup, about two minutes.
Pick bsv.cx
Choose bsv.cx in the gate directory. No sign-in needed.
Use it anywhere
bsv.cx's tools are live in every AI client you've connected — with rules and logging built in.
Free to start · No credit card · No hosting needed
The actual tools bsv.cx exposes
Fetched live from the official endpoint and re-checked daily by gate — not marketing copy.
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
verify_hash — Look up a sha256 across EVERY bsv.cx protocol — notary timestamps, verifiable-fetch receipts, notarized captures, web-page archives, Merkle
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.
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 heade
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 pa
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
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 inc
+ 1 more tools once connected
Who runs the bsv.cx MCP server?
The bsv.cx MCP server at a glance
https://bsv.cx/mcpQuestions, answered
Is there an official bsv.cx MCP server?
Yes — bsv.cx operates its own remote MCP server at bsv.cx. gate connects you to that official endpoint and adds security scanning, per-tool access rules, and an activity log on top.
How do I connect bsv.cx to Claude or ChatGPT?
Add gate's gateway URL to your AI client once, then pick bsv.cx in the directory. No account or sign-in is needed. From then on, bsv.cx's tools are available in every client you've connected to gate.
Do I need to host anything?
No. bsv.cx runs the server, and gate is fully managed. You just connect one URL — there's nothing to install, deploy, or maintain.
Is the bsv.cx MCP server safe to connect?
It's the vendor's official endpoint, and gate scans its tools for prompt injection and hidden instructions before it goes live, re-checks it whenever it changes, and lets you allow, block, or require approval for every single tool.
Is it free?
Yes — you can get started with gate for free and connect bsv.cx in minutes. No credit card required.
Connect more than just bsv.cx
Every server below works through the same gateway URL — connect once, add tools anytime.
Squarespace DomainsDesignView →Set up bsv.cx in: Claude · Claude Code · ChatGPT · Cursor · VS Code