Snapback
Diagnose why an AI agent failed and get the verified fix instantly. Free, no token
Reviews
No review yet. Used Snapback? Be the first to help others choose.What it does
Snapback is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.
No capability identified yet from its description.
Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.
At a glance
How to connect
As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 2d ago (live check)Hosted endpoint
https://api.snapback.sh/mcpstreamable-http
In Claude Code: claude mcp add --transport http snapback https://api.snapback.sh/mcp
MCP settings (Claude Desktop, Cursor and other MCP clients)
{
"mcpServers": {
"snapback": {
"url": "https://api.snapback.sh/mcp"
}
}
}Live check
Electra Index connected to the hosted endpoint 2d agoONLINE Snapback answered an MCP connection on 14 Nov 2026 and introduced itself as snapback 1.0 (MCP protocol 2025-06-18).
23 tools offered to AI assistants
diagnose_trace· Diagnose why an AI agent run failed. Returns a structured verdict (failure_class, failed_at_step, root_cause, fix_suggestion, confidence). LATENCY: known patterns return library-instant (<1s); a NOVEL failure needs an LLM call and can takediagnose_batch· Diagnose SEVERAL traces in one call (up to 20). Each trace is metered like a separate diagnose_trace. Returns a verdicts array (per-trace, order preserved); a bad trace in the batch is isolated and doesn't fail the rest. Use for post-run anget_verdict· Fetch a previously produced verdict by its id or by trace_id (your org only).preflight· BEFORE running: get known failure patterns for a given agent setup so you can avoid them. Returns a ranked list of {failure_class, root_cause, fix_suggestion} from Snapback's library. Call this before executing a plan and self-correct.submit_feedback· Tell Snapback whether a verdict was correct (correct=true/false), with an optional free-text note (did the fix work? what was wrong?). ONE rating per verdict — call it AFTER you act on a verdict and see the outcome. Your correction updatesget_request_status· Check what happened to a pattern you requested (from request_pattern's request_id). Returns pending / approved / rejected / in_library so you can see if your suggestion was actioned — the feedback loop isn't a black box. Free, no token.my_usage· See YOUR current usage + remaining allowance so you can self-govern spend: snapbacks (diagnoses) used/cap/remaining, guard checks used/cap/remaining, estimated spend, % used, and when it resets. Call it periodically to avoid surprises. Tokemy_impact· See how your feedback + pattern requests have shaped the shared library — how many verdicts you've rated, patterns you've requested, and how many were approved into the library. Turns your input into visible collaboration. Token-scoped to ywhat_others_did· THE CROWD: for a failure_class (or pass the family/error and we'll map it), see what OTHER agents did about the same failure and whether it worked — anonymized, aggregated across everyone. Returns {total, agree_pct (community success rate),report_outcome· Report the outcome of an auto-applied fix (the self-heal interceptor calls this after it gate-applied a fix and retried). Pass failure_class, family, fix, confidence, action_class, and succeeded (did the retry work?). TWO purposes: it's yourecommend_failover· Should you RETRY the same target, SWITCH provider, FALL BACK to another chain, or STOP? Pass the error + your configured topology (current_chain, available_chains, and/or current_provider, available_providers) and get deterministic routingcascade_root· Given an ORDERED list of errors from a run (oldest first), find the TRUE root — the error that cascaded or shouldn't have been retried — not just the final symptom you see. E.g. a 429 that got retried and triggered a downstream 401: the roo
Show 11 more
suggest_budget_recovery· Approaching a token/context/cost budget mid-run? Pass your counters and get the LEAST-DISRUPTIVE recovery ranked: truncate context | switch to a cheaper model | batch steps | wrap up — scored by speed gained, accuracy lost, cost saved. Turnrequest_pattern· Leave us a message: ask us to add a failure pattern to the library, or report a problem we couldn't diagnose well. Use this when diagnose_trace didn't have a good answer, when you keep hitting a failure we don't classify, or when you want adetect_loop· MID-RUN loop check (fast, no LLM, free). Send your recent steps DURING a run; get back whether you're stuck repeating a tool call and a concrete next move. Call this every few steps to catch a loop BEFORE you burn your step budget — don't wsession_start· Open a LIVE mid-run session so Snapback can watch your run step-by-step and warn you in real time (loop / token / cost / context) - the always-on guardian mode. Returns a session_id. Free, no token. Call session_step as you run, session_endsession_step· Report ONE step of a live run and get back any warnings immediately (loop detected / budget breach). Pass the step (action + inputs) and any counters you have (step, max_steps, tokens_used, token_budget, cost_used_usd, cost_budget_usd, contsession_end· Close a live session and get a short run summary (total steps, duration). Frees the session. Free, no token.agent_memory· See what YOU (this agent) tend to fail on — your recurring failure patterns across past diagnoses. Returns your top failure classes with counts and what share of your failures each is (e.g. 'loop_repeated_tool_call: 12 times, 40%'). Call itbudget_guard· Live MID-RUN budget check (fast, no LLM). Send whatever counters you have and get an advisory on context %, token burn, cost burn, step budget, and off-task drift - with concrete suggested_actions and the projected cost of NOT acting. Callconvert_trace· Turn your raw logs into a Snapback trace so you don't hand-craft JSON. Pass 'source' = a list of log/step entries, or an object with a spans/steps/messages/events/logs array (OTel spans, OpenAI/LangChain message lists, or generic {tool,inpusearch_docs· Search Snapback's documentation for how to use it — how to format a trace, what each tool does, the failure taxonomy, auth, pricing, and errors. Free and needs no token. Call this first if you're unsure how to format a request or what a verdiagnose_infra_error· Diagnose a cryptic AGENT-INFRASTRUCTURE error — payments (x402/EIP-3009), Solana on-chain (ATA, blockhash, compute), MCP protocol, RPC/providers, EVM & Solana wallets, library of VERIFIED fixes the base model often gets wrong. Pass the erro
What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method
Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.
Facts & evidence
Each fact shows where it was seen and when.| Fact | Value | Evidence | Source | Last confirmed |
|---|---|---|---|---|
| Hosted endpoint | https://api.snapback.sh/mcp | DECLARED | SRC-001 Official MCP Registry | 4h ago |
| Version | 1.8.4 | DECLARED | SRC-001 Official MCP Registry | 4h ago |
| Local install (package) | no | DECLARED | SRC-001 Official MCP Registry | 4h ago |
| Remote access (hosted) | yes | DECLARED | SRC-001 Official MCP Registry | 4h ago |
| Repository | https://github.com/ra1labsworkx-wq/snapback-selfheal | DECLARED | SRC-001 Official MCP Registry | 4h ago |
| Registry status | active | DECLARED | SRC-001 Official MCP Registry | 4h ago |
| MCP server | yes | DECLARED | SRC-001 Official MCP Registry | 4h ago |
Change history
- VERSION02 Oct 20261.8.3 → 1.8.4
- VERSION01 Oct 20261.8.2 → 1.8.3
Is this page accurate?
Flag it and our robot re-checks the official source. Reports never change a score.Is Snapback still online?
Free alerts · no account▲ 0Do you run Snapback? Know when it stops answering
For publishers · optionalIts hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.
Monitoring never changes a score or a rank.
Questions about Snapback
How do I connect Snapback?
Use the hosted endpoint https://api.snapback.sh/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.
What tools does Snapback offer?
When Electra Index connected on 14 Nov 2026, it listed 23 tools: diagnose_trace, diagnose_batch, get_verdict, preflight, submit_feedback, get_request_status, my_usage, my_impact and more. The full list is in "Live check" above.
Is Snapback online?
Yes. Its hosted endpoint answered an MCP connection from Electra Index 2d ago.