Is the Ra1labsworkx Wq Snapback MCP server down?

mcp-registry/io.github.ra1labsworkx-wq/snapback · v1.0

healthy
Last checked 2026-10-18 18:50 UTC · handshake 835ms

As of 2026-10-18 18:50 UTC, the Ra1labsworkx Wq Snapback MCP server is up with a Glimind reliability score of 92/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 7 minutes.

uptime (30d checks)
100%
checks observed
3,484
outages (90d)
1
tools
23

Diagnose why an AI agent failed and get the verified fix instantly. Free, no token.

Install Ra1labsworkx Wq Snapback MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http ra1labsworkx-wq-snapback-mcp-server https://api.snapback.sh/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "ra1labsworkx-wq-snapback-mcp-server": {
      "type": "http",
      "url": "https://api.snapback.sh/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: A (90/100)

A (90/100): 0 error(s), 3 warning(s) across 23 tool(s); ~4,192 tokens of tool definitions.
Scores higher than 71% of 15,317 MCP servers Glimind has audited.
Its tool list costs an agent ~4,192 tokens per session — more than 55% of servers.
90 → 90 since 2026-10-17
no tool-poisoning patterns
Schemas88
Descriptions69
Safety hints100
Token cost100
Client compatibility100
Protocol100
Reliability85
Stability96

What to fix (4)

25 parameter(s) across 7 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: budget_guard, get_request_status, get_verdict, report_outcome, session_end and 2 more

1 tool(s) have parameters with no type (no type/enum/anyOf/$ref).

Give every parameter a "type" (or "enum"/"anyOf"). Untyped parameters make models guess — strings for numbers, objects for arrays. How to fix →

Tools: convert_trace

Handshake + tools/list takes ~2,085 ms.

Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.

In the last 30 days: 0 tool(s) removed and 1 schema change(s).

Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →

Auto-fix: 1 corrected tool definition

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 7 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.ra1labsworkx-wq%2Fsnapback/fixes

convert_trace 1 change 
{
  "name": "convert_trace",
  "description": "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,input,output} arrays all work). Returns {trace} ready to pass straight to diagnose_trace. Free, no token.",
  "inputSchema": {
    "type": "object",
    "required": [
      "source"
    ],
    "properties": {
      "hint": {
        "type": "string",
        "description": "optional: the framework/format, e.g. 'otel', 'openai'"
      },
      "source": {
        "description": "your logs: a list, or an object wrapping a spans/steps/messages array",
        "type": "string"
      }
    }
  },
  "annotations": {
    "title": "Convert Trace",
    "readOnlyHint": true,
    "openWorldHint": false,
    "idempotentHint": true,
    "destructiveHint": false
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.ra1labsworkx-wq/snapback"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.ra1labsworkx-wq/snapback"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown 
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.ra1labsworkx-wq%2Fsnapback.svg)](https://glimind.com/server/mcp-registry%2Fio.github.ra1labsworkx-wq%2Fsnapback?ref=badge)
HTML 
<a href="https://glimind.com/server/mcp-registry%2Fio.github.ra1labsworkx-wq%2Fsnapback?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.ra1labsworkx-wq%2Fsnapback.svg" alt="MCP agent-readiness"></a>
reStructuredText 
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.ra1labsworkx-wq%2Fsnapback.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.ra1labsworkx-wq%2Fsnapback?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:d882ac60c62dfaa8…, first seen 2026-10-17, included at leaf 13792 of 23,105. Version history · verify what your client received.

Tools (23)

Compare: most reliable analytics servers · most reliable finance servers · most reliable other servers · most reliable data servers · most reliable devops servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Ra1labsworkx Wq Snapback MCP server down right now?

As of 2026-10-18 18:50 UTC, the Ra1labsworkx Wq Snapback MCP server is up with a Glimind reliability score of 92/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 7 minutes.

How many tools does Ra1labsworkx Wq Snapback MCP server provide?

Ra1labsworkx Wq Snapback MCP server advertises 23 tools, including agent_memory, budget_guard, cascade_root, convert_trace, detect_loop.

How do I install Ra1labsworkx Wq Snapback MCP server?

Point your MCP client at this streamable-http endpoint: https://api.snapback.sh/mcp

Is the Ra1labsworkx Wq Snapback MCP server safe to connect to an AI agent?

Glimind scanned all 23 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Ra1labsworkx Wq Snapback MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.