Validate Formhaus form definitions and simulate multi-step paths against the real engine.
Nothing to run from here
Livetennisapi is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
100/100
trust score
13
downloads a day
local
runs on your machine
580
downloads in 30d
What it does
MCP server for the Live Tennis API — give Claude, Cursor and other LLM agents real-time tennis scores, players and fixtures for ATP, WTA, Challenger and ITF. Odds and model win-probability tools require the PRO and ULTRA plans.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user livetennisapi-mcp '--' npx -y livetennisapi-mcp
# 2 — ask your agent for something these tools do
# get_live_matches, get_upcoming_matches, get_match and 21 more
Livetennisapi costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
LIAll 1 server
livetennisapi1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Livetennisapi as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user livetennisapi-mcp '--' npx -y livetennisapi-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
Nothing is required, but it can take 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 w) if you want to set it.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
24 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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).
No parameter schema on file.
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).
No parameter schema on file.
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).
No parameter schema on file.
Current score for one match — the fastest, lowest-latency read. Use this when you only need the score and already know the match id. Works on the FREE plan (no card needed).
No parameter schema on file.
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).
No parameter schema on file.
One player's profile: ranking, country, handedness, date of birth and cached stats. Works on the FREE plan (no card needed).
No parameter schema on file.
Upcoming scheduled tennis fixtures, earliest first — the forward schedule, filterable by tour, player and date. Use this for "what is on this week". Works on the FREE plan (no card needed).
No parameter schema on file.
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. Works on the FREE plan (no card needed).
No parameter schema on file.
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).
No parameter schema on file.
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.
No parameter schema on file.
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…
No parameter schema on file.
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.
No parameter schema on file.
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…
No parameter schema on file.
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…
No parameter schema on file.
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…
No parameter schema on file.
Timeline of events for a match — breaks, games won, sets won, momentum runs. Requires the PRO plan.
No parameter schema on file.
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 — check it first; a match with no market mapped has no prices to return.
No parameter schema on file.
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…
No parameter schema on file.
Model analysis for a match: predicted win probability, the model's thesis and the key factors behind it. Requires the ULTRA plan. Match rows carry has_analysis — check it first; a match with no thesis or profile has nothing to return.
No parameter schema on file.
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…
No parameter schema on file.
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…
No parameter schema on file.
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…
No parameter schema on file.
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.
No parameter schema on file.
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.
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Livetennisapi or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 100 / 100
Release 1.5.0 · scanned 14 Oct 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score100
Findings0 threat · 0 capability
Capabilityminimal
Coveragesource
Verificationsource
Surface digest8f836459341e03221b822892022b0c0a5767b6ef74fcde36a2a510032e07fcdc
Score vectorthreat 100 → client 100
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (24 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| get_live_matches | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_upcoming_matches | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_match | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_match_score | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| search_players | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_player | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_fixtures | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| search_tournaments | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_tournament | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_recent_results | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| search_archive_matches | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_archive_match | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| search_archive_players | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_archive_career | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_h2h | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_match_events | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_match_odds | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_rankings | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_match_analysis | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_player_rankings | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_match_statistics | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_charting_player | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_charting_match | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| check_api_status | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest8f836459341e0322
Scanned2026-10-14
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 1.5.0. Pin a release below and the command asks for exactly that one.
1.5.0
14 Sep 2026
latestNo release note was published with this version.
1.4.0
undated
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Livetennisapi can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.