# bsv.cx (remote · bsv.cx)

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

- Trust score: 70/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `bsv.cx`: 70/100 (this document), [markdown](https://verifymcp.io/servers/cx-bsv-bsv-cx/bsv.md), [page](https://verifymcp.io/servers/cx-bsv-bsv-cx/bsv)

## Channel facts

- Endpoint: `https://bsv.cx/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 81/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 642 tokens (~91/item across 7 items; 7 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http cx-bsv-bsv-cx https://bsv.cx/mcp
```

### Codex

```toml
[mcp_servers.cx-bsv-bsv-cx]
url = "https://bsv.cx/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cx-bsv-bsv-cx": {
      "type": "remote",
      "url": "https://bsv.cx/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add cx-bsv-bsv-cx --url https://bsv.cx/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  cx-bsv-bsv-cx:
    url: "https://bsv.cx/mcp"
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 70, +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.

### 2026-07-31 (score 69, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 69, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 68, +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.

### 2026-07-27 (score 67, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 66)

First indexed and scored.

## MCP tools (7)

### `notarize_hash` (~98 tokens)

Timestamp a hash on-chain

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.

Input parameters:

- `label` (string): optional public note stored with the proof
- `sha256` (string, required): sha256 hex digest of the exact bytes you want to timestamp

### `verify_hash` (~96 tokens)

Check an existing proof (any protocol)

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.

Input parameters:

- `sha256` (string, required): the sha256 hex digest to look up

### `archive_url` (~87 tokens)

Archive a web page with an on-chain timestamp

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.

Input parameters:

- `thorough` (boolean): wait for lazy-loaded content; slower but better for long or image-heavy pages
- `url` (string, required): the page to capture

### `get_archive` (~43 tokens)

Retrieve an archived page capture

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

Input parameters:

- `hash` (string, required): the capture hash returned by archive_url

### `verifiable_fetch` (~76 tokens)

Fetch a page with a proof of what was returned

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.

Input parameters:

- `thorough` (boolean): wait for lazy-loaded content
- `url` (string, required): the page to fetch

### `batch_timestamp` (~66 tokens)

Timestamp many hashes in one transaction

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.

Input parameters:

- `hashes` (array, required): sha256 hex digests to timestamp together

### `service_status` (~71 tokens)

Check bsv.cx availability and the free-trial pool

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.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/cx-bsv-bsv-cx/bsv#diagnostics

## Score history

- 2026-08-03: 70
- 2026-08-02: 70
- 2026-08-01: 69
- 2026-07-31: 69
- 2026-07-30: 69
- 2026-07-29: 68
- 2026-07-28: 67
- 2026-07-27: 67
- 2026-07-26: 66

## Links

- Remote endpoint: https://bsv.cx/mcp
- Website: https://bsv.cx/
- Changelog RSS feed: https://verifymcp.io/servers/cx-bsv-bsv-cx/bsv/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/cx-bsv-bsv-cx/bsv/changelog.json
- HTML version of this page: https://verifymcp.io/servers/cx-bsv-bsv-cx/bsv