bsv.cx
REMOTE · BSV.CX · SCANNED SEP 20
Timestamp & verify evidence on-chain, free. Proofpack: a portable BEEF+BUMP proof bundle per txid.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 9 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability75
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1171 tokens (~130/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the bsv.cx MCP server?
bsv.cx is a hosted endpoint at https://bsv.cx/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · bsv.cx
claude mcp add --transport http cx-bsv-bsv-cx 'https://bsv.cx/mcp'
{
"mcpServers": {
"cx-bsv-bsv-cx": {
"url": "https://bsv.cx/mcp"
}
}
} {
"servers": {
"cx-bsv-bsv-cx": {
"type": "http",
"url": "https://bsv.cx/mcp"
}
}
} [mcp_servers.cx-bsv-bsv-cx] url = "https://bsv.cx/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"cx-bsv-bsv-cx": {
"type": "remote",
"url": "https://bsv.cx/mcp",
"enabled": true
}
}
} openclaw mcp add cx-bsv-bsv-cx --url 'https://bsv.cx/mcp' --transport streamable-http
mcp_servers:
cx-bsv-bsv-cx:
url: "https://bsv.cx/mcp" {
"McpServers": {
"cx-bsv-bsv-cx": {
"Transport": "http",
"Url": "https://bsv.cx/mcp"
}
}
} assistant mcp add cx-bsv-bsv-cx -t streamable-http -u 'https://bsv.cx/mcp'
{
"mcpServers": {
"cx-bsv-bsv-cx": {
"type": "http",
"url": "https://bsv.cx/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 2 Sept 26 −2
- MCP protocol: pass → fail ▼ functional
- MCP protocol version: 2025-11-25 → 2025-06-18 functional
- 31 Aug 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 974 → 1171 ▼ functional
- Server version: 0.1.0 → 0.1.1 functional
- New tool “proofpack” functional
- 28 Aug 26 0
- Schema quality: pass → fail ▼ functional
- New tool “spv_verify” functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Aug 26 0
- Tool “batch_timestamp” rewrote its description, which is the text the model reads security
- Tool “service_status” rewrote its description, which is the text the model reads security
- Tool “verifiable_fetch” rewrote its description, which is the text the model reads security
- Tool “service_status” changed its title: Check bsv.cx availability and the free-trial pool → Check bsv.cx availability cosmetic
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://bsv.cx/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=bsv.cx | CN=WE1,O=Google Trust Services,C=US | 14 Aug 2026 | 12 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 8955afa85b4455440e5e6e869f1df47e |
| SANs: bsv.cx, *.bsv.cx | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of bsv.cx. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| cx. | present | 6500 | 8 | Verified |
| bsv.cx. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| content-security-policy | default-src 'self'; script-src 'self' 'sha256-Y9cfjpA7WPNEED81oDbBwLfp/Lj2TG02O8XPor1zOmQ=' 'sha256-t2NDBWEOAO5c/8RKdiKSuGKtcGPEtAKEqWopaLZWDQk=' 'sha256-h+Cz8J8tFkpEgjs1j0zS6Krf+m4tl4UmVzR4G2U5h3A=' 'sha256-mhcpGY3XKT8I5E9pfE177nXcYmA7XH62jfapPtXarNk=' 'sha256-BnfvoYWQ0a7bFsG+tAWyJKw3w4ZBXhIBqXQg6LF2Bj4=' 'sha256-FAzO5TMcndfNK+4Y9K60WxZAmOOhQk/0onJT7Tl9uww='; style-src 'self' 'unsafe-inline'; img-src 'self' data:; font-src 'self' data:; connect-src 'self'; base-uri 'self'; form-action 'self'; frame-ancestors 'self'; object-src 'none' |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://bsv.cx/mcp | Verified | 200 | |
| http (plaintext) | http://bsv.cx/mcp | HTTPS enforced | 308 | https://bsv.cx/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
archive_url Archive a web page with an on-chain timestamp ~87
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.
| Name | Type | Req | Description |
|---|---|---|---|
| thorough | boolean | – | wait for lazy-loaded content; slower but better for long or image-heavy pages |
| url | string | yes | the page to capture |
No output schema declared.
No examples provided.
batch_timestamp Timestamp many hashes in one transaction ~74
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).
| Name | Type | Req | Description |
|---|---|---|---|
| hashes | array | yes | sha256 hex digests to timestamp together |
No output schema declared.
No examples provided.
get_archive Retrieve an archived page capture ~43
Fetch the manifest for a previous archive_url capture: when it was taken, and its proof. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| hash | string | yes | the capture hash returned by archive_url |
No output schema declared.
No examples provided.
notarize_hash Timestamp a hash on-chain ~98
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.
| Name | Type | Req | Description |
|---|---|---|---|
| label | string | – | optional public note stored with the proof |
| sha256 | string | yes | sha256 hex digest of the exact bytes you want to timestamp |
No output schema declared.
No examples provided.
proofpack Get a portable, pre-verified proof bundle for a transaction ~172
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).
| Name | Type | Req | Description |
|---|---|---|---|
| txid | string | yes | the confirmed transaction id to package a proof bundle for |
No output schema declared.
No examples provided.
service_status Check bsv.cx availability ~28
Report whether anchoring is currently working. Call this if a tool reports something stored but not anchored.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
spv_verify Verify any Bitcoin proof against bsv.cx's own headers ~285
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.
| Name | Type | Req | Description |
|---|---|---|---|
| beef | string | – | a BEEF envelope (BRC-62) as hex — easiest input; carries the tx and its merkle path |
| bump | string | – | a BUMP (BRC-74) merkle path as hex; must be paired with txid |
| height | integer | – | block height (raw TSC proof only) |
| index | integer | – | the transaction's index in the block (raw TSC proof only) |
| nodes | array | – | TSC merkle branch nodes as hex, or "*" for a duplicated node (raw TSC proof only) |
| txid | string | – | 64-hex txid; required with bump, or with a raw TSC proof |
No output schema declared.
No examples provided.
verifiable_fetch Fetch a page with a proof of what was returned ~84
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).
| Name | Type | Req | Description |
|---|---|---|---|
| thorough | boolean | – | wait for lazy-loaded content |
| url | string | yes | the page to fetch |
No output schema declared.
No examples provided.
verify_hash Check an existing proof (any protocol) ~96
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.
| Name | Type | Req | Description |
|---|---|---|---|
| sha256 | string | yes | the sha256 hex digest to look up |
No output schema declared.
No examples provided.
What is the bsv.cx MCP server?
bsv.cx is an MCP server listed in the public MCP registry as cx.bsv/bsv-cx. Timestamp & verify evidence on-chain, free. Proofpack: a portable BEEF+BUMP proof bundle per txid. This page covers its hosted endpoint (https://bsv.cx/mcp).
Is the bsv.cx MCP server safe to use?
bsv.cx scores 79 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the bsv.cx MCP server expose?
bsv.cx exposes 9 tools: notarize_hash, verify_hash, spv_verify, proofpack, archive_url, and 4 more. Their descriptions and schemas cost roughly 967 tokens of context every time the server is loaded.
Does the bsv.cx MCP server require authentication?
No. We connected to bsv.cx without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the bsv.cx MCP server still maintained?
bsv.cx is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.