PinnRadar Odds

Live and prematch Pinnacle odds, sharp line moves and plan usage for Claude, Cursor and any MCP client. Hosted, free API key.

Server MCP Terhosting

npx add-mcp 'https://mcp.pinnradar.com/mcp'

Terpasang ke Claude Code, Codex, Cursor, dan lainnya

Dokumentasi

Let your AI assistant read the odds.

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

Setup

Add it in a minute.

claude code · terminal

# 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

cursor ·.cursor/mcp.json

{
  "mcpServers": {
    "pinnradar": {
      "headers": { "Authorization": "Bearer PASTE_KEY_HERE" },
      "url": "https://mcp.pinnradar.com/mcp"
    }
  }
}

Tools

8

Clients

7 documented

Auth

Your API key

Extra charge

None

tools/list

Eight tools, two of them free.

Each data tool makes a live request with no cache in between and is billed as one request on your plan, the same as a REST call.

board_sports

Sports and their ids

free

find_matches

In-play or upcoming events in one sport, filterable by team or league words

1 request

match_prices

Moneylines, handicaps, over/unders 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; filter on sport, market, period, size or 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

In practice

Built for conversations.

Plain language Ask, don't code

"Totals for tonight's Serie A games" turns into find_matches followed by match_prices. The model chooses; you read.

Identity Key off the transcript

The credential rides on the connection. The assistant neither sees it nor asks for it.

Context Lean answers

Rows are capped and alternate lines centre on the main line, with a trailer telling the model how to ask for more.

Signal Drops on tap

The detection engine behind /api/drops is a single tool call away, with the same filters.

Billing Same plan, same panel

MCP calls are counted and shown in your dashboard alongside every other request on the key.

Help Docs inside the chat

When a parameter is unclear, the assistant can search the API reference itself without you leaving the conversation.

Connection

How it connects.

  1. Transport. The server is stateless Streamable HTTP, POST only.
  2. Sign-in. 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.
  3. Your own key. 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.
  4. 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.

Why bother

Raw JSON drowns a context window.

A full soccer board runs to megabytes. Drop that into a conversation and most of the context window goes 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

Context cost

The entire board

Freshness

As old as your last paste

Quota

A request for every paste

After a 429

You find out by hand

Setup

Copy and paste, forever

pinnradar mcp

Context cost

Capped rows near the main line, plus a note on what was left out

Freshness

Live at the moment you ask

Quota

One per tool call; identical calls in the same instant are merged

After a 429

Calls pause on our side until your limit window rolls over

Setup

One config entry per client

Questions

MCP questions.

Something not connecting? Message @PinnRadarSupport on Telegram or write to info@pinnradar.com with your client and its error.

Which AI clients can connect?

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.

How does sign-in work on claude.ai?

In claude.ai, add https://mcp.pinnradar.com/mcp under custom connectors. It then 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.

Is the MCP server charged separately?

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.

Does the model ever see my API key?

No. The key travels in a header on the connection and never enters the chat. No tool takes an identity argument, and the account tool reports plan and usage only, with no email or billing data.

Can the assistant stream odds?

No. MCP works by request and response, so a tool returns the state at the moment it is called. For pushed updates, your own code should hold a WebSocket feed or SSE drop stream connection.

What kinds of questions work well?

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.