mcpbeat

bsv.cx MCP Server

cx.bsv/bsv-cx
answering

bsv.cx is answering right now. Last checked 1 min ago. It exposes 7 tools.

Timestamp and verify evidence on-chain. Prove what your agent saw and when; verifying is free.

Uptime history 41 hours of history
41 hours agonow
100.0%
Uptime 24h
92 of 92 checks
7
Tools
read from the server
380 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

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

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 7

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. 10 free calls, then priced per call.
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.
service
service_status
Report whether anchoring is currently working, plus free-trial POOL status. The trial is a shared pool with a per-caller cap — not a personal balance — so 'open' means the pool has calls left, NOT that you personally do. Call this if a tool reports something stored but not anchored.
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. 10 free calls, then priced per call.
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

URLTransportStateLatencyChecked
https://bsv.cx/mcp streamable-http answering 401 ms 1 min ago

bsv.cx — questions

Answers built from our own checks of this server.

What can bsv.cx do?
It exposes 7 tools, read directly from the server on our last check. Among them: archive_url, batch_timestamp, get_archive, notarize_hash, service_status, verifiable_fetch and 1 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 92 of 92 checks got a reply (100.0%), average response time 380 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 7 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 380 ms on average, which is faster than 36% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.