Xtract MCP
Connect AI tools to Xtract.
Connect ChatGPT, Claude, Grok, Claude Code, MCP Inspector, the OpenAI API, or your own app to validated Litecoin data from Xtract.
Page Sections
Connection
Endpoint
POST https://forcex.com/xtract/mcp
Use the hosted MCP endpoint above. Every tool returns validated Litecoin data and uses the same Xtract credits, limits, and account controls as the REST API — MCP is an access path to Xtract, not a separate plan.
Technical details
Model Context Protocol 2025-06-18 over Streamable HTTP (JSON-RPC 2.0). The server replies with a single JSON response (no streaming) and exposes the tools capability. Browse every tool in the MCP tool reference.
Authentication
Choose the connection method that fits your client.
Hosted connectors
ChatGPT, Claude, and Grok use OAuth. Enter https://forcex.com/xtract/mcp; the connector handles registration and sends you through ForceX sign-in and consent. You can revoke access any time from your account under Connected Apps.
Developer tools
Claude Code, MCP Inspector, the OpenAI API, and your own server-side apps can use an fx_live_ Xtract API key in the Authorization header. Never put an API key in a browser or end-user app — use a hosted connector (OAuth) for those.
OAuth discovery details
Connectors discover everything automatically. For reference:
- Protected resource:
https://forcex.com/.well-known/oauth-protected-resource— resourcehttps://forcex.com/xtract/mcp, scopextract:read. - Authorization server:
https://auth.forcex.com— authorize/oauth-as/authorize, token/oauth-as/token, register/oauth-as/register. - PKCE
S256, public clients, scopesxtract:read+offline_access. - Access tokens are RS256 and expire after 15 minutes (
expires_in: 900); refresh tokens keep the connection alive until you revoke it.
ChatGPT
Add a connector pointing at https://forcex.com/xtract/mcp. ChatGPT registers itself, then sends you through ForceX sign-in and consent (approve read access). The Xtract tools then appear in your chats.
Claude
Add a custom connector in Claude with the same URL, https://forcex.com/xtract/mcp. Claude runs the same sign-in and consent flow, then lists the Xtract tools.
Grok
In Grok, open Connectors, choose New Connector → Custom, and enter https://forcex.com/xtract/mcp. Grok registers itself, then runs ForceX sign-in and consent; approve read access and the Xtract tools appear in your chats.
MCP Inspector
Use the Streamable HTTP transport with the URL https://forcex.com/xtract/mcp. Either add an Authorization: Bearer fx_live_… header, or let Inspector run the OAuth flow. Then list and call the tools.
Claude Code
Add Xtract as a remote MCP server with your Xtract API key — no browser sign-in needed:
claude mcp add --transport http forcex-xtract https://forcex.com/xtract/mcp \
--header "Authorization: Bearer fx_live_<your-key>"
The key is stored in plaintext in your Claude Code config, so treat that file as a secret.
OpenAI API
Add Xtract as an mcp tool in the Responses API and pass your Xtract key in the tool's headers:
{
"type": "mcp",
"server_label": "forcex-xtract",
"server_url": "https://forcex.com/xtract/mcp",
"headers": { "Authorization": "Bearer fx_live_…" },
"require_approval": "never"
}
Technical details
Put the API key in the nested headers.Authorization. If you instead hold an OAuth access token, the Responses API also accepts a top-level authorization field — don't send both for the same tool.
Your own apps
For a first-party, server-to-server app, send Authorization: Bearer fx_live_… on https://forcex.com/xtract/mcp. For a third-party app acting for a ForceX user, use the OAuth hosted-connector flow instead of embedding a key.
Trust & safety
readOnlyHint=false, openWorldHint=false, destructiveHint=false).
Connections you approve for ChatGPT, Claude, or Grok appear in your ForceX account under Connected Apps, where you can revoke them at any time. Usage, credits, and rate limits are billed to your Xtract plan exactly as REST calls.
Every successful tool result is an answer-first structuredContent contract whose citations array carries the full visible citation, plus a plain-text answer card ending in a ready-made source line — see How to cite ForceX MCP results.