check_api_status — livetennisapi mcp MCP Tool Read-only
check_api_status
(check api status) is one of 24 tools on the
livetennisapi mcp
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call check_api_status from your client
- Claude Code livetennisapi mcp check_api_status run in your project directory
- Claude Desktop livetennisapi mcp check_api_status ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor livetennisapi mcp check_api_status ~/.cursor/mcp.json
- VS Code livetennisapi mcp check_api_status .vscode/mcp.json
- Zed livetennisapi mcp check_api_status ~/.config/zed/settings.json
- Windsurf livetennisapi mcp check_api_status ~/.codeium/windsurf/mcp_config.json
- Cline livetennisapi mcp check_api_status ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI livetennisapi mcp check_api_status ~/.gemini/settings.json
- Grok livetennisapi mcp check_api_status .mcp.json (in your project root)
- ChatGPT livetennisapi mcp check_api_status Settings → Connectors → Advanced → Developer mode
- Claude.ai livetennisapi mcp check_api_status Settings → Connectors → Add custom connector
- LangChain livetennisapi mcp check_api_status pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http livetennisapi-mcp https://mcp.livetennisapi.com/mcpOther tools on this server
- get_live_matches
- get_upcoming_matches
- get_match
- get_match_score
- search_players
- get_player
- get_fixtures
- search_tournaments
- get_tournament
- get_recent_results
- search_archive_matches
- get_archive_match
- search_archive_players
- get_archive_career
- get_h2h
- get_match_events
- get_match_odds
- get_rankings
- get_match_analysis
- get_player_rankings
- get_match_statistics
- get_charting_player
- get_charting_match
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.