Livetennisapi MCP is answering right now. Last checked 14 min ago. 241 installs a week from npm. It exposes 24 tools. Last commit 14 Sep 2026.
Live tennis scores, players, rankings, odds and win-probability. ATP, WTA, Challenger, ITF, juniors.
Installs per day
peak 72 · avg 19 · -40% w/w
a month agotoday
Uptime history
48 days of history · worst day 97%
48 days agonow
100.0%
Uptime 24h
91 of 91 checks
24
Tools
read from the server
417 ms
Response time
average over 24h
241
Installs / week
npm and PyPI
What changed 19
Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 14 August 2026. No other catalogue keeps this.
13 Aug
12 tools appeared
get_archive_career, get_archive_match, get_charting_match and 9 more
13 Aug
4 tools changed the parameters they ask for
get_fixtures, get_live_matches, get_recent_results and 1 more
13 Aug
2 tool descriptions were rewritten
get_live_matches, get_recent_results
13 Aug
a tool changed version
Nothing serious here today
Today is the operative word: we check Livetennisapi MCP every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 14 min ago.
run in your terminal
claude mcp add livetennisapi-mcp --transport http https://mcp.livetennisapi.com/mcp~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"livetennisapi-mcp": {
"url": "https://mcp.livetennisapi.com/mcp"
}
}
}~/.codex/config.toml
[mcp_servers.livetennisapi-mcp]
url = "https://mcp.livetennisapi.com/mcp".cursor/mcp.json
{
"mcpServers": {
"livetennisapi-mcp": {
"url": "https://mcp.livetennisapi.com/mcp"
}
}
}.vscode/mcp.json
{
"mcpServers": {
"livetennisapi-mcp": {
"url": "https://mcp.livetennisapi.com/mcp"
}
}
}This one needs environment variables set before it will start:
LIVETENNISAPI_KEY (Your Live Tennis API key (twjp_...). Get one free, no card, at https://livetennisapi.com/subscribe/free — the server runs without it but only the status check will work.).
The author declared them in the registry entry; get the values from the project itself.
Available tools 24
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
match
get_match
Full detail for one match by id: players, score, surface, round and status. Includes market prices on PRO and model analysis on ULTRA.
get_match_analysis
Model analysis for a match: predicted win probability, the model's thesis and the key factors behind it. Requires the ULTRA plan.
get_match_events
Timeline of events for a match — breaks, games won, sets won, momentum runs. Requires the PRO plan.
get_match_odds
Match-winner market prices for a match — implied probability per player, with bid, ask and mid. Requires the PRO plan.
get_match_score
Current score for one match — the fastest, lowest-latency read. Use this when you only need the score and already know the match id.
get_match_statistics
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.
archive
get_archive_career
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.
get_archive_match
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.
search_archive_matches
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.
search_archive_players
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.
charting
get_charting_match
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.
get_charting_player
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.
player
get_player
One player's profile: ranking, country, handedness, date of birth and cached stats.
get_player_rankings
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.
api
check_api_status
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.
fixtures
get_fixtures
Upcoming scheduled tennis fixtures, earliest first — the forward schedule.
h2h
get_h2h
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.
live
get_live_matches
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".
players
search_players
Search tennis players by name. Returns id, country, ranking and tour. Use the returned id with get_player.
rankings
get_rankings
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.
recent
get_recent_results
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.
tournament
get_tournament
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.
tournaments
search_tournaments
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.
upcoming
get_upcoming_matches
List tennis matches scheduled to start soon, with players and tournament.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://mcp.livetennisapi.com/mcp | streamable-http | answering | 398 ms | 14 min ago |
Alternatives to Livetennisapi MCP
same job, measured the same wayChess Results
by b77
Live chess tournament results and up-to-date player ratings in chat.
Sports MCP Server
by cyanheads
Get live scores, schedules, standings, team and player data for NFL, NBA, MLB, NHL, and soccer.
Voxodds
by voxodds
All-in outcome rankings with live depth, fees, verified rules, EV checks, and track records.
Predixsport
by predixsport
Probability-calibrated NBA, EuroLeague, football and ATP/WTA tennis predictions, full distributions
Sportscore MCP
by backspace-me
Live scores, standings, top scorers, brackets for football, basketball, cricket, tennis. Free API.
College Baseball
by blazesportsintel
Live NCAA DI college baseball scores, standings, schedules, rankings, and sabermetrics.
TruthScan
by truthscan
Detect whether an image is AI-generated or real, with an AI-probability score and confidence.
C
Tee Times
by loopgolf
Live golf tee time availability across US courses. Search by location, date, players, and price.
Livetennisapi MCP — questions
Answers built from our own checks of this server.
What can Livetennisapi MCP do?
It exposes 24 tools, read directly from the server on our last check. Among them: check_api_status, get_archive_career, get_archive_match, get_charting_match, get_charting_player, get_fixtures and 18 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README.
How MCP servers expose tools in the first place →
What is Livetennisapi MCP mostly used for?
Its tools cluster around match, archive and player. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is Livetennisapi MCP working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 417 ms. The bar chart above shows every period we have measured.
How do I connect Livetennisapi MCP?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Livetennisapi MCP need an API key?
No. Livetennisapi MCP completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 24 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Livetennisapi MCP?
It answers our handshake in 417 ms on average, which is faster than 36% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
How many people use Livetennisapi MCP?
The npm package livetennisapi-mcp was installed 241 times in the last week. Week over week that is -40%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is Livetennisapi MCP open source?
Yes — it is published under the MIT licence, written in TypeScript and 159 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.