Home / MCP registry index / io.github.hodlxxi/hodlxxi-readonly

HODLXXI Read-Only

io.github.hodlxxi/hodlxxi-readonly in the official MCP registry. Endpoint https://hodlxxi.com/agent/mcp. Source: github.com/hodlxxi/Universal-Bitcoin-Identity-Layer.

The registry describes it as: Public read-only MCP server for HODLXXI agent identity, trust, receipts, and verification.

We read its 26 tools on 2026-10-29. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http hodlxxi-readonly https://hodlxxi.com/agent/mcp

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "hodlxxi-readonly": {
      "url": "https://hodlxxi.com/agent/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"hodlxxi-readonly","type":"http","url":"https://hodlxxi.com/agent/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which. The free lazaretto-guard plugin reads a server's tools the moment Claude Code adds it and asks you if one of our rules matches.

Tools it advertises

hodlxxi_get_agent_identity hodlxxi_get_operator_continuity hodlxxi_get_api_catalog hodlxxi_get_agent_skills_index hodlxxi_get_mcp_server_card hodlxxi_get_nostr_dm_policy hodlxxi_get_openid_configuration hodlxxi_get_oauth_authorization_server hodlxxi_get_oauth_protected_resource hodlxxi_get_jwks hodlxxi_get_agent_discovery hodlxxi_get_capabilities hodlxxi_get_capabilities_schema hodlxxi_get_skills hodlxxi_get_marketplace_listing hodlxxi_get_reputation hodlxxi_get_attestations hodlxxi_get_trust_events hodlxxi_get_nostr_announcement hodlxxi_get_chain_health hodlxxi_get_covenant_countdown hodlxxi_get_trust_summary hodlxxi_get_covenant hodlxxi_get_report hodlxxi_verify_receipt hodlxxi_get_receipt

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-hodlxxi-hodlxxi-readonly/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-hodlxxi-hodlxxi-readonly)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.