Mmcp.market

FetchSandbox MCP server

by fetchsandbox·io.github.fetchsandbox/mcp·v0.5.6
No reviews yet

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

B82/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B82/100

full report

Adoption
Growing

1 stars959 downloads/wk

Reviews

Write one

Nobody has reviewed FetchSandbox yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

FetchSandbox tools (14, 4 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • coach

    Conversational integration coach for FetchSandbox. Server-side

  • find_bugs

    FIRST STEP for any API-integration bug — webhooks, payments, auth, email,

  • fix_bug

    FetchSandbox remediation: get a proposed fix for a specific bug in YOUR

  • guide

    ROUTE a symptom to the provider behaviour that explains it. Use this when

  • import_spec

    Ingest an OpenAPI spec and get a working sandbox you can call immediately.

  • list_runs

    List recent workflow runs (and ad-hoc traffic) for a sandbox, newest

  • list_specs

    Browse the FetchSandbox spec catalog — every API (Stripe, GitHub,

  • list_workflows

    List the named, runnable workflows for a previously-imported spec.

  • prove_fix

    THE PROOF STEP. The only way to establish that a fix actually works, and

  • quickrunwrite action

    Run a curated proof workflow against a KNOWN, bundled spec (stripe, clerk,

  • run_all_workflowswrite action

    Execute EVERY workflow (or a scoped subset) for a sandbox in ONE call.

  • run_workflowwrite action

    Execute ONE specific workflow by name and return its step-by-step trace

  • submit_proofwrite action

    Receipts are readable by anyone with the link — do not attach bodies the

  • verify_behavior

    Prove a known fix survives a bug — the 'prove' half of reproduce→prove.

Public scan report

scanner v0.1.5 · 2026-09-19 · same rubric, same numbers if you re-run it

no findings
  • Code scan49 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 1 days ago15/15
  • Maintainer identityregistry namespace matches repository owner7/10
Overall 82/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

Grade history

  • 2026-09-19downgradeA → Bscore 82

Install directly

Runs npx -y fetchsandbox-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add mcp -- npx -y fetchsandbox-mcp
Add to Cursor

FetchSandbox: common questions

Is FetchSandbox MCP server safe?
Mostly: it is graded B (82/100). Read the FetchSandbox safety report
How do I install FetchSandbox?
It runs on your machine. Copy the Claude Code, Claude Desktop or Cursor config from the install section.
Does FetchSandbox need an API key?
Yes. The registry entry asks for FETCHSANDBOX_API_KEY.
Is FetchSandbox maintained?
The last commit was 3 days ago (2026-09-18). The latest release is v0.5.6.

More from fetchsandbox →