Agent setup

Machines get the same facts humans get, in the same shapes, with the same source records. Agents must cite pages, admit when the documentation does not answer, and never present an unreleased feature as live. Nothing here can trade, sign, or move funds: the MCP server is read-only by construction.

Corpus files

llms.txt

Point an agent at the index of the corpus. It lists every page with its address and purpose.

https://bitcoinuniverseio.github.io/docs-stampdex/llms.txt

Full corpus

One Markdown document containing every page, with source verification records preserved.

https://bitcoinuniverseio.github.io/docs-stampdex/llms-full.txt

Page index (JSON)

A compact machine index: id, title, description, content type, audience, risk level, and the Markdown address of each page.

https://bitcoinuniverseio.github.io/docs-stampdex/index.json

Per-page Markdown

Every page has a clean Markdown representation at /markdown/<id>. The View as Markdown action on each page links to it.

https://bitcoinuniverseio.github.io/docs-stampdex/markdown/concepts/custody

OpenAPI document

The public API contract, generated in the application repository and snapshotted here. Discoverable also at /.well-known/api-catalog.

https://bitcoinuniverseio.github.io/docs-stampdex/api/downloads/openapi.json

MCP server

@bitcoinuniverse/stampdex-docs-mcp is a versioned, read-only MCP package. Tools: stampdex_docs_search, stampdex_docs_get_page, stampdex_docs_get_section, stampdex_docs_get_api_operation, stampdex_docs_get_release, stampdex_docs_get_capability, stampdex_docs_get_wallet_support, stampdex_docs_get_screenshot_evidence. It serves a built copy of this site, so the tools answer from the same snapshot a reader sees.

{
  "mcpServers": {
    "stampdex-docs": {
      "command": "npx",
      "args": ["-y", "@bitcoinuniverse/stampdex-docs-mcp"],
      "env": { "DOCSDIR": "/path/to/docs-stampdex/dist" }
    }
  }
}

Example: Claude Code

In Claude Code, add the MCP server with the configuration above, then ask:

  What does StampDEX say about where my BTC sits while an SRC-20 trade settles?

The honest answer comes from stampdex_docs_get_section with id concepts/custody;
check that every claim the agent makes traces to a page it can cite.

Exact limitations

• The server is read-only. There is no tool that writes, signs, or broadcasts.
• It serves the built documentation only; private repositories are unreachable.
• Release claims are only as current as the build it serves; verify with GET /api/version.
• Prices and predictions are out of scope everywhere on this site, including here.