# Block Genomics — Nexus Protocol [Health: Active]

**Category:** 💰 Finance & Fintech  
**Repository:** https://github.com/BitmapAsset/block-genomics-nexus  
**GitHub Stars:** 1  
**npm Downloads (last month):** 219  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/block-genomics-nexus-protocol

## Description
Prove Bitcoin block ownership via BIP-322 and register sovereign AI agents on the Nexus Protocol.

## Claude Desktop Quick Installation
Install path inferred — verify against the README before running it. Uses `npx` (confidence: medium):

```json
"mcpServers": {
  "block-genomics-nexus-protocol": {
    "command": "npx",
    "args": ["-y","block-genomics-mcp"]
  }
}
```

## Documentation

## What Block Genomics — Nexus Protocol does

Block Genomics — Nexus Protocol provides a Bitcoin-anchored identity model for AI agents and humans. Its identity source is a Bitcoin block claimed through Bitmap ownership. The protocol uses the block's hash, height, timestamp, merkle root, and transaction data to produce a deterministic 256-bit genome. The same block produces the same genome wherever it is calculated.

The resulting genome is a 64-character hexadecimal value. It can be represented as a visual DNA helix, an 8×8 color grid, a nucleotide sequence, and a set of deterministic traits derived from hash patterns. These representations identify the underlying block rather than serving as independently generated profile data.

## How it works

An agent or person first claims a Bitcoin block through a Bitmap inscription. The protocol then generates the block's genome. To establish control, the owner signs a challenge with a Bitcoin wallet using BIP-322, which provides generic Bitcoin message signing and evidence of address control.

Successful verification contributes to a trust score. The stated factors include signature validity, Bitmap ownership, block age, verification history, and community endorsements. The protocol describes three identity tiers: direct block owners, identities linked to specific transactions, and delegated identities authorized by a higher-tier identity.

A verified block can also serve as a home parcel in the Nexus. Owners can shape terrain and objects on their blocks through signed actions, while the genome and trust score remain associated with the identity. The supplied material describes this as a setting where agents and humans can meet, transact, and build on Bitcoin-linked land.

## Tools and capabilities

The Block Genomics — Nexus Protocol repository publishes an npm package named `block-genomics-mcp`, alongside a `block-genomics-connect` package. The provided material identifies the MCP package but does not list individual MCP tool names or their input schemas.

Documented protocol capabilities include:

- Generating a deterministic genome from Bitcoin block data.
- Verifying wallet control with BIP-322 signatures.
- Associating identities with Bitmap block ownership.
- Calculating trust from verification and community-related factors.
- Representing genomes as DNA-oriented visual and data patterns.
- Using verified blocks as Nexus home parcels.

The broader project also describes an Explorer, Verify functionality, agent profiles, trust scoring, and RuneBolt. The excerpt does not specify which of these are exposed directly through the MCP package.

## Setup and configuration

The repository publishes `block-genomics-mcp` on npm, so a local MCP launch can use the package through `npx`. The supplied material does not document required environment variables, wallet configuration, command-line options, or client-specific configuration examples.

No API key, OAuth flow, or paid service requirement is identified in the provided excerpt. Wallet signing and Bitmap ownership are part of the protocol's identity process, but the excerpt does not explain how credentials are supplied to the MCP process.

Block Genomics — Nexus Protocol is described alongside a platform license of BUSL-1.1 and a separate MIT license for the protocol and SDK. The applicable license for every repository component should be checked before redistribution.

## Limitations and notes

The material does not provide an MCP tool catalog, schemas, supported client list, transport details, or a complete installation guide. It also does not establish that every capability in the wider Block Genomics project is available through MCP. Treat the package name as the documented entry point, but verify its current command behavior and configuration requirements before deploying it.

## Using this Block Genomics — Nexus Protocol MCP server
Always refer to the official documentation for the most accurate and up-to-date information on how to configure and run this server.

_Full upstream README: https://allmcps.com/mcp/block-genomics-nexus-protocol/readme_