MCP server for AI assistants

PinnFeed hosts a Model Context Protocol server so AI assistants can read live Pinnacle odds directly.

URL: https://pinnfeed.io/mcp
Transport: Streamable HTTP (spec 2025-06-18), stateless JSON responses
Auth: your PinnFeed API key as Authorization: Bearer <key> (or x-api-key, or ?key=<key> for clients that cannot send headers)
Limits: your plan's sports, data delay and rate limit. Every tool call counts as one REST request.

The dashboard fills the snippets below with your key.

Tools#

Tool	What it returns
`get_account`	Plan, sports, rate limit, daily quota, data delay, requests used today
`list_sports`	Sports with live / prematch event counts and whether each is in your plan
`search_events`	Events by sport, team or league text, live or prematch
`get_live_odds`	In-play events with prices (decimal, American, no-vig fair, margin, max stake)
`get_prematch_odds`	Upcoming events with prices, soonest first
`get_event`	One event with every market
`get_drops`	Biggest price drops in the last 1–60 minutes
`get_closing_odds`	Closing odds for an event (Builder and above)

Claude Code#

claude mcp add --transport http pinnfeed https://pinnfeed.io/mcp --header "Authorization: Bearer YOUR_KEY"

Claude (web and desktop)#

Settings → Connectors → Add custom connector. Custom connectors cannot send headers, so put the key in the URL:

https://pinnfeed.io/mcp?key=YOUR_KEY

Cursor#

~/.cursor/mcp.json (or .cursor/mcp.json in a project):

{ "mcpServers": { "pinnfeed": { "url": "https://pinnfeed.io/mcp", "headers": { "Authorization": "Bearer YOUR_KEY" } } } }

VS Code Copilot#

.vscode/mcp.json:

{ "servers": { "pinnfeed": { "type": "http", "url": "https://pinnfeed.io/mcp", "headers": { "Authorization": "Bearer YOUR_KEY" } } } }

Codex CLI#

export PINNFEED_KEY="YOUR_KEY"
codex mcp add pinnfeed --url https://pinnfeed.io/mcp --bearer-token-env-var PINNFEED_KEY

ChatGPT#

Settings → Apps & Connectors → Advanced → enable Developer mode, then create a connector with MCP server URL https://pinnfeed.io/mcp?key=YOUR_KEY and authentication "No authentication".

Raw protocol#

curl -s https://pinnfeed.io/mcp -H "Authorization: Bearer YOUR_KEY" -H "content-type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"get_drops","arguments":{"sport":"soccer","minutes":15}}}'

Tool results are JSON text. Errors (unknown sport, plan limits, rate limits) come back as a tool result with isError: true and a message the assistant can act on.

Security#

A key in a URL or a chat is a secret like any other: use a dedicated key per assistant and revoke it from the dashboard if it leaks.