Learning Resources

cryptoinfra.build

An MCP server that exposes a searchable documentation library, letting clients list doc topics, run ranked section-level searches, fetch complete Markdown pages by slug, and get step-by-step integration guides.

1 endpoint4 known toolsFirst detected October 14, 2026Last detected October 14, 2026

ENDPOINT 1

https://docs.cryptoinfra.build/mcp

No auth detected

MCP server metadata

Name: cryptoinfra-docs
Version: 1.0.0

Capabilities

loggingtools.listChangedresources.listChangedcompletionsprompts.listChanged

Server instructions

Documentation for the cryptoinfra crypto payments API — a public, read-only knowledge source. This server serves documentation ONLY. It cannot read balances, create payments, issue cards or move funds, and it holds no credential. Never put an API key, webhook secret, customer personal data or a production payload into a tool argument. Suggested workflow: 1. get_integration_guide for the pattern you are building (deposits-and-balances, payouts, swap-and-exchange, cards, webhooks). 2. Read every page the guide lists, in order, via resources/read on docs://cryptoinfra/{slug} or get_doc. 3. search_docs for anything framework-specific or not covered by those pages. 4. Review the finished integration with the review-cryptoinfra-integration prompt. Two facts that catch out most integrations: amounts are returned both as a human decimal string and as an exact integer *_base string (do arithmetic on *_base with BigInt), and swaps, exchanges and INR buy orders emit NO webhook at all — those must be polled to a terminal state. Check the docs for the current event list rather than assuming an event exists.

Known tools 4

list_docs

Every documentation topic with its slug, title, summary and resource URI.

Inferred read-only

search_docs

Ranked SECTION-level search.

Inferred read-only

get_doc

One page's complete portable Markdown, by slug.

Inferred read-only

get_integration_guide

A build plan for one integration pattern: the pages to read in order, why each one matters, and the conventions that break integrations here.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.cryptoinfra-docs]
url = "https://docs.cryptoinfra.build/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "cryptoinfra-docs": {
      "type": "http",
      "url": "https://docs.cryptoinfra.build/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: cryptoinfra-docs
Remote MCP URL: https://docs.cryptoinfra.build/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "cryptoinfra-docs": {
      "url": "https://docs.cryptoinfra.build/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "cryptoinfra-docs": {
      "type": "http",
      "url": "https://docs.cryptoinfra.build/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "cryptoinfra-docs",
  "transport": "streamable-http",
  "url": "https://docs.cryptoinfra.build/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.