Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/livetennisapi/livetennisapi-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/livetennisapi/livetennisapi-mcp/livetennis)<a href="https://agentmods.dev/mcp/livetennisapi/livetennisapi-mcp/livetennis"><img src="https://agentmods.dev/badge/mcp/livetennisapi/livetennisapi-mcp/livetennis/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/livetennisapi/livetennisapi-mcp/livetennis"><img src="https://agentmods.dev/badge/mcp/livetennisapi/livetennisapi-mcp/livetennis.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket warn
Grade A, and why
livetennis scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 17d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"livetennis": {
"command": "npx",
"args": [
"-y",
"[email protected]"
],
"env": {
"LIVETENNISAPI_KEY": "${user_config.LIVETENNISAPI_KEY}"
}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 17d ago Changed · +3 lines e446b8aca250
- 2mo ago First seen · 9 lines scan A 699fcf5c76d4
livetennis is an MCP server published in the GitHub repository livetennisapi/livetennisapi-mcp (135 stars, last pushed 2d ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
livetennis compared with mcp servers from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| livetennislivetennisapi/livetennisapi-mcp | MCP server | 135 | 2d ago | MIT | A | — | Claude Code |
| context7upstash/context7 | MCP server | 65k | today | MIT | A | — | Claude Code, Codex, Cursor, Gemini CLI, OpenCode |
| excel-mcp-serverharis-musa/excel-mcp-server | MCP server | 4.3k | today | MIT | A | — | Claude Code, Codex, Cursor, Gemini CLI, OpenCode |
| IlyaGusev-academia_mcpIlyaGusev/academia_mcp | MCP server | 94 | 18d ago | Apache-2.0 | A | — | Claude Code, Codex, Cursor, Gemini CLI, OpenCode |
| email-mcpcodefuturist/email-mcp | MCP server | 161 | today | LGPL-3.0 | A | — | Claude Code, Codex, Cursor, Gemini CLI, OpenCode |
| web-accessusestring/string-ai-mcp | MCP server | 7 | today | MIT | A | — | Claude Code, Codex, Cursor, Gemini CLI, OpenCode |
| office-oxide-mcpAimino-Tech/opendocswork-mcp | MCP server | 164 | 6d ago | GPL-3.0 | A | — | Claude Code, Codex, Cursor, Gemini CLI, OpenCode |