MCP server · Streamable HTTP
Point Claude, Cursor, VS Code or Codex at one URL and ask in ordinary words: what is live, where a total sits, which prices just fell. Behind it are eight tools and the PinnRadar key you already have.
https://mcp.pinnradar.com/mcp · Bearer key or OAuth
01 · Why bother
A full soccer board runs to megabytes. Paste it into a chat and the model burns its budget on alternate lines nobody asked about. The MCP tools hand back only what the question needs, and say how to narrow when they cut rows.
| Pasting API output | pinnradar mcp | |
|---|---|---|
| Context cost | The entire board | Capped rows near the main line, plus a note on what was left out |
| Freshness | As old as your last paste | Live at the moment you ask |
| Quota | A request for every paste | One per tool call; identical calls in the same instant are merged |
| After a 429 | You find out by hand | Server stops calling upstream until the window resets |
| Setup | Copy and paste, forever | One config entry per client |
02 · Setup
The server is stateless Streamable HTTP, POST only. Clients that support OAuth 2.1, claude.ai among them, discover it and send you to a one-time authorisation page. Everything else sends the key as a Bearer token.
Whichever route you take, calls run on your own key and plan and appear in your dashboard beside your REST traffic. Nothing is proxied through a shared account.
For teams: commit the entry to .mcp.json with ${PINNRADAR_KEY} so each developer's key comes from their own environment. Snippets for Claude Desktop, VS Code, Codex and the Claude API are in the docs.
# key comes from your shell, not your history
claude mcp add -t http \
-H "Authorization: Bearer $PINNRADAR_KEY" \
pinnradar https://mcp.pinnradar.com/mcp
# then run /mcp: pinnradar shows 8 tools{
"mcpServers": {
"pinnradar": {
"headers": { "Authorization": "Bearer PASTE_KEY_HERE" },
"url": "https://mcp.pinnradar.com/mcp"
}
}
}03 · tools/list
Each data tool makes a live request with no cache in between and counts once against your plan, exactly like a REST call.
| Tool | Returns | Quota |
|---|---|---|
board_sports | Sports and their ids | free |
find_matches | Live or prematch events for a sport, filterable by team or league words | 1 request |
match_prices | Moneyline, spreads, totals and team totals for one match; concise mode keeps the five lines nearest the main one | 1 request |
upcoming_lines | Every alternate line of one prematch market | 1 request |
price_moves | Recent sharp falls, filtered by sport, market, period, size and age | 1 request |
feed_health | Feed health and how current the data is | 1 request |
my_usage | Plan, limits, expiry and today's count | 1 request |
search_pinnradar_docs | Answers about the API from its own reference | free |
04 · In practice
Plain language
"Totals for tonight's Serie A games" turns into find_matches followed by match_prices. The model chooses; you read.
Identity
The credential rides on the connection. The assistant neither sees it nor asks for it.
Context
Rows are capped and alternate lines centre on the main line, with a trailer telling the model how to ask for more.
Signal
The detection engine behind /api/drops is a single tool call away, with the same filters.
Billing
MCP calls are counted and shown in your dashboard alongside every other request on the key.
Help
When a parameter is unclear, the assistant can search the API reference itself without you leaving the conversation.
05 · Questions
Something not connecting? Message @PinnRadarSupport on Telegram or write to info@pinnradar.com with your client and its error.
Claude Code, Claude Desktop, claude.ai, Cursor, VS Code, the Codex CLI and the MCP connector in the Claude API. In general, any client able to reach a remote Streamable HTTP server will do. Copy-ready config for each is in the docs.
Add https://mcp.pinnradar.com/mcp as a custom connector. claude.ai opens PinnRadar's authorisation page, you type your API key once and confirm, and the connector then runs on a short-lived token that renews itself. Your key stays with PinnRadar.
No. It comes with every key, the Free plan included. Each tool call that fetches data counts as one request on your plan, so a Free key's 100 daily requests can run out in a long session; my_usage tells you what remains.
No. The key sits in the HTTP header of the connection, never in the chat. No tool takes an identity argument, and the account tool reports plan and usage only, with no email or billing data.
No. MCP works by request and response, so a tool returns the state at the moment it is called. For pushed updates, connect to the SSE drop streams or the WebSocket feed directly.
Which events are in play for a sport, the moneyline, spread and total of one match, all alternate lines of a prematch market, the largest recent drops, whether the feeds are healthy, and how much quota you have left.
Take a free key, add one config entry, and the tools appear in your client. New accounts get a three-day full demo with the paid limits, so you can test without a card.