# io.github.livetennisapi/livetennisapi-mcp (remote · mcp.livetennisapi.com)

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

- Trust score: 70/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `mcp.livetennisapi.com`: 70/100 (this document), [markdown](https://verifymcp.io/servers/livetennisapi-livetennisapi-mcp/mcp.md), [page](https://verifymcp.io/servers/livetennisapi-livetennisapi-mcp/mcp)
- npm · `livetennisapi-mcp`: 31/100, [markdown](https://verifymcp.io/servers/livetennisapi-livetennisapi-mcp/livetennisapi-mcp.md), [page](https://verifymcp.io/servers/livetennisapi-livetennisapi-mcp/livetennisapi-mcp)

## Channel facts

- Endpoint: `https://mcp.livetennisapi.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.3.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS not yet verified: we couldn't determine whether a plaintext access path exists.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 79/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 652 tokens (~54/item across 12 items; 12 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

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

### Codex

```toml
[mcp_servers.livetennisapi-livetennisapi-mcp]
url = "https://mcp.livetennisapi.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "livetennisapi-livetennisapi-mcp": {
      "type": "remote",
      "url": "https://mcp.livetennisapi.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add livetennisapi-livetennisapi-mcp --url https://mcp.livetennisapi.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  livetennisapi-livetennisapi-mcp:
    url: "https://mcp.livetennisapi.com/mcp"
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 70, +1)

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

### 2026-07-31 (score 69, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 68, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 68, +1)

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

### 2026-07-28 (score 67, +1)

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

### 2026-07-27 (score 66, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 66)

First indexed and scored.

## MCP tools (12)

### `get_live_matches` (~57 tokens)

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

Input parameters:

- `limit` (integer): Maximum matches to return (1-200).

Output parameters:

- `matches` (array): The live matches, most relevant first.
- `message` (string): Human-readable summary. Identical to the text content, so either half can be used alone.
- `ok` (boolean): 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.

### `get_upcoming_matches` (~38 tokens)

Upcoming matches

List tennis matches scheduled to start soon, with players and tournament.

Input parameters:

- `limit` (integer): Maximum matches to return (1-200).

Output parameters:

- `matches` (array): Matches due to start, soonest first.
- `message` (string): Human-readable summary. Identical to the text content, so either half can be used alone.
- `ok` (boolean): 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.

### `get_match` (~64 tokens)

Match detail

Full detail for one match by id: players, score, surface, round and status. Includes market prices on PRO and model analysis on ULTRA.

Input parameters:

- `match_id` (integer, required): Match id, as returned by get_live_matches, get_upcoming_matches or get_recent_results.

Output parameters:

- `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): Human-readable summary. Identical to the text content, so either half can be used alone.
- `ok` (boolean): 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.

### `get_match_score` (~65 tokens)

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.

Input parameters:

- `match_id` (integer, required): Match id, as returned by get_live_matches, get_upcoming_matches or get_recent_results.

Output parameters:

- `message` (string): Human-readable summary. Identical to the text content, so either half can be used alone.
- `ok` (boolean): 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.

### `search_players` (~66 tokens)

Search players

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

Input parameters:

- `limit` (integer): Maximum players to return (1-200).
- `query` (string, required): Full or partial player name, e.g. "alcaraz".

Output parameters:

- `message` (string): Human-readable summary. Identical to the text content, so either half can be used alone.
- `ok` (boolean): 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.

### `get_player` (~42 tokens)

Player profile

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

Input parameters:

- `player_id` (integer, required): Player id, as returned by search_players.

Output parameters:

- `message` (string): Human-readable summary. Identical to the text content, so either half can be used alone.
- `ok` (boolean): 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.

### `get_fixtures` (~37 tokens)

Fixture schedule

Upcoming scheduled tennis fixtures, earliest first — the forward schedule.

Input parameters:

- `limit` (integer): Maximum fixtures to return (1-200).

Output parameters:

- `fixtures` (array): Scheduled fixtures, earliest first.
- `message` (string): Human-readable summary. Identical to the text content, so either half can be used alone.
- `ok` (boolean): 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.

### `get_recent_results` (~34 tokens)

Recent results

Recently completed tennis matches with final scores and winners.

Input parameters:

- `limit` (integer): Maximum matches to return (1-200).

Output parameters:

- `matches` (array): Completed matches, most recent first.
- `message` (string): Human-readable summary. Identical to the text content, so either half can be used alone.
- `ok` (boolean): 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.

### `get_match_events` (~73 tokens)

Match timeline

Timeline of events for a match — breaks, games won, sets won, momentum runs. Requires the PRO plan.

Input parameters:

- `limit` (integer): Maximum events to return (1-200).
- `match_id` (integer, required): Match id, as returned by get_live_matches, get_upcoming_matches or get_recent_results.

Output parameters:

- `events` (array): Events in chronological order.
- `message` (string): Human-readable summary. Identical to the text content, so either half can be used alone.
- `ok` (boolean): 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.

### `get_match_odds` (~78 tokens)

Match market prices

Match-winner market prices for a match — implied probability per player, with bid, ask and mid. Requires the PRO plan.

Input parameters:

- `limit` (integer): Maximum price points to return (1-200).
- `match_id` (integer, required): Match id, as returned by get_live_matches, get_upcoming_matches or get_recent_results.

Output parameters:

- `market` (object): The match-winner market.
- `message` (string): Human-readable summary. Identical to the text content, so either half can be used alone.
- `ok` (boolean): 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.

### `get_match_analysis` (~62 tokens)

Model analysis

Model analysis for a match: predicted win probability, the model's thesis and the key factors behind it. Requires the ULTRA plan.

Input parameters:

- `match_id` (integer, required): Match id, as returned by get_live_matches, get_upcoming_matches or get_recent_results.

Output parameters:

- `message` (string): Human-readable summary. Identical to the text content, so either half can be used alone.
- `ok` (boolean): 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.

### `check_api_status` (~36 tokens)

API status and plan

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.

Output parameters:

- `api_version` (string|null): API version reported by the health check.
- `has_key` (boolean): Whether a key was supplied with this call.
- `message` (string): Human-readable summary. Identical to the text content, so either half can be used alone.
- `ok` (boolean): 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.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/livetennisapi-livetennisapi-mcp/mcp#diagnostics

## Score history

- 2026-08-03: 70
- 2026-08-02: 69
- 2026-08-01: 69
- 2026-07-31: 69
- 2026-07-30: 68
- 2026-07-29: 68
- 2026-07-28: 67
- 2026-07-27: 66
- 2026-07-26: 66

## Links

- Remote endpoint: https://mcp.livetennisapi.com/mcp
- Repository: https://github.com/livetennisapi/livetennisapi-mcp
- Website: https://livetennisapi.com/
- Changelog RSS feed: https://verifymcp.io/servers/livetennisapi-livetennisapi-mcp/mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/livetennisapi-livetennisapi-mcp/mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/livetennisapi-livetennisapi-mcp/mcp