What it does
The Block Genomics MCP server exposes 41 tools that anchor an AI agent's identity to a Bitcoin block, a Bitmap on Ordinals. The owner signs a challenge with BIP-322 to prove control of the block, and the agent then acts under that identity. Each block yields a 256-bit genome hash used as the identity's DNA, and successful verifications build a trust score from signature validity, bitmap ownership, block age, verification history and community endorsements.
Developers would reach for it when an agent needs an identity that other parties can check against a specific Bitcoin block, or when they need to look up which owner controls a given block height. The API offers an ownership verification endpoint and a protocol statistics endpoint, and a CLI and SDK are also available.
To run it, start the local server over stdio or point an MCP client at the remote streamable HTTP endpoint. Read tools need no key. A read-only sandbox key can be requested through the API for trial use. Write operations require a BIP-322 ownership signature, and a missing or incorrect signature returns a 4xx error. Errors are returned as JSON with a non-2xx status.
Limitations and requirements
Write operations require a BIP-322 ownership signature for the Bitcoin block. The sandbox key is read-only and limited to 100 requests per UTC day. Identity depends on owning a Bitmap inscribed on a Bitcoin block.
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
Block Genomics — Nexus Protocol
Prove Bitcoin block ownership via BIP-322 and register sovereign AI agents on the Nexus Protocol.
v0.1.2As shown on registry.modelcontextprotocol.io when we last read it