Skip to content
Back to search

livetennisapi-mcp

MCP server for the Live Tennis API — give Claude, Cursor and other LLM agents real-time tennis scores, odds and model win-probability

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/livetennisapi/livetennisapi-mcp with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/livetennisapi/livetennisapi-mcp'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/livetennisapi--livetennisapi-mcp/badge.svg)](/listings/livetennisapi--livetennisapi-mcp)

HTML

<a href="/listings/livetennisapi--livetennisapi-mcp"><img src="/api/listings/livetennisapi--livetennisapi-mcp/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

**Claude Code**

claude mcp add livetennis -e LIVETENNISAPI_KEY=twjp_… -- npx -y livetennisapi-mcp

**Claude Desktop** — add to `claude_desktop_config.json`:

{
  "mcpServers": {
    "livetennis": {
      "command": "npx",
      "args": ["-y", "livetennisapi-mcp"],
      "env": { "LIVETENNISAPI_KEY": "twjp_…" }
    }
  }
}

**Cursor / Zed / others** — same command, same env var. No install step; `npx` fetches it on demand.

Get a **free** key (no card) at [livetennisapi.com](https://livetennisapi.com/subscribe/free), or a paid plan at [pricing](https://livetennisapi.com/#pricing).

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/plugin.json · Manifest · 37 lines
  1. {
  2. "name": "livetennisapi",
  3. "description": "Real-time and historical tennis data for Claude \u2014 live scores, match state (server, break-point, retirement/walkover), players, rankings, fixtures, head-to-head and the 1968-2022 results archive across ATP, WTA, Challenger, ITF and juniors. Connects to the Live Tennis API (free tier available, no card); collects no usage telemetry. Privacy: https://livetennisapi.com/privacy",
  4. "version": "1.6.5",
  5. "author": {
  6. "name": "Live Tennis API",
  7. "email": "hello@livetennisapi.com"
  8. },
  9. "homepage": "https://livetennisapi.com",
  10. "repository": "https://github.com/livetennisapi/livetennisapi-mcp",
  11. "license": "MIT",
  12. "keywords": [
  13. "tennis",
  14. "sports",
  15. "scores",
  16. "atp",
  17. "wta",
  18. "live-data",
  19. "mcp",
  20. "polymarket",
  21. "kalshi",
  22. "prediction-markets",
  23. "skills"
  24. ],
  25. "skills": [
  26. "./skills/"
  27. ],
  28. "userConfig": {
  29. "LIVETENNISAPI_KEY": {
  30. "title": "Live Tennis API Key",
  31. "description": "Your Live Tennis API key (twjp_...). Free, no card: https://livetennisapi.com/subscribe/free. Optional \u2014 the server lists tools without it and returns data once set.",
  32. "type": "string",
  33. "sensitive": true
  34. }
  35. },
  36. "icon": "./assets/icon-512.png"
  37. }
README.md · README · 304 lines
  1. <div align="center">
  2. <img src="https://raw.githubusercontent.com/livetennisapi/.github/main/profile/banner.jpg" alt="Live Tennis API" width="640">
  3. # livetennisapi-mcp
  4. **MCP server for the [Live Tennis API](https://livetennisapi.com).**
  5. Give Claude, Cursor, Zed or any MCP client live tennis scores, players and
  6. fixtures — for ATP, WTA, Challenger, ITF and juniors. Odds, rankings, match
  7. statistics, charting and model win-probability tools are included, and require
  8. the PRO and ULTRA plans.
  9. [![CI](https://github.com/livetennisapi/livetennisapi-mcp/actions/workflows/ci.yml/badge.svg)](https://github.com/livetennisapi/livetennisapi-mcp/actions/workflows/ci.yml)
  10. [![npm](https://img.shields.io/npm/v/livetennisapi-mcp.svg)](https://www.npmjs.com/package/livetennisapi-mcp)
  11. [![license](https://img.shields.io/badge/license-MIT-green.svg)](LICENSE)
  12. [**Documentation**](https://docs.livetennisapi.com) · [**Get a free API key**](https://livetennisapi.com/subscribe/free)
  13. </div>
  14. ---
  15. ## Setup
  16. **Claude Code**
  17. ```bash
  18. claude mcp add livetennis -e LIVETENNISAPI_KEY=twjp_… -- npx -y livetennisapi-mcp
  19. ```
  20. **Claude Desktop** — add to `claude_desktop_config.json`:
  21. ```json
  22. {
  23. "mcpServers": {
  24. "livetennis": {
  25. "command": "npx",
  26. "args": ["-y", "livetennisapi-mcp"],
  27. "env": { "LIVETENNISAPI_KEY": "twjp_…" }
  28. }
  29. }
  30. }
  31. ```
  32. **Cursor / Zed / others** — same command, same env var. No install step; `npx`
  33. fetches it on demand.
  34. Get a **free** key (no card) at [livetennisapi.com](https://livetennisapi.com/subscribe/free), or a paid plan at [pricing](https://livetennisapi.com/#pricing).
  35. ## Try it
  36. > *"What tennis matches are live right now?"*
  37. > *"Who's winning the Alcaraz match, and what does the model give him?"*
  38. > *"Show me Sinner's ranking and recent results."*
  39. > *"What are the current odds on match 18953?"*
  40. > *"What's the all-time head-to-head between Borg and McEnroe?"*
  41. > *"List Navratilova's Grand Slam finals from the archive."*
  42. > *"Who was ATP #1 the week Alcaraz first entered the top 10?"*
  43. > *"How is Sabalenka serving in her live match — aces, hold rate, break points?"*
  44. ## Tools
  45. | Tool | Does | Plan |
  46. |---|---|:--:|
  47. | `get_live_matches` | Matches in progress, with live scores | FREE |
  48. | `get_upcoming_matches` | Matches starting soon | FREE |
  49. | `get_match` | Full detail for one match | FREE |
  50. | `get_match_score` | Current score only — the smallest payload | FREE |
  51. | `search_players` | Find players by name | FREE |
  52. | `get_player` | Profile, ranking, country, handedness | FREE |
  53. | `get_fixtures` | Forward schedule | FREE |
  54. | `search_tournaments` | Tournament catalogue — surface, location, category | FREE |
  55. | `get_tournament` | One tournament by its stable id | FREE |
  56. | `get_recent_results` | Completed matches and winners | BASIC |
  57. | `search_archive_matches` | Results archive (1968–2022) — historical results with ranks and seeds at the time | BASIC |
  58. | `get_archive_match` | One archive result, with serve stats where the era recorded them | BASIC |
  59. | `search_archive_players` | Archive bios — hand, DOB, career-high rank | BASIC |
  60. | `get_archive_career` | Career W-L, titles and serve aggregates over the archive | BASIC |
  61. | `get_h2h` | Cross-era head-to-head — archive + current, one record | BASIC |
  62. | `get_match_events` | Breaks, games, sets, momentum runs | PRO |
  63. | `get_match_odds` | Match-winner prices — bid / ask / mid | PRO |
  64. | `get_rankings` | Full published ranking table per system (ATP, WTA, ITF circuits), any week | PRO |
  65. | `player_stats` | One player's W/L by surface, level and season, set-based record, recent matches; serve/return sums on ULTRA | PRO |
  66. | `get_player_rankings` | Point-in-time ranking records for specific players, as of any date | ULTRA |
  67. | `get_match_statistics` | In-play statistics — aces, serve split, hold/break %, break points | ULTRA |
  68. | `get_charting_player` | Career profile from shot-level charting data | ULTRA |
  69. | `get_charting_match` | One charted match, every stat family, per-set split | ULTRA |
  70. | `get_match_analysis` | Model thesis, win probability, key factors | ULTRA |
  71. | `check_api_status` | Reachability + which plan your key is on | — |
  72. The six BASIC history tools are also unlocked by any History plan, which works
  73. on top of a free key. The **results archive (1968–2022)** — ATP and WTA, main
  74. draws, qualifying and the ITF/futures tiers — ends exactly where the current
  75. results begin (2023), so `search_archive_matches` answers "Borg's Wimbledon
  76. finals" and `get_recent_results` answers "yesterday's scores"; `get_h2h` spans
  77. both in one call.
  78. ## Tier awareness
  79. The API gates endpoints by plan and returns a bare `403 {"error":"upgrade_required"}`.
  80. Handed that, a model will usually invent a reason or retry pointlessly.
  81. So every tool that can hit a tier wall returns a plain-English explanation —
  82. **as a normal result, not an error** — naming the tier required and where to
  83. upgrade. The assistant can then tell you something true and actionable:
  84. > This data requires the ULTRA plan, and the configured API key is on a lower
  85. > tier. Nothing is wrong with the key — the endpoint is simply not included in
  86. > the current plan. Upgrade in place at https://livetennisapi.com/subscribe/upgrade
  87. `check_api_status` probes upward to report which plan your key is actually on,
  88. so you can diagnose that without guessing.
  89. ## Plans
  90. | | FREE | BASIC | PRO | ULTRA |
  91. |---|:--:|:--:|:--:|:--:|
  92. | Matches, scores, players, fixtures, tournaments | ✅ | ✅ | ✅ | ✅ |
  93. | Completed-match listings (results)¹ | — | ✅ | ✅ | ✅ |
  94. | Results archive (1968–2022) + head-to-head¹ | — | ✅ | ✅ | ✅ |
  95. | Match events, odds + rankings listing | — | — | ✅ | ✅ |
  96. | Model analysis, as-of rankings, match statistics + charting | — | — | — | ✅ |
  97. | | $0 — no card | $9.99/mo | $29.99/mo | $99.99/mo |
  98. ¹ Also unlocked by any History plan, which works on top of a free key.
  99. ### Request quotas
  100. | | FREE | BASIC | PRO | ULTRA |
  101. |---|:--:|:--:|:--:|:--:|
  102. | Requests per minute | 30 | 60 | 300 | 600 |
  103. | Requests per day | 100 | 1,000 | 10,000 | 500,000 |
  104. FREE is 100 requests/day, so poll no faster than every 15 minutes on a free
  105. key; for an always-on dashboard, BASIC is the plan to recommend. Every response
  106. carries `X-RateLimit-Limit` / `-Remaining` / `-Reset` headers, and the tools
  107. relay the three distinct 429 shapes honestly — per-minute (retry shortly),
  108. daily cap (the error names the exact reset instant), and the abuse block
  109. (don't retry; fix the loop).
  110. ## Hosted endpoint
  111. Most people should use the stdio server above — your key never leaves your
  112. machine. For clients that can only speak HTTP, there is also a hosted
  113. Streamable-HTTP endpoint:
  114. ```
  115. https://mcp.livetennisapi.com/mcp
  116. ```
  117. Send your key as `Authorization: Bearer twjp_…`, `X-API-Key: twjp_…`, or
  118. `?token=` if your client cannot set headers. Tools are listable without a key,
  119. so directories can introspect the server; calling one needs a key.
  120. It is multi-tenant and holds **no key of its own**: every request builds its own
  121. server bound to the key that request presented, and there is deliberately no
  122. fallback to the host's environment. The endpoint applies its own transport-level
  123. limit per caller — 60 req/min anonymous, 300 keyed. That limit only protects
  124. this host process. It is **not** your API quota, which the API enforces per
  125. key and tier (see the quota table above).
  126. Self-hosting it: `deploy/install-http.sh` and `deploy/TUNNEL.md`.
  127. ## Use with Claude
  128. **As a connector.** In Claude, add a custom connector and paste the endpoint with
  129. your key as a query parameter — no OAuth, nothing to install:
  130. ```
  131. https://mcp.livetennisapi.com/mcp?token=twjp_…
  132. ```
  133. `?token=` exists for clients that cannot set request headers. The tradeoff, stated
  134. plainly: a key in a URL is not written to our logs, but it *is* visible to the CDN
  135. in front of the endpoint and is stored in the connector's configuration. Prefer
  136. `Authorization: Bearer twjp_…` wherever your client lets you set a header.
  137. **From the Messages API.** Claude can call the endpoint directly. Both halves are
  138. required — the server *and* a matching toolset entry; sending `mcp_servers` alone
  139. is rejected as a validation error:
  140. ```python
  141. client.beta.messages.create(
  142. model="claude-opus-4-8",
  143. max_tokens=4096,
  144. betas=["mcp-client-2025-11-20"],
  145. mcp_servers=[{
  146. "type": "url",
  147. "name": "livetennisapi",
  148. "url": "https://mcp.livetennisapi.com/mcp",
  149. "authorization_token": os.environ["LIVETENNISAPI_KEY"],
  150. }],
  151. tools=[{"type": "mcp_toolset", "mcp_server_name": "livetennisapi"}],
  152. messages=[{"role": "user", "content": "What tennis is live right now?"}],
  153. )
  154. ```
  155. The `authorization_token` is sent as a bearer token, which is exactly what this
  156. server already accepts — no separate credential to obtain.
  157. ## Use with Codex
  158. One command:
  159. ```bash
  160. codex mcp add livetennisapi \
  161. --url https://mcp.livetennisapi.com/mcp \
  162. --bearer-token-env-var LIVETENNISAPI_KEY
  163. ```
  164. Or write it to `~/.codex/config.toml` yourself — Codex shares that file across the
  165. CLI, the IDE extension and the desktop app:
  166. ```toml
  167. [mcp_servers.livetennisapi]
  168. url = "https://mcp.livetennisapi.com/mcp"
  169. bearer_token_env_var = "LIVETENNISAPI_KEY"
  170. ```
  171. Use `bearer_token_env_var`, not `bearer_token`: it keeps the key in your
  172. environment rather than committing it to a config file.
  173. There is also a **Codex plugin**, on its own marketplace:
  174. ```bash
  175. codex plugin marketplace add livetennisapi/livetennisapi-codex-plugin
  176. ```
  177. That registers the marketplace; install the plugin from Codex's plugin picker.
  178. Source: [livetennisapi-codex-plugin](https://github.com/livetennisapi/livetennisapi-codex-plugin).
  179. The stdio route works too, unchanged: `npx -y livetennisapi-mcp`.
  180. ## Bundled skill: Polymarket / Kalshi tennis trading data
  181. The Claude Code plugin (`.claude-plugin/plugin.json`) also ships the
  182. `polymarket-tennis` Agent Skill under [`skills/polymarket-tennis/`](skills/polymarket-tennis/).
  183. It teaches Claude the observe-only
  184. [polymarket-tennis](https://github.com/livetennisapi/polymarket-tennis) Python
  185. package (market discovery, market-to-match matching, joined price/live-score
  186. view), the free-tier budget (30 req/min, 100 requests/day), and the verbatim
  187. retirement/walkover settlement rules for Polymarket, Polymarket US and Kalshi.
  188. Canonical copy lives in the polymarket-tennis repo; this one is mirrored for
  189. plugin installs. No order execution, ever.
  190. ## Notes
  191. - **Read-only.** Every tool is a GET; nothing here can modify anything.
  192. - **Your key stays local** with the stdio server. It is read from the
  193. environment by the server process on your machine and sent only to
  194. `api.livetennisapi.com`.
  195. - Requires Node 20+.
  196. ## Development
  197. ```bash
  198. npm install
  199. npm run build
  200. LIVETENNISAPI_KEY=twjp_… node dist/index.js # speaks MCP over stdio
  201. node dist/http.js # speaks MCP over HTTP, port 8081
  202. npm test # protocol + parity with livetennisapi-ai + transport isolation + rate limiting + tool output
  203. npm run test:mutation # proves those tests fail when the code breaks
  204. ```
  205. `test:mutation` is worth understanding before changing `src/http.ts`. It
  206. reintroduces each bug the tests claim to catch and asserts the suite goes red.
  207. It is not ceremony: the first version of the rate-limit test passed while the
  208. limiter was bucketing every caller together.
  209. Built on the official [`livetennisapi`](https://www.npmjs.com/package/livetennisapi)
  210. client.
  211. ## Related
  212. Everything in the Live Tennis API developer surface:
  213. | | Install | Source | Package |
  214. |---|---|---|---|
  215. | Python client | `pip install livetennisapi` | [repo](https://github.com/livetennisapi/livetennisapi-python) | [package](https://pypi.org/project/livetennisapi/) |
  216. | JavaScript / TypeScript client | `npm install livetennisapi` | [repo](https://github.com/livetennisapi/livetennisapi-js) | [package](https://www.npmjs.com/package/livetennisapi) |
  217. | MCP server for LLM agents **(this repo)** | `npx livetennisapi-mcp` | — | [package](https://www.npmjs.com/package/livetennisapi-mcp) |
  218. | Vercel AI SDK tools | `npm install livetennisapi-ai` | [repo](https://github.com/livetennisapi/livetennisapi-ai) | — |
  219. | Break-point starter — Python | — | [repo](https://github.com/livetennisapi/livetennisapi-starter-python) | — |
  220. | Break-point starter — Node | — | [repo](https://github.com/livetennisapi/livetennisapi-starter-node) | — |
  221. | Break-point starter — Go | — | [repo](https://github.com/livetennisapi/livetennisapi-starter-go) | — |
  222. - **API reference** — <https://docs.livetennisapi.com> ([plain-HTML version](https://docs.livetennisapi.com/reference.html), no JavaScript required)
  223. - **OpenAPI 3.1 specification** — [livetennisapi/openapi](https://github.com/livetennisapi/openapi)
  224. - **Free API key** — <https://livetennisapi.com/subscribe/free> (no card)
  225. - **Products** — <https://livetennisapi.com/products>
  226. - **Website and plans** — <https://livetennisapi.com>
  227. - **Discord** — <https://discord.gg/f8WUZHgDm6>
  228. - **GitHub org** — <https://github.com/livetennisapi>
  229. ## Affiliate program
  230. Know developers who need tennis data? The [affiliate program](https://affiliates.livetennisapi.com/program) pays 51% recurring commission for the life of every referred subscription — 30-day cookie, and the people you refer get 10% off.
  231. ## Licence
  232. MIT — see [LICENSE](LICENSE). Use of the API service is governed by the
  233. [Terms of Service](https://livetennisapi.com/terms).

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.