Bots St

bots.st/fetchsandbox

FetchSandbox

Deterministic verification for agent fixes

2403 ms

answered our call

State
Answered
Protocol
MCP 2025-06-18
Tools listed
8
Answered
3 of the last 3 calls

How to reach it

  • MCP, HTTPhttps://fetchsandbox.com/mcp/v1
  • npmnpx -y fetchsandbox-mcpReleased 19 Oct 2026, version 0.7.30

What it can do

ToolWhat it says it does
coachConversational 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 brain.yaml, route to the right workflow, prove the contract…
get_jobRetrieve the SAME running find_bugs, fix_bug, prove_fix, verify_behavior or validate_integration job (including requirements planning). Follow next_tool_call until status is done or error. Never restart the original tool to poll. A proposed plan is not execution proof; a running response is not…
guideROUTE 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 not what can be inferred from reading the integration code…
list_workflowsList 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. Use this for exploration ("what can I do?", "show me the…
quickrunRun 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 slug, so you do NOT need import_spec or a sandbox_id first. Use this when exploring the bundled provider contract: call `guide` on their…
run_workflowExecute 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 canonical 'here's what happened' artifact: surface it verbatim in…
validate_integrationCompletion rule: a request to verify an app includes its applicable failure checks without another user prompt. When verification_continuation.required is true, continue in this agent: inspect pending_checks, preserve every declared check and its assertions, implement supported actions, and rerun…
verify_behaviorProve 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 double-charges on a duplicate webhook, the fixed handler dedupes)…

In its maker's words

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

Website
fetchsandbox.com
Source
github.com/fetchsandbox/mcp
Publisher
fetchsandbox
Listed from
the official MCP Registry as io.github.fetchsandbox/mcp
Version
0.7.30, updated 19 Oct 2026
Kinds of work
AI models and agent tools, Security and trust, Code and developer tools

The domain it lives on

fetchsandbox.com
registered 11 Mar 2026 (8 months ago), at Squarespace Domains LLC, its home page is a working site

From our own crawl of domain names: registry records and the home page as our crawler last saw it.

Every call we made

WhenWhat happenedTime
Answered2403 ms
Answered2413 ms
Answered1076 ms

Next door

Is this your bot? Claim its address to add a verified badge and keep the listing current.