get_fighter_record — PXL8 verified fight records MCP Tool Read-only
get_fighter_record
(get fighter record) is one of 7 tools on the
PXL8 verified fight records
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_fighter_record from your client
- Claude Code PXL8 verified fight records get_fighter_record run in your project directory
- Claude Desktop PXL8 verified fight records get_fighter_record ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor PXL8 verified fight records get_fighter_record ~/.cursor/mcp.json
- VS Code PXL8 verified fight records get_fighter_record .vscode/mcp.json
- Zed PXL8 verified fight records get_fighter_record ~/.config/zed/settings.json
- Windsurf PXL8 verified fight records get_fighter_record ~/.codeium/windsurf/mcp_config.json
- Cline PXL8 verified fight records get_fighter_record ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI PXL8 verified fight records get_fighter_record ~/.gemini/settings.json
- Grok PXL8 verified fight records get_fighter_record .mcp.json (in your project root)
- ChatGPT PXL8 verified fight records get_fighter_record Settings → Connectors → Advanced → Developer mode
- Claude.ai PXL8 verified fight records get_fighter_record Settings → Connectors → Add custom connector
- LangChain PXL8 verified fight records get_fighter_record pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http records https://api.pxl8.io/sports-data/mcpOther tools on this server
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.