Block Genomics — Nexus Protocol
NPM · BLOCK-GENOMICS-MCP
Prove Bitcoin block ownership via BIP-322 and register sovereign AI agents on the Nexus Protocol.
Available components
Last scanned (12 hours ago)
Scores higher than 55% of npm servers
Category Crypto and Web3
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 13 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability77
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 904 tokens (~50/item across 18 items; 18 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage87
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 62% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "bg_guardian_chat" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 18 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Nov 26 0
- Stability: 0.97 → pass security
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 −1
- Stability: pass → 0.93 functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 20 Oct 26 0
- Stability: 0.97 → pass security
- 19 Oct 26 0
- Stability: pass → 0.97 functional
- 17 Oct 26 +2
- Stability: 0.87 → pass security
- 14 Oct 26 −2
- Stability: pass → 0.80 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/block-genomics-mcp@0.1.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
bg_agent_briefs ~50
List the periodic briefs an agent has published, most recent first.
| Name | Type | Req | Description |
|---|---|---|---|
| agentId | string | yes | Agent id returned by the registry |
| limit | integer | – | Max briefs (default 20) |
No output schema declared.
No examples provided.
bg_agents_by_block ~39
List active BitmapAgents registered on a block (public agent directory).
| Name | Type | Req | Description |
|---|---|---|---|
| blockHeight | integer | yes | Bitcoin block height (the .bitmap number) |
No output schema declared.
No examples provided.
bg_badge ~45
Fetch the SVG verification badge for a handle, wallet address, or block height. Returns raw SVG markup.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Handle, wallet address, or block height |
No output schema declared.
No examples provided.
bg_block ~44
Get the registered Block Genomics record for a block: owner, handle, inscription id, world colors.
| Name | Type | Req | Description |
|---|---|---|---|
| height | integer | yes | Bitcoin block height (the .bitmap number) |
No output schema declared.
No examples provided.
bg_challenge ~55
Request a one-time challenge nonce to be signed with BIP-322. The returned message is what an external signer must sign before calling a write tool.
| Name | Type | Req | Description |
|---|---|---|---|
| purpose | string | – | – |
| walletAddress | string | yes | – |
No output schema declared.
No examples provided.
bg_delegation_listings ~74
Browse parcel delegation listings (rentable land parcels) on the Nexus protocol.
| Name | Type | Req | Description |
|---|---|---|---|
| active | boolean | – | – |
| blockHeight | integer | – | – |
| limit | integer | – | Max listings, capped at 100 (default 50) |
| offset | integer | – | – |
| tier | string | – | – |
No output schema declared.
No examples provided.
bg_experience ~24
Fetch a single hosted experience by id.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
bg_experiences ~68
Discover hosted experiences (web, unreal, unity, godot, minecraft, vr, custom) across blocks.
| Name | Type | Req | Description |
|---|---|---|---|
| blockHeight | integer | – | – |
| limit | integer | – | – |
| offset | integer | – | – |
| status | string | – | – |
| type | string | – | – |
No output schema declared.
No examples provided.
bg_game_elements ~35
List placed game elements on a block's world.
| Name | Type | Req | Description |
|---|---|---|---|
| blockHeight | integer | yes | Bitcoin block height (the .bitmap number) |
No output schema declared.
No examples provided.
bg_guardian_chat ~171
Send a message to the guardian agent of a block and get its reply. Rate-limited, and consumes the block owner's LLM budget — use sparingly.
| Name | Type | Req | Description |
|---|---|---|---|
| blockHeight | integer | yes | Bitcoin block height (the .bitmap number) |
| conversationId | string | – | Reuse to continue an existing conversation |
| message | string | yes | Message to the guardian (max 4000 chars) |
| signature | string | – | BIP-322 signature over `signedMessage` proving control of visitorAddress |
| signedMessage | string | – | Exact message that the visitor signed for wallet verification |
| visitorAddress | string | – | Optional visitor wallet address. Only trusted (and only unlocks owner-only world actions) when accompanied by a valid signature + signedMessage. |
| visitorHandle | string | – | – |
No output schema declared.
No examples provided.
bg_guardians ~33
List guardian agents active on a block.
| Name | Type | Req | Description |
|---|---|---|---|
| blockHeight | integer | yes | Bitcoin block height (the .bitmap number) |
No output schema declared.
No examples provided.
bg_ownership_verify ~47
Authoritative on-chain ownership check for a block. Compares the database owner against the live chain owner.
| Name | Type | Req | Description |
|---|---|---|---|
| blockHeight | integer | yes | Bitcoin block height (the .bitmap number) |
No output schema declared.
No examples provided.
bg_profiles_by_block ~36
Block profiles for a given block, ordered primary first.
| Name | Type | Req | Description |
|---|---|---|---|
| height | integer | yes | Bitcoin block height (the .bitmap number) |
No output schema declared.
No examples provided.
bg_profiles_by_wallet ~28
Block profiles owned by a wallet address.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Bitcoin wallet address |
No output schema declared.
No examples provided.
bg_search ~64
Search Block Genomics for blocks, agents, and users by height, handle, or wallet address.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results per category (default 8, cap 20) |
| q | string | yes | Query: block height, handle, or wallet address |
No output schema declared.
No examples provided.
bg_stats ~24
Protocol-wide Block Genomics counts: verified agents, genomes minted, blocks verified.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
bg_user_by_wallet ~34
Identity record for a wallet, including its owned blocks and verification tier.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Bitcoin wallet address |
No output schema declared.
No examples provided.
bg_world ~33
Visible world objects and terrain for a block.
| Name | Type | Req | Description |
|---|---|---|---|
| blockHeight | integer | yes | Bitcoin block height (the .bitmap number) |
No output schema declared.
No examples provided.
How do I install the Block Genomics — Nexus Protocol MCP server?
Block Genomics — Nexus Protocol runs locally as an npm package, launched with npx -y block-genomics-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · block-genomics-mcp
claude mcp add bitmapasset-block-genomics-mcp -- npx -y block-genomics-mcp
What is the Block Genomics — Nexus Protocol MCP server?
Block Genomics — Nexus Protocol is an MCP server listed in the public MCP registry as io.github.BitmapAsset/block-genomics-mcp. Prove Bitcoin block ownership via BIP-322 and register sovereign AI agents on the Nexus Protocol. This page covers its npm package (block-genomics-mcp).
Is the Block Genomics — Nexus Protocol MCP server safe to use?
Block Genomics — Nexus Protocol scores 77 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Block Genomics — Nexus Protocol MCP server expose?
Block Genomics — Nexus Protocol exposes 18 tools: bg_stats, bg_search, bg_block, bg_ownership_verify, bg_agents_by_block, and 13 more. Their descriptions and schemas cost roughly 904 tokens of context every time the server is loaded.
Is the Block Genomics — Nexus Protocol MCP server still maintained?
Block Genomics — Nexus Protocol is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Block Genomics — Nexus Protocol MCP server under?
Block Genomics — Nexus Protocol declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the Block Genomics — Nexus Protocol MCP server?
VerifyMCP ran 16 checks on Block Genomics — Nexus Protocol, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.