Security & Testing

bsv.cx

Provides tools to anchor, verify, and archive content on the Bitcoin SV blockchain for data integrity and timestamping.

x402 supported1 endpoint8 known toolsFirst detected July 25, 2026Last detected August 29, 2026

ENDPOINT 1

https://bsv.cx/mcp

No auth detected

MCP server metadata

Name: bsv.cx
Version: 0.1.0

Capabilities

tools.listChanged

Server instructions

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.

Known tools 8

notarize_hash

Anchor a sha256 digest in a Bitcoin SV transaction, proving the content existed at this time.

Inferred read-only

verify_hash

Look up a sha256 across EVERY bsv.

Inferred read-only

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.

Inferred read-only

archive_url

Capture a web page as it looks right now — screenshot and text — and anchor a hash of that capture on-chain.

Inferred read-only

get_archive

Fetch the manifest for a previous archive_url capture: when it was taken, and its proof.

Inferred read-only

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.

Inferred read-only

batch_timestamp

Anchor a Merkle root over many sha256 digests in a single transaction — far cheaper per item than notarizing each one.

Inferred read-only

service_status

Report whether anchoring is currently working.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

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

Claude Code

.mcp.json

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

Claude Desktop

Settings → Connectors → Add custom connector

Name: bsv-cx
Remote MCP URL: https://bsv.cx/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

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

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "bsv-cx": {
      "type": "http",
      "url": "https://bsv.cx/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "bsv-cx",
  "transport": "streamable-http",
  "url": "https://bsv.cx/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for bsv.cx was fetched 2026-07-26T07:22:18.037Z and is being refreshed.

Trust status Trusted

bsv.cx is assessed as Trusted: Domain has an established technology history spanning over a year.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.