Skip to content
External endpointresponds

bsv.cx

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

Endpoint URL
https://bsv.cx/mcp
Current status
responds
Last checked
Aug 17, 2026, 05:00 AM UTC
Check
MCP initialize · 8s limit
Latency
529 ms
Response record
4 of 4 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
cx.bsv/bsv-cx

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
bsv.cx
Version
0.1.0
Capability keys
tools
Tool names
notarize_hash, verify_hash, archive_url, get_archive, verifiable_fetch, batch_timestamp, service_status
Instructions excerpt

Timestamp and verify evidence on the Bitcoin SV blockchain. Use notarize_hash to prove a document or output existed at a point in time WITHOUT revealing it — hash the content yourself and send only the digest. Use archive_url to capture a web page as it looked right now, so a later change cannot be denied. Use verify_hash and get_archive to check any existing proof; verification is free and needs no trust in bsv.cx. Anchors are independently verified against bsv.cx's OWN block headers (synced over the BSV P2P network, not an explorer), and every proof is exportable as BEEF/BUMP (/spv/beef/:txid, /spv/bump/:txid) that any @bsv/sdk client verifies with no bsv.cx-specific code. Hashes are of exact bytes: re-encoding a file changes its hash.

Reported Aug 17, 2026, 05:00 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 135ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 343ms
  3. responds
    MCP initialize · 8s limit · HTTP 200 · 999ms
  4. responds
    MCP initialize · 8s limit · HTTP 200 · 529ms