bsv.cx認証済み注目
@Andy Rowe
bsv.cx について
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.
接続情報
https://bsv.cx/mcpセットアップ
claude mcp add bsv-cx --transport http https://bsv.cx/mcpツール
7Anchor 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 previously notarized sha256 and return when it was timestamped and the transaction that proves it. Free, and never rate-limited into unavailability — verifying a proof must always work.
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. 3 free calls, then priced per call.
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. 3 free calls, then priced per call.
Report whether anchoring is currently working and how much of the free trial remains. 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.
よくある質問
bsv.cx のリモート MCP サーバーとは何ですか?
bsv.cx のリモート MCP サーバーは、https://bsv.cx/mcp にホストされた Model Context Protocol エンドポイントです。AI アシスタントはローカルに何もインストール・実行することなく接続できます。
bsv.cx の MCP サーバーにはどう接続しますか?
エンドポイント https://bsv.cx/mcp を Claude Code、Cursor、VS Code など任意の MCP 対応クライアントに追加してください。このページのセットアップ手順で各クライアントを一度に設定できます。
bsv.cx の MCP サーバーは認証が必要ですか?
いいえ。bsv.cx の MCP サーバーは認証不要です——エンドポイント URL で直接接続できます。
bsv.cx の MCP サーバーはどのトランスポートを使用しますか?
bsv.cx は Streamable HTTP エンドポイントを公開しており、これはリモート MCP サーバーで広く使われ、主要な MCP クライアントがサポートするトランスポートです。
基本情報
コメント