Copied. Paste it into Claude Code, Cursor or Codex:Fetch and follow the instructions at https://qamcp.dev/setup.md to test my MCP server.
Your AI finds your server in your project, tests it with QAmcp, explains what's wrong in plain words, fixes it with your OK, and tests again. Read the instructions
On their server. What you send to it goes to them.
What you need
Nothing: it answered without a login
Tools
4 tools
Its own safety labels
4 read-only
Memory it takes
About 890 tokens of your AI's memory, just for its tool descriptions
Largest answer
About 15.2 KB in our test
Speed
Average answer in our test: 882 ms
Tokens are an estimate: the characters in its tool names, descriptions and inputs, divided by 4. The exact number depends on your AI model. Safety labels are what the server says about itself. From the daily test on 14 Nov 2026.
Is Escro MCP server safe?
None of the hidden-instruction wordings we know were found in its 4 tool descriptions.
Its error messages showed no secrets or internal details.
All 4 of its tools are labeled read-only.
Overall it scored 93/100 on 14 Nov 2026.
A test can only see what the server shows from outside, not what it does with your data behind the scenes. Connect servers from makers you trust.
What this test does not check
Its source code and packages.
What a tool quietly does behind the scenes, such as writing a file or calling another service.
Instructions hidden inside live tool answers. We only look for those in tool descriptions.
Hidden instructions worded in a way our list doesn't know yet.
Tools that could change something. Those are read, never run.
None found in GitHub Security Advisories and OSV.dev on 14 Nov 2026.
That means none were published there, not that there are no problems. QAmcp tests how a server behaves. It does not scan source code.
What it can do
4 tools, in the server's own words.
list_escrowsread-only
List escrows on escro.ai with optional filters: state (one of the 8 lifecycle states), assignedTo (base-58 worker wallet), mine (true: only escrows this server…
get_escrowread-only
Fetch one escrow by its base-58 PDA address, including its state as mirrored by the Escro API (it can briefly lag the chain; the program is authoritative).
list_botsread-only
Discover registered Escro bots by capability and role.
get_reputationread-only
Fetch one wallet's EscroRep raw components (completion, disputes, delivery time, volume, age), served from the Escro database, which mirrors Escro's on-chain e…
!Uses an older MCP version (2025-11-25). It works today, but it isn't on the July 2026 version (2026-07-28) yet.
note
!
Fast enough1 warning
!list_escrows: Slowest tool: list_escrows (3.0 s): users will notice the wait
and 3 more
note
!
Follows MCP best practices (not scored yet)1 tip (not scored)
!2 tools answer with structured data but don't declare its shape (outputSchema): list_escrows, list_bots. If those answers change shape, nothing can catch it; with a schema, every answer is checked.
note
✓
ConnectsConnected in 973 ms
pass
✓
Lists its toolsFound 4 tools
pass
✓
Every tool is describedAll 4 tools and their inputs are described
pass
✓
Tools are labeled safe or dangerousEvery tool has a safety label
pass
✓
No known hidden instructionsNone of the hidden-instruction wordings we know were found in tool descriptions. New wordings can get past this check.
pass
✓
Tools work with good inputsAll good
✓list_escrows: Worked (3.0 s)
✓get_escrow: Answered with an error, probably because of our sample input: MCP error -32602: Input validation error: Invalid arguments for tool get_escrow: must be a base-58 public key at address
✓list_bots: Worked (231 ms)
✓get_reputation: Answered with an error, probably because of our sample input: MCP error -32602: Input validation error: Invalid arguments for tool get_reputation: must be a base-58 public key at wallet
pass
✓
Bad inputs give a clean errorAll good
✓list_escrows: Refused wrong type for "state" with a clear error
✓get_escrow: Refused missing required input "address" with a clear error
✓get_escrow: Refused wrong type for "address" with a clear error
✓list_bots: Refused wrong type for "capability" with a clear error
✓get_reputation: Refused missing required input "wallet" with a clear error
✓get_reputation: Refused wrong type for "wallet" with a clear error
pass
✓
No secrets leakedChecked 8 error messages: no secrets or internal details
pass
✓
No known hidden instructions in tool answers (not scored yet)Read 10 answers from 4 tools: none of the hidden-instruction wordings we know were found. New wordings can get past this check.
pass
–
Tools work togetherNo tool's answer could be fed into another tool, so there were no chains to test (not counted either way)
not tested
Show this score on GitHub
Free for every server in the directory. Paste this into your README: the badge always shows the newest score, from the daily test, a test on our website or a Monitor test.