find_time_loss — Rush SR Lap Analyzer MCP Tool Read-only
find_time_loss
(find time loss) is one of 4 tools on the
Rush SR Lap Analyzer
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call find_time_loss from your client
- Claude Code Rush SR Lap Analyzer find_time_loss run in your project directory
- Claude Desktop Rush SR Lap Analyzer find_time_loss ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Rush SR Lap Analyzer find_time_loss ~/.cursor/mcp.json
- VS Code Rush SR Lap Analyzer find_time_loss .vscode/mcp.json
- Zed Rush SR Lap Analyzer find_time_loss ~/.config/zed/settings.json
- Windsurf Rush SR Lap Analyzer find_time_loss ~/.codeium/windsurf/mcp_config.json
- Cline Rush SR Lap Analyzer find_time_loss ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Rush SR Lap Analyzer find_time_loss ~/.gemini/settings.json
- Grok Rush SR Lap Analyzer find_time_loss .mcp.json (in your project root)
- ChatGPT Rush SR Lap Analyzer find_time_loss Settings → Connectors → Advanced → Developer mode
- Claude.ai Rush SR Lap Analyzer find_time_loss Settings → Connectors → Add custom connector
- LangChain Rush SR Lap Analyzer find_time_loss pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http lap-analyzer https://laps.mcp.rush.sr/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 1 October 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.