Livetennisapi MCP Server

io.github.livetennisapi/livetennisapi-mcp

answering

Livetennisapi MCP is answering right now. Last checked 4 min ago. 221 installs a week from npm. It exposes 12 tools. Last commit 3 Aug 2026.

Real-time tennis scores, players, odds and model win-probability for ATP, WTA, Challenger, ITF.

Installs per day peak 685 · avg 55 · -78% w/w

a month agotoday

Uptime history 42 hours of history

42 hours agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

186 ms

Response time

average over 24h

221

Installs / week

npm and PyPI

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 4 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

~/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"
    }
  }
}

Available tools 12

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.

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.

live

get_live_matches

List tennis matches currently in progress, with live scores. Covers ATP, WTA, Challenger and ITF. Use this for "what tennis is on right now".

player

get_player

One player's profile: ranking, country, handedness, date of birth and cached stats.

players

search_players

Search tennis players by name. Returns id, country, ranking and tour. Use the returned id with get_player.

recent

get_recent_results

Recently completed tennis matches with final scores and winners.

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	181 ms	4 min ago

Livetennisapi MCP — questions

Answers built from our own checks of this server.

What can Livetennisapi MCP do?

It exposes 12 tools, read directly from the server on our last check. Among them: check_api_status, get_fixtures, get_live_matches, get_match, get_match_analysis, get_match_events and 6 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 →

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 186 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 12 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 186 ms on average, which is faster than 66% 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 221 times in the last week. Week over week that is -78%. 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 214 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.