FetchSandbox

Name: FetchSandbox
Author: fetchsandbox

MCP serverMCP

A deterministic verification engine for agents. Proves a fix: fails on the old code, passes on new.

by fetchsandboxrepository ↗homepage ↗v0.7.29MIT

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"fetchsandbox-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability112/112 checks ok

when	check	result	http	latency	detail
2 h ago	mcp initialize	ok	200	710 ms	server fetchsandbox 0.7.30 · protocol 2025-06-18 · 8 tools
9 h ago	mcp initialize	ok	200	690 ms	server fetchsandbox 0.7.30 · protocol 2025-06-18 · 8 tools
16 h ago	mcp initialize	ok	200	645 ms	server fetchsandbox 0.7.30 · protocol 2025-06-18 · 8 tools
23 h ago	mcp initialize	ok	200	666 ms	server fetchsandbox 0.7.30 · protocol 2025-06-18 · 8 tools
29 h ago	mcp initialize	ok	200	728 ms	server fetchsandbox 0.7.30 · protocol 2025-06-18 · 8 tools
2 d ago	mcp initialize	ok	200	811 ms	server fetchsandbox 0.7.30 · protocol 2025-06-18 · 8 tools
2 d ago	mcp initialize	ok	200	195 ms	server fetchsandbox 0.7.30 · protocol 2025-06-18 · 8 tools
2 d ago	mcp initialize	ok	200	803 ms	server fetchsandbox 0.7.30 · protocol 2025-06-18 · 8 tools
3 d ago	mcp initialize	ok	200	754 ms	server fetchsandbox 0.7.30 · protocol 2025-06-18 · 8 tools
3 d ago	mcp initialize	ok	200	187 ms	server fetchsandbox 0.7.30 · protocol 2025-06-18 · 8 tools

Tools observed via MCP handshake

coach — Conversational integration coach for FetchSandbox. Server-side orchestrator that walks the user through adding an API integration (payments / email / auth / etc
get_job — Retrieve the SAME running find_bugs, fix_bug, prove_fix, verify_behavior or validate_integration job (including requirements planning). Follow next_tool_call un
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
quickrun — Run a curated reference workflow against a KNOWN, bundled spec (stripe, clerk, descope, resend, twilio, and 50+ others) in ONE call — it spins up the sandbox by
validate_integration — Completion rule: a request to verify an app includes its applicable failure checks without another user prompt. When verification_continuation.required is true,
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 p
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 (ever
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 pro

Declared by sources

What the publisher says

Attributed to the source that supplied each field. Treated as claims, not facts.

No long description beyond the summary.

mcpmodel-context-protocolverificationagent-verificationintegration-testingwebhook-testingidempotencyapi-sandboxstripepaddleclaudecursoropenapi

kind Official MCP Registry

name Official MCP Registry

license npm registry

repoUrl Official MCP Registry

summary Official MCP Registry

version Official MCP Registry

description Official MCP Registry

homepageUrl Official MCP Registry

publisherName Official MCP Registry

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

npm registryfetchsandbox-mcp

first seen 2 mo ago · fetched 3 h agoopen ↗

Official MCP Registryio.github.fetchsandbox/mcp

first seen 2 mo ago · fetched 3 d agoopen ↗

Field history (12 recent events)

3 d ago · observed · packageFacts → {"name":"fetchsandbox-mcp","registry":"npm","publishedAt":"2026-10-19T14:33:10.328Z","latestVersion":"0.7.30","weeklyDow
3 d ago · declared · version → "0.7.29"
4 d ago · observed · packageFacts → {"name":"fetchsandbox-mcp","registry":"npm","publishedAt":"2026-10-18T15:14:57.160Z","latestVersion":"0.7.29","weeklyDow
10 d ago · declared · version → "0.7.28"
10 d ago · observed · packageFacts → {"name":"fetchsandbox-mcp","registry":"npm","publishedAt":"2026-10-12T19:35:02.640Z","latestVersion":"0.7.28","weeklyDow
11 d ago · observed · packageFacts → {"name":"fetchsandbox-mcp","registry":"npm","publishedAt":"2026-10-12T03:15:08.718Z","latestVersion":"0.7.24","weeklyDow
11 d ago · observed · packageFacts → {"name":"fetchsandbox-mcp","registry":"npm","publishedAt":"2026-10-11T07:35:58.330Z","latestVersion":"0.7.19","weeklyDow
12 d ago · observed · packageFacts → {"name":"fetchsandbox-mcp","registry":"npm","publishedAt":"2026-10-11T04:14:46.031Z","latestVersion":"0.7.15","weeklyDow
15 d ago · declared · version → "0.7.2"
16 d ago · observed · packageFacts → {"name":"fetchsandbox-mcp","registry":"npm","publishedAt":"2026-10-06T18:21:11.108Z","latestVersion":"0.7.11","weeklyDow
17 d ago · observed · packageFacts → {"name":"fetchsandbox-mcp","registry":"npm","publishedAt":"2026-10-06T08:11:55.742Z","latestVersion":"0.7.5","weeklyDown
18 d ago · observed · packageFacts → {"name":"fetchsandbox-mcp","registry":"npm","publishedAt":"2026-10-04T18:09:20.567Z","latestVersion":"0.7.2","weeklyDown

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from