get_request_status — Snapback MCP Tool Read-only
get_request_status
(get request status) is one of 23 tools on the
Snapback
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_request_status from your client
- Claude Code Snapback get_request_status run in your project directory
- Claude Desktop Snapback get_request_status ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Snapback get_request_status ~/.cursor/mcp.json
- VS Code Snapback get_request_status .vscode/mcp.json
- Zed Snapback get_request_status ~/.config/zed/settings.json
- Windsurf Snapback get_request_status ~/.codeium/windsurf/mcp_config.json
- Cline Snapback get_request_status ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Snapback get_request_status ~/.gemini/settings.json
- Grok Snapback get_request_status .mcp.json (in your project root)
- ChatGPT Snapback get_request_status Settings → Connectors → Advanced → Developer mode
- Claude.ai Snapback get_request_status Settings → Connectors → Add custom connector
- LangChain Snapback get_request_status pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http snapback https://api.snapback.sh/mcpOther tools on this server
- diagnose_trace
- diagnose_batch
- get_verdict
- preflight
- submit_feedback
- my_usage
- my_impact
- what_others_did
- report_outcome
- recommend_failover
- cascade_root
- suggest_budget_recovery
- request_pattern
- detect_loop
- session_start
- session_step
- session_end
- agent_memory
- budget_guard
- convert_trace
- search_docs
- diagnose_infra_error
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.