MCP.Market

Football Odds History MCP server

online · 100% uptime
by pipeworx-io·io.github.pipeworx-io/football-odds-history·v0.2.1

football-odds-history — historical football (soccer) results and odds from sportsbooks, sourced…

B77/100grade B
What users say
No reviews yet
Be the first
Safety scan
B77/100

not scanned yet

Adoption
Growing

0 stars

Reviews

Write one

Nobody has reviewed Football Odds History yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Football Odds History tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Not scanned yet. New listings are scanned within a day or two of arriving.

How Football Odds History compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
77/100
higher than 50% of 48,255 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
80 ms
faster than 88% of 30,031 servers

Release history: 3 versions in the registry since 2026-10-13, latest 2026-11-02, typically one every 11 days.

Install Football Odds History in Claude Code, Cursor or VS Code

claude mcp add --transport http football-odds-history https://gateway.pipeworx.io/football-odds-history/mcp
Add to Cursor

What the publisher says

From the Football Odds History repository's README, as published. We do not edit it. Read it on GitHub

@pipeworx/football-odds-history

Historical football (soccer) match results and odds from sportsbooks — 1X2, over/under 2.5 goals, and Asian handicap — for 22 main European leagues back to 1993/94 and 16 further countries back to roughly 2012/13.

Part of Pipeworx — an MCP gateway connecting AI agents to 1779+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.

Tools

and file layout (main leagues: one file per season; extra leagues: one file spanning all seasons).

  • listoddsleagues() — every league code this pack covers, with name, country

— results and odds for one league + season (season is required for the 22 main leagues; optional for the 16 extra-league countries, whose single file already spans every season). Optional team / date filters.

  • matchodds(league, season?, team?, datefrom?, date_to?, limit?, bookmakers?)

results and odds across multiple seasons of a single league, newest first. Defaults to the 5 most recent seasons for a main league if seasons is not given.

  • team_results(team, league, seasons?, limit?, bookmakers?) — one team's

Response size. A full season is 380 matches, and the full odds detail for one match (every bookmaker, opening and closing) runs to several KB — too much to hand a model by default. Both tools default to a compact shape: closing 1X2 from Pinnacle, Bet365 and the market average/max; the market's closing over/under 2.5; and the Asian handicap closing line (the number, not a per-bookmaker breakdown); referee/half-time/shots-corners-cards are omitted. limit caps how many matches come back (default 50, max 400); the response always reports matchcount (returned), totalmatches (all rows matching your filters), truncated, and — when truncated — a narrowhint naming the arguments that narrow the result. Pass bookmakers: "all" for opening+closing odds across every bookmaker plus full match detail, or bookmakers: ["B365","PS"] for that detail on just the named code(s). Every response says which form (oddsform / oddsformdetail) it returned.

Every odds entry names its bookmaker and whether the figure is the opening or closing line; older seasons simply carry fewer bookmaker columns (and no closing odds at all before roughly 2019/20) — the response only includes whatever the source season actually has, never a fabricated value.

Auth

Keyless. The upstream is free and requires no registration.

Data sources

match results and bookmaker betting odds across 22 main European leagues and 16 further countries, free and keyless. The site asks for attribution; every tool response names football-data.co.uk as the source.

  • football-data.co.uk (compiled by Joseph Buchdahl) — historical football

Column coverage varies by season — the site adds bookmakers and an explicit closing line over time, so a 1990s-era file has far fewer odds columns than a 2020s one, and a handful of very old combinations (e.g. the English National League before it was tracked) simply don't exist. This pack reads whichever columns a given season's file actually has rather than assuming a fixed layout, and a request for a combination the site doesn't carry comes back as a clear error rather than a silent empty result.

Two bookmaker codes resolve to the same name for a structural reason, not a data error: Pinnacle's column is PS for 1X2 odds but plain P for over/under and Asian handicap, in every season observed. Both are labeled "Pinnacle" — the raw column code is kept on each entry so the distinction is still visible if it matters.

Dates before the mid-2000s are given as a 2-digit year in the source file; this pack applies the obvious pivot (<=30 → 20xx, else 19xx), which is safe across the site's actual 1993/94–present range.

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Football Odds History: common questions

Is Football Odds History MCP server safe?
Mostly: it is graded B (77/100). Read the Football Odds History safety report
How do I install Football Odds History?
It runs remotely at gateway.pipeworx.io. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Football Odds History need an API key?
Yes. The registry entry asks for PIPEWORX_API_KEY.
Is Football Odds History maintained?
The last commit was 22 days ago (2026-10-13). The latest release is v0.2.1.
Is Football Odds History up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Football Odds History compare with other MCP servers?
safety score 77/100 (higher than 50% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 80 ms (faster than 88% of 30,031 servers). Full comparison.

More from pipeworx-io →