FetchSandbox MCP MCP server

Which servers in the official MCP registry are FetchSandbox MCP's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-09

← Back to FetchSandbox MCP

Whose server it is

Registry nameio.github.fetchsandbox/mcppublished by fetchsandbox on GitHub

Published under the GitHub organisation fetchsandbox, the same one fetchsandbox.com links from its homepage. The registry ties that namespace to a GitHub sign-in.

When we asked itchecked 2026-10-09

Stateanswerschecked 2026-10-09
Tools7
Server calls itselffetchsandbox
Server version0.7.11
Protocol version2025-06-18

On 2026-10-09 the server answered initialize and tools/list without a sign-in. First answer in 77 ms.

Tools it offers7 tools · read 2026-10-09

coach
Conversational integration coach for FetchSandbox. Server-side orchestrator that walks the user through adding an API integration (payments / email / auth / etc.) — intake the goal, elicit domain-aware discovery questions from the spec's…
guide
ROUTE a symptom to the provider behaviour that explains it. Use this when the user names a provider or a domain (payments, email, auth, SMS, subscriptions) and you need to know what that provider ACTUALLY does — not what its docs say, and…
quickrun
Run a curated proof workflow against a KNOWN, bundled spec (stripe, clerk, descope, resend, twilio, and 50+ others) in ONE call — it spins up the sandbox by slug, so you do NOT need import_spec or a sandbox_id first. This is the normal…
validate_integration
Start with providers (and optional app_base_url), then reuse the returned session_id for application_context, fixtures and attempts. Do not include application_context in the initial session call. Inspect how the actual app or workflow…
list_workflows
List the named, runnable workflows for a known provider slug or imported spec. Workflows are realistic multi-step API journeys (e.g. 'create customer → attach payment method → create subscription'). Known provider slugs need no import…
run_workflow
Execute ONE specific workflow by name and return its step-by-step trace PLUS a `share_url` — a public, replayable proof URL that renders the full timeline (every request, response, webhook event) for this run. The share_url is the…
verify_behavior
Prove a known fix survives a bug — the 'prove' half of reproduce→prove. The backend spawns a buggy AND a fixed reference handler and fires the bug_pattern's probes at both, returning the side-by-side diff (e.g. the buggy handler…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

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

Also shipped through: npm

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.