bsv.cx
REMOTE · BSV.CX · SCANNED AUG 3
Timestamp and verify evidence on-chain. Prove what your agent saw and when; verifying is free.
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 →
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 7 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 Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 642 tokens (~91/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · bsv.cx
claude mcp add --transport http cx-bsv-bsv-cx 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": {
"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 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 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
- 30 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 66
First indexed and scored.
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 3 Aug 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=YE1,O=Let's Encrypt,C=US | 21 Jul 2026 | 19 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 507bb9fd731cb69fe3f7428aca5722ee643 |
| SANs: bsv.cx | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
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 |
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.
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 ~66
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.
| 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.
service_status Check bsv.cx availability and the free-trial pool ~71
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
verifiable_fetch Fetch a page with a proof of what was returned ~76
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.
| 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.