MCP.so
登录

bsv.cx MCP Server已验证已精选

@Andy Rowe

基本信息

传输方式

Streamable HTTP

认证方式

无需认证

分类

AI 与智能体

作者

Andy Rowe

提交者

Andy Rowe

关于 bsv.cx MCP Server

Timestamp and verify evidence on-chain. Let your agent prove what it saw and when. bsv.cx gives an AI agent verifiable memory. Timestamp a hash of any output, archive a web page as it looked, or fetch a URL with a receipt proving what came back — each anchored in a Bitcoin SV transaction. Verification is free and needs no trust in bsv.cx: anyone can check the proof on any explorer.

#provenance#timestamping#notary#verification#blockchain#archival#web-capture#bitcoin-sv

连接信息

https://bsv.cx/mcp

接入方式

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

bsv.cx MCP Server 工具

9

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.

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.

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.

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).

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.

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

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).

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).

Report whether anchoring is currently working. Call this if a tool reports something stored but not anchored.

概览

An agent that summarises a page, cites a source, or produces an artifact has no way to demonstrate later that the input was real and unaltered. "I read it on Tuesday" is not evidence.

bsv.cx turns that into something a third party can check:

  • notarize_hash — prove a document or output existed at a point in time WITHOUT revealing it. You hash the content yourself and send only the digest; bsv.cx never sees what was hashed.
  • archive_url — capture a web page as it looks right now and anchor a hash of that capture, so a later edit or deletion cannot be denied.
  • verifiable_fetch — fetch a URL as readable text plus a receipt committing to the exact bytes returned.
  • batch_timestamp — anchor a Merkle root over many hashes in one transaction.
  • verify_hash / get_archive — check any existing proof. Always free.
  • service_status — availability and remaining free-trial calls.

Every proof is a real Bitcoin SV transaction. You do not have to trust bsv.cx to check one — read the transaction on any explorer.

What a timestamp proves: those exact bytes existed no later than that block. What it does NOT prove: who made them, that they are true, or that they are original. Anyone can timestamp anything, including someone else's work.

Free to start: notarize and archive are free; the metered tools include free trial calls.

常见问题

1

bsv.cx 远程 MCP 服务器是什么?

bsv.cx 的远程 MCP 服务器是一个托管的 Model Context Protocol 端点,地址是 https://bsv.cx/mcp,AI 助手无需在本地安装或运行任何东西即可连接。

2

怎么连接 bsv.cx 的 MCP 服务器?

把端点 https://bsv.cx/mcp 添加到任意支持 MCP 的客户端,比如 Claude Code、Cursor 或 VS Code。本页的接入代码块可以一步配置好每个客户端。

3

bsv.cx 的 MCP 服务器需要认证吗?

不需要。bsv.cx 的 MCP 服务器不需要认证——直接用端点地址连接即可。

4

bsv.cx 的 MCP 服务器用的是哪种传输方式?

bsv.cx 暴露的是 Streamable HTTP 端点,这是远程 MCP 服务器普遍使用、主流客户端都支持的传输方式。

评论