Trinity MCP Frequently Asked Questions

The Trinity Insights MCP Server is a technical interface compliant with the Model Context Protocol that allows AI clients (Claude, ChatGPT, Cursor, Gemini, Windsurf, VS Code, Perplexity) to programmatically access Trinity Insights data and educational content. It is an access channel, not a separate product from the dashboard.

The canonical endpoint is https://mcp.trinityinsights.io/mcp. Transport: Streamable HTTP compliant with the MCP 2025-11-25 specification. Authentication: Authorization: Bearer YOUR_TRINITY_API_KEY.

Sign in on trinityinsights.io, open the Developer console, create a key with a descriptive name. The plaintext key is shown only once - copy it immediately into your MCP client.

No separate pricing for the MCP. The MCP access scope exactly mirrors your Trinity Insights dashboard tier (Free, Founding, Pro, Performance, Team). Tier details are on the /pricing page.

Trinity MCP supports all clients compliant with the Model Context Protocol Streamable HTTP specification: Claude Desktop, Claude Code (CLI), Cursor, ChatGPT Apps SDK, Gemini Code Assist, Windsurf, VS Code + GitHub Copilot, Perplexity Spaces. Per-client installation guides at /mcp/docs/clients/.

Five minutes maximum: create the API key + configure your MCP client + first tool call. See the Quickstart guide at /mcp/docs/quickstart.

The Free MCP tier exposes strictly the free charts of the Trinity Free dashboard - no more, no less. The tools list_metrics, get_chart_education, get_audit_status, get_glossary_term are available with a standard quota.

The Founding tier (early adopter) is equivalent to the Pro tier. Scope: full library of Trinity charts (on-chain, macro, cycle, narrative, price, exchange) + the Trinity proprietary composites + cross-rubric query + all MCP tools.

Performance adds advanced analysis features and a larger quota. Otherwise the catalog scope is identical to Pro. See /mcp/docs/tier-access for the full matrix.

60 seconds maximum (tier resolution cache TTL). You do not need to re-create your MCP key after a dashboard upgrade or downgrade.

Trinity Insights exposes a family of proprietary composite indicators across the on-chain, macro, cycle, narrative, price and exchange rubrics. Each produces a 0-100 score and an atemporal interpretive zone.

No. Trinity Insights is not a Financial Investment Advisor within the meaning of articles L.541-1 et seq. of the French Monetary and Financial Code. Trinity does not provide any personalized advice recommending a transaction on financial instruments.

No. Trinity Insights is not a Digital Asset Service Provider registered or licensed by the AMF. Trinity does not provide any of the digital asset services listed in article L.54-10-2 of the French Monetary and Financial Code.

No. Trinity Insights is not a Crypto-Asset Service Provider under Regulation (EU) 2023/1114 on markets in crypto-assets (MiCA). Trinity, as an educational analytical tool, does not fall within the scope of MiCA regulated services. See /legal/mica-status.

Mandatory TLS 1.3, HSTS preload. Authentication via HMAC-SHA256-hashed API key with pepper. Tier-aware rate limiting via distributed cache. Front WAF + reverse-proxy Origin validation. Anonymized logs with no user prompt content. See /mcp/docs/security.

The revoked key stops working within 60 seconds (cache TTL). Your MCP clients using this key will then receive a 401 error and must use another key. Revocation is irreversible.

HMAC-SHA256 hash of your API key, user identifier, tier at the time of each request, daily aggregated counters, anonymized application logs. No user prompt content is stored. No cookie is set on mcp.trinityinsights.io. See /legal/mcp-privacy.

Tier-aware quota: visitor (limited exploration), free (standard quota), founding/pro (sustained quota), performance (institutional quota), team (Performance × seats). Exact values are in the private API documentation accessible once authenticated.

1) Check that the configuration JSON is valid (single root, correct commas). 2) Check that the Authorization header contains Bearer followed by your key. 3) Fully restart your MCP client. 4) Consult your client-specific logs (e.g. ~/Library/Logs/Claude/mcp.log for Claude Desktop). 5) If the issue persists, contact [email protected].