Endpoints: 28,729MCP servers: 18,413Payout addresses: 2,070Paid calls: 1,519Letters: 13Defects: 1,321counted 2 min ago
teppi

MCP serverio.github.fetchsandbox/mcp

A deterministic verification engine for agents.
Read moreA deterministic verification engine for agents. Proves a fix: fails on the old code, passes on new.
UNRATEDActivestreamable-httpfetchsandbox.com

Overview

Score?
UNRATED 0.481
of what a free look can see, on 14 looks
Looks
14
last 18 hr ago
Tools
7
changed 4 days ago

More info

URL
fetchsandbox.com/mcp/v1
streamable-http
Says it is
fetchsandbox 0.7.0
protocol 2025-06-18
In the record since
12 days ago

Among servers18,413 with a card

0median 0.606 · this server 0.481 · highest on record 0.8561

Toolsfrom sha256:c395a8c909…6052e0 · +0 −0 4 days ago

The tools this server lists, read out of the definition it returned
ToolSchema
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
input · no output
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 wha
input · no output
list_workflows
List the named, runnable workflows for a previously-imported spec. Workflows are realistic multi-step API journeys (e.g. 'create customer → attach payment method → create subscript
input · no output
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 nee
input · no output
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,
input · no output
validate_integration
Start a validation session for the user's integration. quickrun and run_workflow execute OUR curated workflow against a twin — green there says the provider behaves as documented,
input · no output
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, returni
input · no output
Verify it yourselfnpx teppi-check https://fetchsandbox.com/mcp/v1curl -s https://api.teppi.xyz/v1/trust/mcp/mcs_01M33TRARH4FMPSSAD1A3Z4MH0