Skip to content

MCP server

The Trinity Insights Model Context Protocol server exposes Bitcoin analytical data (on-chain, macro, cycle, narrative) directly to MCP-compatible AI agents. Canonical endpoint : https://mcp.trinityinsights.io/mcp

Transport & protocol

  • Transport - Streamable HTTP (covers the major MCP clients).
  • Protocol version - 2025-11-25
  • Authentication Bearer token, derived from a Trinity API key ( Authorization: Bearer ... header).
  • Native bilingual optional language fr or en (default fr).

Compatible MCP clients

Any MCP client supporting Streamable HTTP transport with Bearer authentication can connect. Trinity Insights is tested against the following clients :

  • Claude Desktop · Claude Code (CLI) · Claude (anthropic.com)
  • Cursor · Windsurf · VS Code Copilot
  • ChatGPT Apps SDK
  • Gemini Code Assist
  • Perplexity Spaces

Generic configuration

The configuration pattern is identical for most MCP clients. Here is the canonical JSON block :

{
  "mcpServers": {
    "trinity-insights": {
      "transport": "streamable-http",
      "url": "https://mcp.trinityinsights.io/mcp",
      "headers": {
        "Authorization": "Bearer $TRINITY_API_KEY"
      }
    }
  }
}

Exposed surface

  • Tools - actions the agent can invoke (metric query, cycle comparison, etc.).
  • Resources - reference resources (compliance disclaimer, catalog, glossary, etc.).
  • Prompts - Trinity-curated prompts, ready to invoke (typical briefings).

The exhaustive list of tools, resources and prompts is served at runtime by the MCP server via the initial handshake. Any compatible client can enumerate them.

Tier access

Capabilities accessible via MCP strictly follow the API key's subscription tier. No divergence between the dashboard surface and the MCP surface — a Pro account sees the same library on both. See the pricing grid for the per-tier feature breakdown.

Security

  • Strict TLS + HSTS preload on mcp.trinityinsights.io.
  • API keys stored hashed (HMAC-SHA256 with server-side pepper).
  • Per-tier rate limiting (dedicated Redis).
  • Append-only call logs with hashed arguments (PII-safe).
  • Origin validation + strict Content-Security-Policy.

MiCA + AMF compliance

Every MCP response includes a compliance block carrying the institutional disclaimer and the non-CASP attestation under Regulation (EU) 2023/1114. Response vocabulary respects AMF discipline. See the full MiCA status.

Institutional disclaimer

Trinity Insights is an educational and analytical tool. Content does not constitute investment advice. Trinity Insights is not a Crypto-Asset Service Provider (CASP) registered under MiCA Regulation (EU) 2023/1114, nor a Financial Investment Advisor (CIF), nor a PSAN. See the full disclaimer.