Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Docteur Bet — football probabilities

REMOTE · MCP.DOCTEURBET.FR

Free football match probabilities (Dixon-Coles), season projections and a public track record.

+4 this week 82 Trust /100

Last scanned (8 hours ago)

Scores higher than 85% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Entertainment and Games

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security80
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability69
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1248 tokens (~178/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management67
  • Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 5 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

  • 3 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

  • 30 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 25 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 23 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 21 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Probed https://mcp.docteurbet.fr/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.docteurbet.fr CN=YR2,O=Let's Encrypt,C=US 16 Oct 2026 14 Jan 2027 RSA 2048 SHA256-RSA 6065388691c628f3da97a76fcd26e310f1f
SANs: mcp.docteurbet.fr
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.docteurbet.fr. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
fr. DS published 65381 13 Verified
docteurbet.fr. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=15552000; includeSubDomains
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy geolocation=(), microphone=(), camera=(), payment=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.docteurbet.fr/mcp Verified 200
http (plaintext) http://mcp.docteurbet.fr/mcp HTTPS enforced 301 https://mcp.docteurbet.fr/mcp
MCP tools · 7 exposed · ~920 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
find_match ~181

Finds upcoming or recent football matches (next 21 days) by team name, accepting nicknames such as "PSG", "Man City", "Barça" or "Bayern Munich". Optionally narrow with the opponent and a date. Returns candidate matches with their match_id, to pass to get_match_probabilities. If several teams match (e.g. "Paris" = Paris FC or Paris Saint-Germain), all are returned: ask the user which one they mean.

NameTypeReqDescription
datestring–Match date (YYYY-MM-DD, UTC), if known.
langstring–Language of the summary and notices: "en" or "fr".
opponentstring–The other team, if known.
teamstringyesA team name or nickname, e.g. "PSG", "Arsenal", "Inter".

No output schema declared.

No examples provided.

get_match_probabilities ~157

Returns the probabilities for one football match from the free Dixon-Coles model offered by Docteur Bet (not the Docteur Bet model, which is reserved for value bets in the app): home win / draw / away win, over/under 1.5, 2.5 and 3.5 goals, both teams to score, expected goals, most likely exact scores and team strengths. Get the match_id from find_match or get_upcoming_matches. Always cite the source, the model and the calculation date.

NameTypeReqDescription
langstring–Language of the summary and notices: "en" or "fr".
match_idintegeryesThe match_id returned by find_match or get_upcoming_matches.

No output schema declared.

No examples provided.

get_season_projection ~122

Returns the current table of a league with a season projection from tens of thousands of seasons simulated with the free Dixon-Coles model offered by Docteur Bet: each team's chances of winning the title, finishing in Champions League and European places, being relegated, and its projected final points. Not available for cups or for leagues whose format the simulator does not handle (see list_competitions).

NameTypeReqDescription
competitionstringyesLeague name, abbreviation or id.
langstring–Language of the summary and notices: "en" or "fr".

No output schema declared.

No examples provided.

get_team_strengths ~108

Returns the power ranking of a competition from the free Dixon-Coles model offered by Docteur Bet: each team's attack and defence strength relative to the league average (1 = average; a lower defence figure is better), an overall index (attack / defence), and the gap between its strength rank and its actual league position.

NameTypeReqDescription
competitionstringyesLeague name, abbreviation or id.
langstring–Language of the summary and notices: "en" or "fr".

No output schema declared.

No examples provided.

get_track_record ~112

Returns Docteur Bet's public track record: every value bet published before kick-off and then settled, wins and losses, with the number of bets, average odds and yield for each country's bookmaker market. These value bets come from the Docteur Bet model, Docteur Bet's own model for app subscribers (not the free Dixon-Coles model); the individual bets are subscriber-only and are not returned.

NameTypeReqDescription
langstring–Language of the summary and notices: "en" or "fr".

No output schema declared.

No examples provided.

get_upcoming_matches ~135

Lists the upcoming matches of one competition over the next days, each with home/draw/away probabilities from the free Dixon-Coles model offered by Docteur Bet, when published. The competition can be given by name ("Premier League", "Ligue 1", "Champions League"), common abbreviation ("EPL", "UCL") or id from list_competitions.

NameTypeReqDescription
competitionstringyesCompetition name, abbreviation or id.
daysinteger–How many days ahead (1-21).
langstring–Language of the summary and notices: "en" or "fr".

No output schema declared.

No examples provided.

list_competitions ~105

Lists the football competitions Docteur Bet models (major European leagues, three second tiers (Championship, Serie B, La Liga 2), other European leagues, Champions League, Europa League) and what is published for each: match probabilities, full match markets, season projection (title/relegation chances), team strengths. Call this when unsure whether a competition is covered.

NameTypeReqDescription
langstring–Language of the summary and notices: "en" or "fr".

No output schema declared.

No examples provided.

Install

How do I install the Docteur Bet — football probabilities MCP server?

Docteur Bet — football probabilities is a hosted endpoint at https://mcp.docteurbet.fr/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp.docteurbet.fr

# add to Claude Code
claude mcp add --transport http fr-docteurbet-docteurbet 'https://mcp.docteurbet.fr/mcp'
Common questions

What is the Docteur Bet — football probabilities MCP server?

Docteur Bet — football probabilities is an MCP server listed in the public MCP registry as fr.docteurbet/docteurbet. Free football match probabilities (Dixon-Coles), season projections and a public track record. This page covers its hosted endpoint (https://mcp.docteurbet.fr/mcp).

Is the Docteur Bet — football probabilities MCP server safe to use?

Docteur Bet — football probabilities scores 82 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Docteur Bet — football probabilities MCP server expose?

Docteur Bet — football probabilities exposes 7 tools: list_competitions, find_match, get_match_probabilities, get_upcoming_matches, get_season_projection, and 2 more. Their descriptions and schemas cost roughly 920 tokens of context every time the server is loaded.

Does the Docteur Bet — football probabilities MCP server require authentication?

No. We connected to Docteur Bet — football probabilities without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Docteur Bet — football probabilities MCP server still maintained?

Docteur Bet — football probabilities is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Docteur Bet — football probabilities MCP server?

VerifyMCP ran 13 checks on Docteur Bet — football probabilities, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.