Local MCP capabilities provider for Expo
Nothing to run from here
bsv.cx is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
9
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Timestamp & verify evidence on-chain, free. Proofpack: a portable BEEF+BUMP proof bundle per txid.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http bsv-cx-mcp https://bsv.cx/mcp
# 2 — ask your agent for something these tools do
# notarize_hash, verify_hash, spv_verify and 6 more
bsv.cx costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
BSAll 1 server
bsv1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http bsv-cx-mcp https://bsv.cx/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
9 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sha256 | string | yes | sha256 hex digest of the exact bytes you want to timestamp |
| label | string | no | optional public note stored with the proof |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sha256 | string | yes | the sha256 hex digest to look up |
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 t
| Parameter | Type | Required | Notes |
|---|---|---|---|
| beef | string | no | a BEEF envelope (BRC-62) as hex — easiest input; carries the tx and its merkle path |
| bump | string | no | a BUMP (BRC-74) merkle path as hex; must be paired with txid |
| txid | string | no | 64-hex txid; required with bump, or with a raw TSC proof |
| height | integer | no | block height (raw TSC proof only) |
| index | integer | no | the transaction's index in the block (raw TSC proof only) |
| nodes | array | no | TSC merkle branch nodes as hex, or "*" for a duplicated node (raw TSC proof only) |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| txid | string | yes | the confirmed transaction id to package a proof bundle for |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | the page to capture |
| thorough | boolean | no | wait for lazy-loaded content; slower but better for long or image-heavy pages |
Fetch the manifest for a previous archive_url capture: when it was taken, and its proof. Free.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| hash | string | yes | the capture hash returned by archive_url |
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).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | the page to fetch |
| thorough | boolean | no | wait for lazy-loaded content |
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).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| hashes | array | yes | sha256 hex digests to timestamp together |
Report whether anchoring is currently working. Call this if a tool reports something stored but not anchored.
No parameter schema on file.
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install bsv.cx or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.1.1.
0.1.1
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish bsv.cx can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.