Livetennisapi MCP Server

by livetennisapi Your server? Claim it

answering

Livetennisapi MCP is answering right now. Last checked 6 min ago. 610 installs a week from npm. It exposes 25 tools.

Live tennis scores, players, rankings, odds and win-probability. ATP, WTA, Challenger, ITF, juniors.

The linked repository no longer exists on GitHub — it was deleted or made private.

Installs per day peak 184 · avg 18 · -5% w/w

a month agotoday

Uptime history 91 days of history · worst day 93%

91 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

427 ms

Response time

average over 24h

610

Installs / week

npm and PyPI

What changed 62

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 14 August 2026. No other catalogue keeps this.

28 Oct 18 tool descriptions were rewritten check_api_status, get_archive_career, get_archive_match and 15 more

28 Oct 11 tools changed the parameters they ask for check_api_status, get_archive_career, get_charting_match and 8 more

28 Oct a tool appeared player_stats

28 Oct a tool changed version

20 Sep 11 tool descriptions were rewritten get_fixtures, get_live_matches, get_match and 8 more

20 Sep a tool changed version

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

This one has been quiet for a while

Quiet is not dead — but it is worth knowing when it wakes up, or when someone else takes it over. We watch the repository and tell you either way.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 6 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add livetennisapi-mcp --transport http https://mcp.livetennisapi.com/mcp

Settings → Connectors → Add custom connector, then paste this address

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

{
  "servers": {
    "livetennisapi-mcp": {
      "type": "http",
      "url": "https://mcp.livetennisapi.com/mcp"
    }
  }
}

Available tools 25

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. Works on the FREE plan (no card needed).

get_match_analysis

Model analysis for a match: predicted win probability, the model's thesis and the main factors behind it. Requires the ULTRA plan. Match rows carry has_analysis, so check it first. A match with no thesis or profile has nothing to return.

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. Match rows carry has_market, so check it first. A match with no market mapped has no prices to return.

get_match_score

Current score for one match. This is the fastest read, with the lowest latency. Use it when you only need the score and already know the match id. Works on the FREE plan (no card needed).

get_match_statistics

In-play (or final) statistics for one match, in TWO families kept separate on purpose. DERIVED is rebuilt from the point-by-point record (holds/breaks, break points, service/return points). MEASURED is counted per match. It 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 to 2022). W-L record in total and by surface/level/year, titles, and summed serve statistics. The corpus records serve stats from 1991 only, so matches_with_stats says 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 to 2022), with per-match serve statistics where the era recorded them. Stats are null for most rows before 1991, 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. Each record has winner and loser, final score, and 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 the current results (get_recent_results) begin. Requires the BASIC plan or any History plan.

search_archive_players

The people of the results archive (1968 to 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.

player

get_player

One player's profile: ranking, country, handedness, date of birth and cached stats. Works on the FREE plan (no card needed).

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 one 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.

player_stats

One player's record over completed singles matches from 2023 onward, by default the last 365 days. It gives W/L overall, over the last 12 months and by surface, venue, level and season. It also gives tiebreaks, deciding sets, the record after winning or losing the first set, comebacks, withdrawals and the last N matches. Every count carries its sample size, and a percentage on an empty sample is null, never 0. On ULTRA it adds serve_return: measured serve and return statistics summed over the window. Singles only, so a doubles-team id is refused. For 1968 to 2022 use get_archive_career. Requires the PRO plan (serve_return requires ULTRA).

charting

get_charting_match

Every charting 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 to 2026). Most of these matches have no counterpart in the live tables. Requires the ULTRA plan.

get_charting_player

Career profile from shot-level charting data, summed over the player's charted matches. Serve placement (deuce/ad x wide/body/T), return depth and outcomes, net play, and clutch break/game/set-point serving. Also winners and errors by wing, and rally-length tendencies. COVERAGE IS CURATED, not full-slate: 11,646 charted matches back to the 1960s, concentrated on the majors. An ambiguous name returns the candidates to choose from. Requires the ULTRA plan.

api

check_api_status

Check whether the Live Tennis API is reachable and which plan the configured key is on. Use it to find out why other tools are refusing data. Works with no key.

fixtures

get_fixtures

Upcoming scheduled tennis fixtures, earliest first. This is the forward schedule, filterable by tour. Use this for "what is on this week". Works on the FREE plan (no card needed).

h2h

get_h2h

The all-time record between two players, across BOTH halves of the product. That is the results archive (1968 to 2022) plus the completed matches from 2023 onward. Names are the keys. An ambiguous fragment returns the candidate list to choose from, and nothing is guessed. 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". Works on the FREE plan (no card needed).

players

search_players

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).

rankings

get_rankings

The FULL published ranking table in rank order for one system, from 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. Works on the FREE plan (no card needed).

tournaments

search_tournaments

Search the tournament catalogue. Its ids are the tournament_id that match objects carry. Returns surface, indoor, host city/country and category where curated. Works on the FREE plan (no card needed).

upcoming

get_upcoming_matches

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).

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.livetennisapi.com/mcp	streamable-http	answering	398 ms	6 min ago

Alternatives to Livetennisapi MCP

same job, measured the same way

Chess Results

by b77

Live chess tournament results and up-to-date player ratings in chat.

answering

KashRock MCP

by kashrock

Esports props, odds, live scores, and player stats across 8 titles for agents.

182 installs/wk local only

SportAPI Football Data

by sportapi

Football fixtures, live scores, standings, lineups, teams and players for 117 leagues and cups

13 tools answering

LiveScore MCP by Nova (CIVAI)

by civai-nova

Live football scores, fixtures, teams, and players.

10 tools answering

Aura

by aura

Live sports data: scores, play-by-play, box scores, odds and props. No key needed to start.

18 tools answering

TypeBid 标探

by typebid

Search public tenders in China, inspect buyers, and estimate bid win probability.

answering

Sports MCP Server

by cyanheads

Get live scores, schedules, standings, team and player data for NFL, NBA, MLB, NHL, and soccer.

200 installs/wk local only

FootVal

by footval

Football match predictions, title race chances, player valuations, live scores, tables and news.

answering

Livetennisapi MCP — questions

Answers built from our own checks of this server.

What can Livetennisapi MCP do?

It exposes 25 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 19 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 427 ms. The bar chart above shows every period we have measured.

Is Livetennisapi MCP still maintained?

The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.

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 in the form 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 25 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 427 ms on average, which is faster than 30% 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 610 times in the last week. Week over week that is -5%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.