io.github.livetennisapi/livetennisapi-mcp
REMOTE · MCP.LIVETENNISAPI.COM · 2 COMPONENTS · SCANNED SEP 20
Live tennis scores, players, rankings, odds and win-probability. ATP, WTA, Challenger, ITF, juniors.
Available components
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 Security83
- 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. 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 is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2929 tokens (~122/item across 24 items; 24 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 24 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 24 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
How do I install the io.github.livetennisapi/livetennisapi-mcp server?
io.github.livetennisapi/livetennisapi-mcp is a hosted endpoint at https://mcp.livetennisapi.com/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.livetennisapi.com
claude mcp add --transport http livetennisapi-livetennisapi-mcp 'https://mcp.livetennisapi.com/mcp'
{
"mcpServers": {
"livetennisapi-livetennisapi-mcp": {
"url": "https://mcp.livetennisapi.com/mcp"
}
}
} {
"servers": {
"livetennisapi-livetennisapi-mcp": {
"type": "http",
"url": "https://mcp.livetennisapi.com/mcp"
}
}
} [mcp_servers.livetennisapi-livetennisapi-mcp] url = "https://mcp.livetennisapi.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"livetennisapi-livetennisapi-mcp": {
"type": "remote",
"url": "https://mcp.livetennisapi.com/mcp",
"enabled": true
}
}
} openclaw mcp add livetennisapi-livetennisapi-mcp --url 'https://mcp.livetennisapi.com/mcp' --transport streamable-http
mcp_servers:
livetennisapi-livetennisapi-mcp:
url: "https://mcp.livetennisapi.com/mcp" {
"McpServers": {
"livetennisapi-livetennisapi-mcp": {
"Transport": "http",
"Url": "https://mcp.livetennisapi.com/mcp"
}
}
} assistant mcp add livetennisapi-livetennisapi-mcp -t streamable-http -u 'https://mcp.livetennisapi.com/mcp'
{
"mcpServers": {
"livetennisapi-livetennisapi-mcp": {
"type": "http",
"url": "https://mcp.livetennisapi.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 20 Sept 26 −1
- Tool “search_players” rewrote its description, which is the text the model reads security
- Tool “search_tournaments” rewrote its description, which is the text the model reads security
- Tool “get_live_matches” rewrote its description, which is the text the model reads security
- Tool “get_match” rewrote its description, which is the text the model reads security
- Tool “get_match_analysis” rewrote its description, which is the text the model reads security
- Tool “get_match_odds” rewrote its description, which is the text the model reads security
- Tool “get_match_score” rewrote its description, which is the text the model reads security
- Tool “get_player” rewrote its description, which is the text the model reads security
- Tool “get_tournament” rewrote its description, which is the text the model reads security
- Tool “get_upcoming_matches” rewrote its description, which is the text the model reads security
- Tool “get_fixtures” rewrote its description, which is the text the model reads security
- Server version: 1.4.0 → 1.5.0 functional
- 15 Sept 26 +1
- DNSSEC: fail → pass ▲ security
- 31 Aug 26 +3
- HSTS header: fail → pass ▲ security
- 30 Aug 26 +4
- HTTPS: unverified → pass ▲ security
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Aug 26 0
- Tool “get_live_matches” rewrote its description, which is the text the model reads security
- Tool “get_recent_results” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- Server version: 1.2.1 → 1.4.0 functional
- New tool “get_h2h” functional
- New tool “get_archive_career” functional
- New tool “get_archive_match” functional
- New tool “get_charting_match” functional
- New tool “get_charting_player” functional
- New tool “get_match_statistics” functional
- New tool “get_player_rankings” functional
- New tool “get_rankings” functional
- New tool “get_tournament” functional
- New tool “search_archive_matches” functional
- New tool “search_archive_players” functional
- New tool “search_tournaments” functional
- “get_fixtures” added an optional parameter “tour” cosmetic
- “get_live_matches” added an optional parameter “country” cosmetic
- “get_live_matches” added an optional parameter “player” cosmetic
- “get_live_matches” added an optional parameter “tour” cosmetic
- “get_recent_results” added an optional parameter “country” cosmetic
- “get_recent_results” added an optional parameter “from” cosmetic
- “get_recent_results” added an optional parameter “player” cosmetic
- “get_recent_results” added an optional parameter “to” cosmetic
- “get_recent_results” added an optional parameter “tour” cosmetic
- “get_upcoming_matches” added an optional parameter “country” cosmetic
- “get_upcoming_matches” added an optional parameter “from” cosmetic
- “get_upcoming_matches” added an optional parameter “player” cosmetic
- “get_upcoming_matches” added an optional parameter “to” cosmetic
- “get_upcoming_matches” added an optional parameter “tour” cosmetic
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 20 Sept 2026 · Probed https://mcp.livetennisapi.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=livetennisapi.com | CN=WE1,O=Google Trust Services,C=US | 15 Sept 2026 | 14 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 961d8365094d23f50ed6bd87585e0b90 |
| SANs: livetennisapi.com, *.livetennisapi.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of mcp.livetennisapi.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| livetennisapi.com. | present | 2371 | 13 | Verified |
| mcp.livetennisapi.com. | Verified address RRset verified with the apex keys |
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 |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.livetennisapi.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.livetennisapi.com/mcp | HTTPS enforced | 301 | https://mcp.livetennisapi.com/mcp |
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 →
check_api_status API status and plan ~36
Check whether the Live Tennis API is reachable and which plan the configured key is on. Useful for diagnosing why other tools are refusing data.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| api_version | string|null | – | API version reported by the health check. |
| has_key | boolean | – | Whether a key was supplied with this call. |
| message | string | yes | Human-readable summary. Identical to the text content, so either half can be used alone. |
| ok | boolean | yes | True when the call returned data. False for a tier wall, a missing or rejected key, or an empty result — all of which are normal states with a clear remedy, not failures. |
| reachable | boolean | – | True when the API answered its health check. |
| tier | string|null | – | Detected plan: FREE, BASIC, PRO or ULTRA. Null when no key is configured. |
No examples provided.
get_archive_career Archive career aggregates ~120
One player's whole career over the results archive (1968–2022): W-L record overall and by surface/level/year, titles, and summed serve statistics with honest coverage — the corpus records serve stats from 1991 only, so matches_with_stats states how many matches the serve block covers. The name must resolve to one person; an ambiguous fragment returns the candidate list to choose from. Requires the BASIC plan or any History plan.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Player name fragment, min 3 chars — must resolve to exactly one person. |
| Name | Type | Req | Description |
|---|---|---|---|
| by_year | array | – | Per-season W-L. |
| message | string | yes | Human-readable summary. Identical to the text content, so either half can be used alone. |
| ok | boolean | yes | True when the call returned data. False for a tier wall, a missing or rejected key, or an empty result — all of which are normal states with a clear remedy, not failures. |
| player_name | string|null | – | The resolved player. |
| record | object | – | The W-L record. |
| serve | – | – | Summed serve stats + derived ratios. matches_with_stats states the coverage; ratios are null where the denominator is zero. |
| span | object | – | Career span inside the archive. |
No examples provided.
get_archive_match Archive result detail ~78
One result from the results archive (1968–2022), with per-match serve statistics where the era recorded them — stats are null for most rows before 1991, honestly, never synthesised. Requires the BASIC plan or any History plan.
| Name | Type | Req | Description |
|---|---|---|---|
| archive_match_id | integer | yes | Archive match id, as returned by search_archive_matches. |
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | Human-readable summary. Identical to the text content, so either half can be used alone. |
| ok | boolean | yes | True when the call returned data. False for a tier wall, a missing or rejected key, or an empty result — all of which are normal states with a clear remedy, not failures. |
| result | object | – | The archive result. |
| stats | – | – | Per-match serve statistics (aces, double_faults, serve_points, first_in, first_won, second_won, serve_games, bp_saved, bp_faced). Null for most pre-1991 rows. |
No examples provided.
get_charting_match Charting: one match, every stat family ~104
Every Match Charting Project stat family for ONE charted match, both players, with the per-set split (set 1, set 2, …, Total) exactly as charted. Charting ids are their own id space (1960–2026), mostly matches with no counterpart in the live tables. Requires the ULTRA plan.
| Name | Type | Req | Description |
|---|---|---|---|
| charting_match_id | integer | yes | Charting match id — its own id space, not a match_id. |
| Name | Type | Req | Description |
|---|---|---|---|
| charting_match_id | number|null | – | The charted match. |
| families | object | – | Every stat family, per player, with the per-set split. |
| gender | string|null | – | – |
| mcp_id | string|null | – | The Match Charting Project's own row identifier. |
| message | string | yes | Human-readable summary. Identical to the text content, so either half can be used alone. |
| ok | boolean | yes | True when the call returned data. False for a tier wall, a missing or rejected key, or an empty result — all of which are normal states with a clear remedy, not failures. |
| players | – | – | Both players as charted. |
No examples provided.
get_charting_player Charting: player career profile ~151
Career shot-level profile from the Match Charting Project: serve placement (deuce/ad × wide/body/T), return depth and outcomes, net play, clutch break/game/set-point serving, winners and errors by wing, rally-length tendencies — summed over the player's charted matches. COVERAGE IS CURATED (11,646 charted matches back to the 1960s, concentrated on the majors), not full-slate. An ambiguous name returns the candidates to choose from. Requires the ULTRA plan.
| Name | Type | Req | Description |
|---|---|---|---|
| gender | string | – | Disambiguates a name charted on both tours. |
| name | string | yes | Player name fragment, min 3 chars — must resolve to one charted person. |
| Name | Type | Req | Description |
|---|---|---|---|
| coverage | string|null | – | A reminder that charting coverage is curated, not full-slate. |
| families | object | – | Per-family summed numeric columns — raw sums over the player's charted Total rows. |
| matches_charted | number|null | – | The sample every summed field covers. |
| message | string | yes | Human-readable summary. Identical to the text content, so either half can be used alone. |
| ok | boolean | yes | True when the call returned data. False for a tier wall, a missing or rejected key, or an empty result — all of which are normal states with a clear remedy, not failures. |
| player | – | – | The resolved charted player. |
No examples provided.
get_fixtures Fixture schedule ~97
Upcoming scheduled tennis fixtures, earliest first — the forward schedule, filterable by tour, player and date. Use this for "what is on this week". Works on the FREE plan (no card needed).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum fixtures to return (1-200). |
| tour | string | – | Tour filter; each name covers its doubles variants. Exhibition/team events carry no tour and are excluded whenever the filter is used. |
| Name | Type | Req | Description |
|---|---|---|---|
| fixtures | array | – | Scheduled fixtures, earliest first. |
| message | string | yes | Human-readable summary. Identical to the text content, so either half can be used alone. |
| ok | boolean | yes | True when the call returned data. False for a tier wall, a missing or rejected key, or an empty result — all of which are normal states with a clear remedy, not failures. |
No examples provided.
get_h2h Head-to-head ~151
The all-time record between two players, across BOTH halves of the product: the results archive (1968–2022) plus our own completed matches (2023 onward). Names are the keys — an ambiguous fragment returns the candidate list to choose from rather than guessing. Totals count only meetings with a known winner; walkovers and retirements are part of the record and each meeting carries its outcome. Requires the BASIC plan or any History plan.
| Name | Type | Req | Description |
|---|---|---|---|
| player1 | string | yes | First player name (fragment, min 3 chars), e.g. "federer". |
| player2 | string | yes | Second player name (fragment, min 3 chars), e.g. "nadal". |
| Name | Type | Req | Description |
|---|---|---|---|
| by_surface | object | – | Decided wins per surface; keys are surface names plus "unknown". |
| meetings | array | – | Individual meetings, newest first, capped at 200. |
| message | string | yes | Human-readable summary. Identical to the text content, so either half can be used alone. |
| ok | boolean | yes | True when the call returned data. False for a tier wall, a missing or rejected key, or an empty result — all of which are normal states with a clear remedy, not failures. |
| players | – | – | The resolved names; null when no player matches the fragments. |
| totals | object | – | The headline record. |
No examples provided.
get_live_matches Live matches ~174
List tennis matches currently in progress, with live scores. Covers ATP, WTA, Challenger, ITF and juniors. Use this for "what tennis is on right now". Works on the FREE plan (no card needed).
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Either participant's country — the lowercase 3-letter IOC-style code the Player object returns (e.g. ned, sui, gre), NOT ISO-3166. Players with no recorded country never match. |
| limit | integer | – | Maximum matches to return (1-200). |
| player | array | – | Player ids (from search_players), max 50 — keeps matches where ANY listed player is either participant. |
| tour | string | – | Tour filter; each name covers its doubles variants. Exhibition/team events carry no tour and are excluded whenever the filter is used. |
| Name | Type | Req | Description |
|---|---|---|---|
| matches | array | – | The live matches, most relevant first. |
| message | string | yes | Human-readable summary. Identical to the text content, so either half can be used alone. |
| ok | boolean | yes | True when the call returned data. False for a tier wall, a missing or rejected key, or an empty result — all of which are normal states with a clear remedy, not failures. |
No examples provided.
get_match Match detail ~74
Full detail for one match by id: players, score, surface, round and status. Includes market prices on PRO and model analysis on ULTRA. Works on the FREE plan (no card needed).
| Name | Type | Req | Description |
|---|---|---|---|
| match_id | integer | yes | Match id, as returned by get_live_matches, get_upcoming_matches or get_recent_results. |
| Name | Type | Req | Description |
|---|---|---|---|
| analysis | object | – | Model analysis. Requires the ULTRA plan; absent otherwise. |
| market | object | – | Match-winner market. Requires the PRO plan; absent otherwise. |
| match | object | – | The match. |
| message | string | yes | Human-readable summary. Identical to the text content, so either half can be used alone. |
| ok | boolean | yes | True when the call returned data. False for a tier wall, a missing or rejected key, or an empty result — all of which are normal states with a clear remedy, not failures. |
No examples provided.
get_match_analysis Model analysis ~84
Model analysis for a match: predicted win probability, the model's thesis and the key factors behind it. Requires the ULTRA plan. Match rows carry has_analysis — check it first; a match with no thesis or profile has nothing to return.
| Name | Type | Req | Description |
|---|---|---|---|
| match_id | integer | yes | Match id, as returned by get_live_matches, get_upcoming_matches or get_recent_results. |
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | Human-readable summary. Identical to the text content, so either half can be used alone. |
| ok | boolean | yes | True when the call returned data. False for a tier wall, a missing or rejected key, or an empty result — all of which are normal states with a clear remedy, not failures. |
| profile | object | – | Quantitative view. |
| thesis | object | – | Narrative view. |
No examples provided.
get_match_events Match timeline ~73
Timeline of events for a match — breaks, games won, sets won, momentum runs. Requires the PRO plan.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum events to return (1-200). |
| match_id | integer | yes | Match id, as returned by get_live_matches, get_upcoming_matches or get_recent_results. |
| Name | Type | Req | Description |
|---|---|---|---|
| events | array | – | Events in chronological order. |
| message | string | yes | Human-readable summary. Identical to the text content, so either half can be used alone. |
| ok | boolean | yes | True when the call returned data. False for a tier wall, a missing or rejected key, or an empty result — all of which are normal states with a clear remedy, not failures. |
No examples provided.
get_match_odds Match market prices ~100
Match-winner market prices for a match — implied probability per player, with bid, ask and mid. Requires the PRO plan. Match rows carry has_market — check it first; a match with no market mapped has no prices to return.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum price points to return (1-200). |
| match_id | integer | yes | Match id, as returned by get_live_matches, get_upcoming_matches or get_recent_results. |
| Name | Type | Req | Description |
|---|---|---|---|
| market | object | – | The match-winner market. |
| message | string | yes | Human-readable summary. Identical to the text content, so either half can be used alone. |
| ok | boolean | yes | True when the call returned data. False for a tier wall, a missing or rejected key, or an empty result — all of which are normal states with a clear remedy, not failures. |
No examples provided.
get_match_score Match score ~75
Current score for one match — the fastest, lowest-latency read. Use this when you only need the score and already know the match id. Works on the FREE plan (no card needed).
| Name | Type | Req | Description |
|---|---|---|---|
| match_id | integer | yes | Match id, as returned by get_live_matches, get_upcoming_matches or get_recent_results. |
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | Human-readable summary. Identical to the text content, so either half can be used alone. |
| ok | boolean | yes | True when the call returned data. False for a tier wall, a missing or rejected key, or an empty result — all of which are normal states with a clear remedy, not failures. |
| score | object | – | The current score. |
No examples provided.
get_match_statistics Match statistics ~129
In-play (or final) statistics for one match, in TWO families kept deliberately separate: DERIVED is rebuilt from the point-by-point record (holds/breaks, break points, service/return points); MEASURED is counted upstream and includes what no point record can yield — aces, double faults, the serve split, winners/unforced errors. Measured coverage varies by tour; absent fields are omitted, never zero-filled. Requires the ULTRA plan.
| Name | Type | Req | Description |
|---|---|---|---|
| match_id | integer | yes | Match id, as returned by get_live_matches, get_upcoming_matches or get_recent_results. |
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | Human-readable summary. Identical to the text content, so either half can be used alone. |
| ok | boolean | yes | True when the call returned data. False for a tier wall, a missing or rejected key, or an empty result — all of which are normal states with a clear remedy, not failures. |
| statistics | object | – | The statistics. |
No examples provided.
get_player Player profile ~52
One player's profile: ranking, country, handedness, date of birth and cached stats. Works on the FREE plan (no card needed).
| Name | Type | Req | Description |
|---|---|---|---|
| player_id | integer | yes | Player id, as returned by search_players. |
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | Human-readable summary. Identical to the text content, so either half can be used alone. |
| ok | boolean | yes | True when the call returned data. False for a tier wall, a missing or rejected key, or an empty result — all of which are normal states with a clear remedy, not failures. |
| player | object | – | The player. |
No examples provided.
get_player_rankings Player rankings as of a date ~176
Point-in-time ranking records for SPECIFIC players: per system, the newest record in force ON OR BEFORE as_of — never one dated after it. Every other ranking field in this API is the CURRENT value joined at read time; this is the historical answer. Systems are never collapsed: ATP/WTA and the ITF circuits carry rank+points, UTR a rating. ITF and UTR history begins 2026-07-29. Requires the ULTRA plan.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | – | YYYY-MM-DD — the record in force on this date. Omit for the latest known. |
| player_ids | array | yes | Roster player ids, as returned by search_players. Max 50. |
| system | string | – | Restrict to one system. Omit for every system held for the player. |
| Name | Type | Req | Description |
|---|---|---|---|
| coverage | – | – | What resolved against what was asked (players_resolved, systems_resolved, oldest_available per system). Read before trusting an empty result. |
| message | string | yes | Human-readable summary. Identical to the text content, so either half can be used alone. |
| ok | boolean | yes | True when the call returned data. False for a tier wall, a missing or rejected key, or an empty result — all of which are normal states with a clear remedy, not failures. |
| rankings | array | – | One record per player × system held. |
No examples provided.
get_rankings Rankings listing ~163
The FULL published ranking table in rank order for one system — the newest week at or before as_of. Rows carry player_name as published and a null player_id for players outside our roster, so the table has no silent holes. ATP/WTA history runs deep; the ITF circuits begin 2026-07-29. For point-in-time records of SPECIFIC players use get_player_rankings. Requires the PRO plan.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | – | YYYY-MM-DD — serves the newest published week at or before this date. Omit for latest. |
| limit | integer | – | Maximum ranking rows to return (1-200). |
| system | string | yes | Ranking system to list. utr has no listing — it is a rating, not a ranking. |
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | Human-readable summary. Identical to the text content, so either half can be used alone. |
| ok | boolean | yes | True when the call returned data. False for a tier wall, a missing or rejected key, or an empty result — all of which are normal states with a clear remedy, not failures. |
| rankings | array | – | The table in rank order. |
No examples provided.
get_recent_results Recent results ~212
Recently completed tennis matches with final scores and winners. Filterable by tour, player, nationality and play date. Requires the BASIC plan or any History plan.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Either participant's country — the lowercase 3-letter IOC-style code the Player object returns (e.g. ned, sui, gre), NOT ISO-3166. Players with no recorded country never match. |
| from | string | – | Earliest play date: YYYY-MM-DD (a whole UTC day) or ISO-8601 datetime. |
| limit | integer | – | Maximum matches to return (1-200). |
| player | array | – | Player ids (from search_players), max 50 — keeps matches where ANY listed player is either participant. |
| to | string | – | Latest play date: YYYY-MM-DD or ISO-8601; must not precede from. |
| tour | string | – | Tour filter; each name covers its doubles variants. Exhibition/team events carry no tour and are excluded whenever the filter is used. |
| Name | Type | Req | Description |
|---|---|---|---|
| matches | array | – | Completed matches, most recent first. |
| message | string | yes | Human-readable summary. Identical to the text content, so either half can be used alone. |
| ok | boolean | yes | True when the call returned data. False for a tier wall, a missing or rejected key, or an empty result — all of which are normal states with a clear remedy, not failures. |
No examples provided.
get_tournament Tournament detail ~78
One tournament by its stable id — the tournament_id carried on match objects. Name, tour, surface, indoor, plus host city/country and category where curated. Works on the FREE plan (no card needed).
| Name | Type | Req | Description |
|---|---|---|---|
| tournament_id | string | yes | Stable tournament id, as returned by search_tournaments or carried on a match as tournament_id. |
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | Human-readable summary. Identical to the text content, so either half can be used alone. |
| ok | boolean | yes | True when the call returned data. False for a tier wall, a missing or rejected key, or an empty result — all of which are normal states with a clear remedy, not failures. |
| tournament | object | – | The tournament. |
No examples provided.
get_upcoming_matches Upcoming matches ~226
List tennis matches scheduled to start soon, with players, tournament and start time. Use this for "who plays next" or to find a match id before it starts. Works on the FREE plan (no card needed).
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Either participant's country — the lowercase 3-letter IOC-style code the Player object returns (e.g. ned, sui, gre), NOT ISO-3166. Players with no recorded country never match. |
| from | string | – | Earliest play date: YYYY-MM-DD (a whole UTC day) or ISO-8601 datetime. |
| limit | integer | – | Maximum matches to return (1-200). |
| player | array | – | Player ids (from search_players), max 50 — keeps matches where ANY listed player is either participant. |
| to | string | – | Latest play date: YYYY-MM-DD or ISO-8601; must not precede from. |
| tour | string | – | Tour filter; each name covers its doubles variants. Exhibition/team events carry no tour and are excluded whenever the filter is used. |
| Name | Type | Req | Description |
|---|---|---|---|
| matches | array | – | Matches due to start, soonest first. |
| message | string | yes | Human-readable summary. Identical to the text content, so either half can be used alone. |
| ok | boolean | yes | True when the call returned data. False for a tier wall, a missing or rejected key, or an empty result — all of which are normal states with a clear remedy, not failures. |
No examples provided.
search_archive_matches Results archive (1968–2022) ~263
Search the results archive — completed-match RESULTS from 1968 through 2022: ATP and WTA, main draws, qualifying and the ITF/futures tiers. Winner/loser-shaped records with final score, seeds and ranks AT THE TIME of the match. Use this for historical questions ("Borg's Wimbledon finals"); the archive ends 2022-12-31 where our own results (get_recent_results) begin. Requires the BASIC plan or any History plan.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | Earliest tournament START date, YYYY-MM-DD. |
| level | string | – | Source tier code: G=grand slam, M=masters, A=tour, F=finals, D=davis cup, C=challenger, O=olympics, or a futures category code (e.g. 15). |
| limit | integer | – | Maximum results to return (1-200). |
| player_name | string | – | Case-insensitive fragment of EITHER player's name, min 3 chars, e.g. "borg". |
| round | string | – | Round code, e.g. F for finals. |
| to | string | – | Latest tournament START date, YYYY-MM-DD. |
| tour | string | – | atp or wta. |
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | Human-readable summary. Identical to the text content, so either half can be used alone. |
| ok | boolean | yes | True when the call returned data. False for a tier wall, a missing or rejected key, or an empty result — all of which are normal states with a clear remedy, not failures. |
| results | array | – | Archive results, newest tournament first. |
No examples provided.
search_archive_players Archive player bios ~135
The people of the results archive (1968–2022): hand, date of birth, country, height, and career-high rank with the week it was first reached. Their ids are corpus person ids (the winner/loser player_id on archive results), not roster ids — for current players use search_players. Requires the BASIC plan or any History plan.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum players to return (1-200). |
| query | string | yes | Full or partial player name, min 3 chars, e.g. "navratilova". |
| tour | string | – | atp or wta. |
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | Human-readable summary. Identical to the text content, so either half can be used alone. |
| ok | boolean | yes | True when the call returned data. False for a tier wall, a missing or rejected key, or an empty result — all of which are normal states with a clear remedy, not failures. |
| players | array | – | Matching archive people, ordered by name. |
No examples provided.
search_players Search players ~76
Search tennis players by name. Returns id, country, ranking and tour. Use the returned id with get_player. Works on the FREE plan (no card needed).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum players to return (1-200). |
| query | string | yes | Full or partial player name, e.g. "alcaraz". |
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | Human-readable summary. Identical to the text content, so either half can be used alone. |
| ok | boolean | yes | True when the call returned data. False for a tier wall, a missing or rejected key, or an empty result — all of which are normal states with a clear remedy, not failures. |
| players | array | – | Matching players, best match first. |
No examples provided.
search_tournaments Tournament catalogue ~102
Search the tournament catalogue — the stable id space that match objects carry as tournament_id. Returns surface, indoor, host city/country and category where curated. Works on the FREE plan (no card needed).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum tournaments to return (1-200). |
| query | string | – | Full or partial tournament name, e.g. "wimbledon". Omit to list all. |
| tour | string | – | Restrict to one tour. |
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | Human-readable summary. Identical to the text content, so either half can be used alone. |
| ok | boolean | yes | True when the call returned data. False for a tier wall, a missing or rejected key, or an empty result — all of which are normal states with a clear remedy, not failures. |
| tournaments | array | – | Matching tournaments, name order. |
No examples provided.
What is the io.github.livetennisapi/livetennisapi-mcp server?
io.github.livetennisapi/livetennisapi-mcp is listed in the public MCP registry as io.github.livetennisapi/livetennisapi-mcp. Live tennis scores, players, rankings, odds and win-probability. ATP, WTA, Challenger, ITF, juniors. This page covers its hosted endpoint (https://mcp.livetennisapi.com/mcp).
Is the io.github.livetennisapi/livetennisapi-mcp server safe to use?
io.github.livetennisapi/livetennisapi-mcp scores 89 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 io.github.livetennisapi/livetennisapi-mcp server expose?
io.github.livetennisapi/livetennisapi-mcp exposes 24 tools: get_live_matches, get_upcoming_matches, get_match, get_match_score, search_players, and 19 more. Their descriptions and schemas cost roughly 2,929 tokens of context every time the server is loaded.
Does the io.github.livetennisapi/livetennisapi-mcp server require authentication?
No. We connected to io.github.livetennisapi/livetennisapi-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.livetennisapi/livetennisapi-mcp server still maintained?
io.github.livetennisapi/livetennisapi-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.