What it does
TapeAPI is a signed API layer for TapeOut. Each response carries a signed receipt that records which holder answered, which request was answered, the returned bytes, and the claimed token usage and price, so anyone can check it. The MCP endpoint exposes eight read methods covering BNB Chain balances, tokens, NFTs, prices and TapeOut names, and each result includes a receipt.
It suits developers who need to confirm that a chain read or an AI answer came from a named signer and matches the request that was sent. Receipts show who signed and what was said. They do not show which model actually ran, so they establish accountability rather than correctness.
Clients such as Claude or Cursor can connect to the hosted endpoint, which is free and needs no sign-up. Verifying receipts locally requires Node.js 22 or later, and the SDK is installed from GitHub Release files rather than npm. Self-hosting the MCP signing proxy is also supported.
Limitations and requirements
Receipts prove only what the signer stated; they do not show which model ran or whether the signer is honest. Hosted contracts are unaudited and not deployed, and no third-party audit of the code has been carried out. Requires Node.js 22 or later. The SDK is not on npm and must be installed from GitHub Release archives. Some features are experimental and fall outside compatibility promises. Streamed receipts in versions 1.0.0 to 1.4.0 could show truncated or injected streams as verified under certain chunking; this was fixed in 1.5.0.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
TapeAPI: signed BNB Chain reads
Signed BNB Chain reads (balances, tokens, NFTs, prices, TapeOut names) with verifiable receipts
v1.0.0As shown on registry.modelcontextprotocol.io when we last read it