io.github.livetennisapi/livetennisapi-mcp

REMOTE · MCP.LIVETENNISAPI.COM · 2 COMPONENTS · SCANNED AUG 3

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

Available components

remote · mcp.livetennisapi.com 70 npm · livetennisapi-mcp 31

+4 this week 70 70 Trust /100

Trust breakdown (6 categories)

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 →

Endpoint Security63

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 not yet verified: we couldn't determine whether a plaintext access path exists. View diagnostics → Unverified
HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail

Transport & Reachability100

Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass

Schema Quality & AI Usability79

AI-judged instruction clarity (excellent).Pass
Tool/resource definitions use about 652 tokens (~54/item across 12 items; 12 tools + 0 resources), lean.Pass
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management27

Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

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

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · mcp.livetennisapi.com

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

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

# ~/.codex/config.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
    }
  }
}

# add to OpenClaw

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

# ~/.hermes/config.yaml

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

// mcp.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 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.

3 Aug 26 +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.
31 Jul 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
30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
29 Jul 26 +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.
28 Jul 26 +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.
27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
26 Jul 26 66

First indexed and scored.

Show 6 earlier entries Hide earlier entries

Diagnostics

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 3 Aug 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	18 Jul 2026	16 Oct 2026	ECDSA 256	ECDSA-SHA256	cdafdf32602cd62b0eef8e5620cf290b
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

DNSSEC insecure

Validation of mcp.livetennisapi.com. — Not signed

Zone	DS	Keys	Algorithms	Outcome
.	trust_anchor	20326, 38696	8, 8	Verified
com.	present	19718	13	Verified
livetennisapi.com.	absent			Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation

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

Transports 2 probes

Transport	URL	Outcome	Status	Location
streamable-http	https://mcp.livetennisapi.com/mcp	Verified	200
http (plaintext)	http://mcp.livetennisapi.com/mcp	Inconclusive	405

MCP tools — 12 exposed · ~652 tokens

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.

Tool Tokens

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 Output Examples

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_fixtures Fixture schedule ~37

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

Input Output Examples

Name	Type	Req	Description
limit	integer	—	Maximum fixtures to return (1-200).

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_live_matches Live matches ~57

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 Output Examples

Name	Type	Req	Description
limit	integer	—	Maximum matches to return (1-200).

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 ~64

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

Input Output Examples

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 ~62

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

Input Output Examples

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.

Input Output Examples

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 ~78

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

Input Output Examples

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 ~65

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 Output Examples

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_player Player profile ~42

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

Input Output Examples

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_recent_results Recent results ~34

Recently completed tennis matches with final scores and winners.

Input Output Examples

Name	Type	Req	Description
limit	integer	—	Maximum matches to return (1-200).

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_upcoming_matches Upcoming matches ~38

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

Input Output Examples

Name	Type	Req	Description
limit	integer	—	Maximum matches to return (1-200).

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_players Search players ~66

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

Input Output Examples

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.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

26 Jul 3 Aug

Day	Score
26 Jul	66
27 Jul	66
28 Jul	67
29 Jul	68
30 Jul	68
31 Jul	69
1 Aug	69
2 Aug	69
3 Aug	70