Football Database and Results

Measured conclusion: Deep-tested. L2 outcome: tools_ok.

Historical football results, draws and no-draw streaks. 11 read-only tools, 6 need no API key.

Add to your agent

Copy this into your MCP client config:

{
  "mcpServers": {
    "Football Database and Results": {
      "url": "https://fdb4.io/mcp",
      "transport": "streamable-http"
    }
  }
}

Measured tools (11)

• predict_draws read-only

  [PAID] Rank teams by how overdue a draw is — the question this database exists to answer. Every team has a historical draw rate and a run of matches since its last draw. When the run is long relative to how often that team normally draws, the team is carrying "draw debt", and this tool ranks the whole field by it, most overdue first. Ask it "which national teams are most due a draw?" or "who is overdue a draw in the World Cup 2026 field?" and it answers directly; nothing else here needs to be queried first. Each entry returns the rank, the score, and the signals behind it: matches played, draws, draw percentage, the current no-draw streak, the longest ever, and the debt figure. Filters subset which teams are listed — a team's score and rank are global and never change with them. Historical pattern, not a betting tip. Costs 1 point per call (1 point = 1 cent); paginated calls cost 1 point per page.

  Parameters:

  • type — string — Restrict the ranking to national teams or to clubs. Omit to rank both together.
  • limit — integer — How many ranked teams to return. Default 25, max 500. One call, one point, whatever the limit.
  • recent — boolean — Only teams with a recent match, so the answer is about teams currently playing. Default true.
  • wc2026 — boolean — Restrict to the 2026 World Cup team group. Default false.

  Hints: read-only yes · destructive not declared · idempotent yes · open-world not declared

• get_team_prediction read-only

  [PAID] How overdue a draw one named team is, plus the results that made it so. Returns the team's draw-likelihood rank and score among all ranked teams, the signals behind it (draw rate, current no-draw streak, longest ever, draw debt), and its recent form — every match in the current no-draw run, with opponent, score and side. Use this when the question is about a specific team ("is Brazil due a draw?"); use predict_draws when the question is about the field. The prediction comes back null when the team exists but is not currently ranked (no played matches, or excluded by the `recent` filter). Historical pattern, not a betting tip. Costs 1 point per call (1 point = 1 cent); paginated calls cost 1 point per page.

  Parameters:

  • team (required) — string — Numeric team id or slug — 431 or "arsenal". Both come from list_teams.
  • recent — boolean — Rank within teams that have played recently, matching predict_draws. Default true.
  • wc2026 — boolean — Rank within the 2026 World Cup team group. Default false.

  Hints: read-only yes · destructive not declared · idempotent yes · open-world not declared

• get_draw_model read-only

  [PAID] Every draw reading FDB4 holds for ONE match — use it when someone asks how likely a specific fixture is to end level, rather than which teams are overdue a draw (`predict_draws` answers that). Five readings come back side by side, because they are not interchangeable: the Dixon-Coles goals model's own probability with the expected goals behind it; the historical draw rate at this fixture's Elo rating gap; the one-parameter blend of those two the site has published since September 2026; the five-feature logistic model that now sits beside it with a 95% band around it; and the bookmaker's draw price where one is recorded. Also returned: when the logistic model was last fitted, over how many matches, and its coefficients — so an answer can explain itself. Identify the match by `match_id`, or by `team` (id or slug) plus an optional `date`; with no date you get that team's next fixture. `is_forecast` says whether the logistic figure is a real forecast (a fixture) or an in-sample description of a match the model was fitted on. Historical pattern, not a betting tip. Costs 1 point per call (1 point = 1 cent); paginated calls cost 1 point per page.

  Parameters:

  • date — string — With `team`, the match date as YYYY-MM-DD. Omit for that team's next fixture.
  • team — string — A team id or slug (431, arsenal), from list_teams. Give this or `match_id`.
  • match_id — integer — The match id, from search_results or a fixture list. Give this or `team`.

  Hints: read-only yes · destructive not declared · idempotent yes · open-world not declared

• top_streaks read-only

  [PAID] The all-time leaderboard of no-draw runs — the longest any team has gone without drawing. Answers "what is the longest run of matches without a draw on record?" and "who else has done it?". Each entry is one run: its length, the dates it started and ended, and the team. A team can appear more than once, since a great side may have several long runs. Filter to one team, to national teams or clubs, or to runs above a minimum length. Paginated, 25 per page by default; `page` walks the leaderboard and each page costs its own point. Costs 1 point per call (1 point = 1 cent); paginated calls cost 1 point per page.

  Parameters:

  • min — integer — Minimum run length to list. Default 5.
  • page — integer — Page number, from 1. Each page is a separate call and costs its own point.
  • type — string — Restrict to national teams or to clubs.
  • limit — integer — Page size. Default 25, max 500.
  • team_id — integer — Restrict to one team. Numeric id from list_teams.

  Hints: read-only yes · destructive not declared · idempotent yes · open-world not declared

• get_team_streaks read-only

  [FREE] Every no-draw run one team has ever had, plus the one it is on now. A no-draw run is a sequence of matches that ended in a win or a loss. This returns the run currently in progress with each match in it — date, competition, opponent, score — so you can say exactly when the team last drew and what has happened since, together with every recorded run in the team's history, longest first, each with its start and end dates. Runs span all competitions; per-competition runs are not split out. Free: no key needed, and it costs a key holder nothing either.

  Parameters:

  • team (required) — string — Numeric team id or slug — 431 or "arsenal". Find either with list_teams.

  Hints: read-only yes · destructive not declared · idempotent yes · open-world not declared

• list_teams read-only

  [FREE] Find a team and its id — the lookup every other team tool depends on. Search by name prefix with `q` ("arse" finds Arsenal), or browse by first letter, or list one kind of team. Each row carries the numeric id and the slug that get_team, get_team_streaks, get_team_prediction, head_to_head and search_results take. The database holds thousands of teams, so an unfiltered call returns the first 25 with the full total beside them. Always pass `q` when you know the name. Free: no key needed, and it costs a key holder nothing either.

  Parameters:

  • q — string — Name prefix, matched against both the short and the full name. The fastest way to find one team.
  • type — string — Restrict to national teams or to clubs.
  • limit — integer — How many teams to return. Default 25; the total number of matches is always reported.
  • letter — string — First letter A-Z to browse by, or "#" for names starting with a non-letter.

  Hints: read-only yes · destructive not declared · idempotent yes · open-world not declared

• get_team read-only

  [FREE] One team's profile and its all-time draw statistics. Returns the team's name, country and type alongside the numbers this database is built on: matches played, draws, draw percentage, the no-draw streak currently running, the longest one ever, the average of its longest runs, its draw debt and its rank in the draw-likelihood field. Use it to answer "how often does this team draw?" or "how long since they last drew?". Takes a numeric id or a slug, whichever you already hold; both come from list_teams. Free: no key needed, and it costs a key holder nothing either.

  Parameters:

  • team (required) — string — Numeric team id or slug — 431 or "arsenal". Find either with list_teams.

  Hints: read-only yes · destructive not declared · idempotent yes · open-world not declared

• list_tournaments read-only

  [FREE] Every competition covered — leagues, domestic cups, continental cups, World Cups — with how many matches and how many draws each one holds. Two uses. Without `tournament` it answers "what is in this database, and how draw-heavy is each competition?", returning each competition's id, slug, country, match count, draw count and draw percentage. With `tournament` (an id or slug) it returns that one competition in full: the years it covers, every edition newest first with its champion where one was decided, and the all-time winners ranking with title counts and years. The competition ids here are what search_results and head_to_head filter by. Free: no key needed, and it costs a key holder nothing either.

  Parameters:

  • limit — integer — How many competitions to list. Default 25; the total is always reported.
  • tournament — string — One competition, by numeric id or slug (53 or "norway-cup"). Returns its editions, champions and all-time winners instead of the list.

  Hints: read-only yes · destructive not declared · idempotent yes · open-world not declared

• list_countries read-only

  [FREE] Every country in the database, with its FIFA code and id. Use it to turn a country name into the id and FIFA code the rest of the data is keyed by, or to check which countries are covered at all. Search with `q`, which matches a name prefix or an exact FIFA code ("ENG"). Countries that no longer exist are included and flagged, because the match archive still holds their games. Free: no key needed, and it costs a key holder nothing either.

  Parameters:

  • q — string — Country name prefix, or an exact FIFA code such as ENG or BRA.
  • limit — integer — How many countries to return. Default 25; the total is always reported.

  Hints: read-only yes · destructive not declared · idempotent yes · open-world not declared

• search_results read-only

  [FREE for the last 7 days · PAID for the archive] Search the match archive: finished matches, newest first, with scores. This is the raw history behind every other tool — decades of results across national team football, domestic leagues and cups. Filter by team, competition, single season, outcome (home win, away win or draw) and date range, in any combination: "Arsenal's draws since 2020", "every match in the 2025/26 Premier League", "all draws in the World Cup". Each match returns its date, competition and edition, both teams, the score and whether it was a draw. Results are paginated, 50 per page by default; `page` walks through them and `meta.total` tells you how many matches matched before you start. Free, no key needed, for recent results: the first page of 50, and any `from` date inside the last 7 days. Reaching further back — an older `from`, a bigger `limit`, or page 2 onward — is the archive and costs 1 point per call (1 point = 1 cent), one point per page.

  Parameters:

  • to — string — Latest match date, inclusive, as YYYY-MM-DD.
  • from — string — Earliest match date, inclusive, as YYYY-MM-DD. Inside the last 7 days the call is free and needs no key; earlier than that it costs 1 point.
  • page — integer — Page number, from 1. Page 1 can be free; every page after it is a separate call and costs its own point.
  • type — string — Restrict to national-team or club football.
  • limit — integer — Page size: 50, 100, 250 or 500. Default 50, which is also the largest free page. Anything else is treated as 100.
  • outcome — string — H for a home win, A for an away win, D for a draw.
  • team_id — integer — Matches involving this team, home or away. Numeric id from list_teams.
  • competition_id — integer — Restrict to one competition. Id from list_tournaments.
  • competition_item_id — integer — Restrict to a single edition or season. Edition ids come from list_tournaments with a `tournament` argument.

  Hints: read-only yes · destructive not declared · idempotent yes · open-world not declared

• head_to_head read-only

  [PAID] The complete record between two teams, and every match they have ever played. Answers "who wins more between these two, and how often do they draw?" — matches played, wins each way, draws, goals each way and the draw percentage, all from team A's perspective, followed by every meeting with its date, competition and score. Optionally narrow to one competition type or a single edition to compare only their league games, or only one season. Both teams are given as numeric ids, which list_teams returns. Costs 1 point per call (1 point = 1 cent); paginated calls cost 1 point per page.

  Parameters:

  • a (required) — integer — Team A, as a numeric id from list_teams. The record is reported from this team's point of view.
  • b (required) — integer — Team B, as a numeric id from list_teams. Must differ from a.
  • item — integer — Restrict to a single edition or season id, from list_tournaments with a `tournament` argument.
  • type — string — Restrict to one competition type, such as league or cup.

  Hints: read-only yes · destructive not declared · idempotent yes · open-world not declared

Publisher website

Measured by MCPYP probing. Untested fields are omitted, never estimated. Listing is always free; MCPYP never proxies calls or stores user tokens.