What is the bsv.cx remote MCP server?
The bsv.cx remote MCP server is a hosted Model Context Protocol endpoint at https://bsv.cx/mcp, so AI assistants can connect to it without installing or running anything locally.
bsv.cx MCP ServerVerifiedFeatured
@Andy Rowe
Basic information
About bsv.cx MCP Server
Timestamp and verify evidence on-chain. Let your agent prove what it saw and when. bsv.cx gives an AI agent verifiable memory. Timestamp a hash of any output, archive a web page as it looked, or fetch a URL with a receipt proving what came back — each anchored in a Bitcoin SV transaction. Verification is free and needs no trust in bsv.cx: anyone can check the proof on any explorer.
Connection details
https://bsv.cx/mcpSetup
claude mcp add bsv-cx --transport http https://bsv.cx/mcpbsv.cx MCP Server tools
9Anchor 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.
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.
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.
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).
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.
Fetch the manifest for a previous archive_url capture: when it was taken, and its proof. Free.
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).
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).
Report whether anchoring is currently working. Call this if a tool reports something stored but not anchored.
Overview
An agent that summarises a page, cites a source, or produces an artifact has no way to demonstrate later that the input was real and unaltered. "I read it on Tuesday" is not evidence.
bsv.cx turns that into something a third party can check:
- notarize_hash — prove a document or output existed at a point in time WITHOUT revealing it. You hash the content yourself and send only the digest; bsv.cx never sees what was hashed.
- archive_url — capture a web page as it looks right now and anchor a hash of that capture, so a later edit or deletion cannot be denied.
- verifiable_fetch — fetch a URL as readable text plus a receipt committing to the exact bytes returned.
- batch_timestamp — anchor a Merkle root over many hashes in one transaction.
- verify_hash / get_archive — check any existing proof. Always free.
- service_status — availability and remaining free-trial calls.
Every proof is a real Bitcoin SV transaction. You do not have to trust bsv.cx to check one — read the transaction on any explorer.
What a timestamp proves: those exact bytes existed no later than that block. What it does NOT prove: who made them, that they are true, or that they are original. Anyone can timestamp anything, including someone else's work.
Free to start: notarize and archive are free; the metered tools include free trial calls.
Frequently asked questions
How do I connect to the bsv.cx MCP server?
Add the endpoint https://bsv.cx/mcp to any MCP-compatible client such as Claude Code, Cursor, or VS Code. The setup snippets on this page configure each client in one step.
Does the bsv.cx MCP server require authentication?
No. bsv.cx's MCP server does not require authentication — you can connect directly with the endpoint URL.
Which transport does the bsv.cx MCP server use?
bsv.cx exposes a Streamable HTTP endpoint, the transport used by remote MCP servers and supported by all major MCP clients.
More remote MCP servers
A
AccountHub
One MCP connection for all your Gmail, Google Calendar, Drive and Contacts accounts, Slack workspaces and Notion — free.
%20-%20Sarah%20Xu.svg){kind=icon}
Adobe Experience Manager
Manage your Adobe Experience Manager content
Adgentek Ad Server (AdsMCP)
AdsMCP is the MCP entry point into the Adgentek Ad Server. Call ads_serve with the conversation context and get back a native ad matched to user intent, or no ad when one does not fit. Publishers earn on a CPM basis. Fre
AOI — Environmental Intelligence
AOI is a commercial environmental-intelligence gateway that gives AI agents programmatic access to 38 real-world intelligence capabilities — climate risk, satellite monitoring, methane detection, water & soil, vegetation
Aard
Aard connects Macroeconomic and other official data from 170+ publishers including World Bank, IMF, BIS, ECB, Eurostat, and National Statistical Offices. Aard is powered by a large graph of the metadata universe and an
Comments