Deep MCP Trust Report
We run your MCP server and call every tool.
A badge says “trust me.” A receipt says “here is what happened when we actually executed it.” Independent, sandboxed verification of your MCP server — protocol, schemas, live tool calls, error handling — published as evidence anyone can check.
What we check
Five lenses. Zero opinions.
Startup & registration
Installed, built, and started in an isolated sandbox. Registered tools compared against what your README claims.
Protocol compliance
Real MCP handshake: protocol version, identity, capabilities, a clean stdio channel, graceful shutdown.
Tool schemas
Every tool inspected for a description and a well-formed, typed input schema — the contract agents depend on.
Tool execution
Every tool actually CALLED with inputs generated from its own schema. Crashes, hangs, and malformed results have nowhere to hide.
Error handling
Every tool probed with invalid input. A production server errors gracefully and stays up — a fragile one dies.
Honest by construction
Tools that need real credentials are labeled structurally verified — never faked as functional. Sandbox problems never count against your server.
The output
Receipts, not a score
Real lines from real runs. Every claim pins to evidence — what was called, what came back, what broke.
- Tool `list_prs` responds to a schema-valid call without crashing — Responded to the call; server stayed up.
- Tool `get_pr` returns a successful result — Executed but returned "Bad credentials" — needs real credentials (structurally verified only).
- Tool `boom` responds to a schema-valid call without crashing — Server process died when this tool was called.
- Tool `loose` rejects invalid input gracefully — Accepted a call missing required parameters — schema contract not enforced.
Founding offer
$49 · pay on acceptance
- Full receipt report — every lens, every tool, published at a permanent URL (or kept private, your call)
- A README badge linking to the live report
- One free re-run after you fix anything the report surfaces
- You see the report first. Pay only if you accept it — if it isn’t useful, you owe nothing.
Currently Node.js MCP servers in public GitHub repos. Verification runs in an isolated e2b sandbox; we never publish a report on your repo without your request.
Don't have an MCP server yet?
We build custom MCP servers — fixed price, verified against your spec, IP transfers to you, pay on acceptance.