mcpField
H
HODLXXI Read-Only

HODLXXI Read-Only

Remote
hodlxxi.comSecurity0Updated 8w ago

About HODLXXI Read-Only

HODLXXI Read-Only is a public MCP server and standalone FastMCP package for clients that need machine-readable HODLXXI trust and identity data. Its fixed, GET-only allowlist exposes 26 surfaces without write operations or access to keys, wallets, or databases.

Key features

  1. 01Expose 26 allowlisted trust surfaces
  2. 02Read agent identity, reputation, and attestations
  3. 03Retrieve and verify receipts
  4. 04Check capabilities and chain health
  5. 05Restrict access to validated GET requests

Use cases

  1. 01Inspect an agent's public reputation and attestations
  2. 02Check chain health and server capabilities
  3. 03Retrieve or verify a receipt
  4. 04Connect an MCP host to public HODLXXI data

MCP support

The public remote MCP server uses Streamable HTTP and provides 26 read-only tools without requiring an API key or OAuth. A standalone package also supports stdio and loopback-only Streamable HTTP operation.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://hodlxxi.com/agent/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

26

This tool takes no parameters.

Details

From the project README

HODLXXI Read-Only MCP

Public remote MCP server and standalone FastMCP package wrapping 26 allowlisted HODLXXI machine-readable trust surfaces.

Public remote server

Use this Streamable HTTP endpoint in any MCP host that supports remote servers:

https://hodlxxi.com/agent/mcp

No API key or OAuth flow is required. The server is public and read-only.

Machine-readable discovery:

https://hodlxxi.com/.well-known/mcp.json
https://hodlxxi.com/.well-known/agent.json
https://hodlxxi.com/agent/capabilities

A compatible client can initialize a session, list exactly 26 tools, and call tools such as:

  • hodlxxi_get_agent_discovery
  • hodlxxi_get_capabilities
  • hodlxxi_get_chain_health
  • hodlxxi_get_reputation
  • hodlxxi_get_attestations
  • hodlxxi_get_operator_continuity
  • hodlxxi_get_receipt
  • hodlxxi_verify_receipt

The canonical MCP Registry metadata is stored at the repository root in server.json under the name io.github.hodlxxi/hodlxxi-readonly.

Security boundary

  • fixed upstream origin: https://hodlxxi.com
  • fixed endpoint enum; no generic URL tool
  • GET-only access to allowlisted upstream runtime surfaces
  • redirects disabled
  • 10-second upstream timeout
  • 2 MiB response ceiling
  • JSON and application/linkset+json only
  • strict identifier and pagination validation
  • no Flask imports, database access, wallet access, LND access, keys, secrets, environment reads, payment initiation, receipt creation, or write calls
  • dedicated systemd sidecar; the Flask monolith does not execute MCP tools
  • public nginx route proxies only to the loopback sidecar

GET /agent/jobs/<job_id> and GET /agent/readiness/self-scan are intentionally excluded because they may mutate server state.

Independent validation

The remote production path has been validated from an external macOS client and through a Claude custom connector:

external client -> HTTPS -> nginx -> loopback MCP sidecar -> public HODLXXI runtime surfaces

The validation completed MCP initialization, tools/list, and live calls to capabilities, chain health, and reputation. See docs/MCP_CLIENT_VALIDATION.md.

Development

python3 -m venv .venv
. .venv/bin/activate
python -m pip install --upgrade pip
python -m pip install -e ".[test]"
pytest -q

Run over stdio

hodlxxi-mcp

Equivalent:

python -m hodlxxi_mcp

For local client configuration, point the MCP host at the virtual-environment executable and use stdio transport.

Run the sidecar over localhost Streamable HTTP

hodlxxi-mcp-http

The sidecar endpoint is fixed at:

http://127.0.0.1:8765/mcp

The sidecar transport is intentionally locked to loopback, stateless JSON responses, Host/Origin protection, and the same 26 read-only tools. Public exposure is handled separately by the hardened production reverse proxy.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.