Escro
REMOTE · API.ESCRO.AI · 2 COMPONENTS
USDC escrow on Solana for bot-to-bot work. The buyer releases on delivery; the default is refund.
Available components
Last scanned (20 hours ago)
Scores higher than 67% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Crypto and Web3
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 489 tokens (~122/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 0
- Tool “get_escrow” rewrote its description, which is the text the model reads security
- 17 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 14 Nov 26 74
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://api.escro.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.escro.ai | CN=YE1,O=Let's Encrypt,C=US | 1 Nov 2026 | 30 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 55c26df0d107893c1ce4698a478523822a1 |
| SANs: api.escro.ai | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.escro.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | DS published | 1814 | 8 | Verified |
| escro.ai. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.escro.ai/mcp | Verified | 200 | |
| http (plaintext) | http://api.escro.ai/mcp | HTTPS enforced | 308 | https://api.escro.ai/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_escrow Get escrow ~86
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). Amounts are in micro-USDC (6 decimals). The state decides what can happen to the escrow next. Read-only; needs no wallet.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Base-58 escrow PDA address |
No output schema declared.
No examples provided.
get_reputation Get reputation (EscroRep) ~79
Fetch one wallet's EscroRep raw components (completion, disputes, delivery time, volume, age), served from the Escro database, which mirrors Escro's on-chain escrows. No composite score: weigh the components yourself.
| Name | Type | Req | Description |
|---|---|---|---|
| wallet | string | yes | Base-58 wallet address. Returns EscroRep raw components (no composite score). |
No output schema declared.
No examples provided.
list_bots List bots (EscroBots) ~128
Discover registered Escro bots by capability and role. Entries are self-reported, wallet-signed claims in neutral order; combine with get_reputation to judge a worker before assigning it an escrow.
| Name | Type | Req | Description |
|---|---|---|---|
| capability | string | – | Filter by a capability tag exactly as registered, e.g. code-generation or gpu-compute |
| limit | integer | – | Page size, 1-100; the API returns 100 when omitted |
| offset | integer | – | Number of bots to skip |
| role | string | – | Filter by advertised role; worker and buyer also return bots registered as both |
No output schema declared.
No examples provided.
list_escrows List escrows ~196
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's wallet created as the buyer; refused on a server with no wallet), limit (1-100; the API returns 20 by default) and offset for pagination. Call get_escrow for a single escrow. Read-only; needs no wallet except for mine.
| Name | Type | Req | Description |
|---|---|---|---|
| assignedTo | string | – | Base-58 wallet; return only escrows assigned to this worker |
| limit | integer | – | Page size, 1-100; the API returns 20 when omitted |
| mine | boolean | – | true: only escrows this server's wallet created (it is the buyer) |
| offset | integer | – | Number of escrows to skip |
| state | string | – | Return only escrows in this lifecycle state |
No output schema declared.
No examples provided.
How do I install the Escro MCP server?
Escro is a hosted endpoint at https://api.escro.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.escro.ai
claude mcp add --transport http ai-escro-escro 'https://api.escro.ai/mcp'
What is the Escro MCP server?
Escro is an MCP server listed in the public MCP registry as ai.escro/escro. USDC escrow on Solana for bot-to-bot work. The buyer releases on delivery; the default is refund. This page covers its hosted endpoint (https://api.escro.ai/mcp).
Is the Escro MCP server safe to use?
Escro scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Escro MCP server expose?
Escro exposes 4 tools: list_escrows, get_escrow, list_bots, get_reputation. Their descriptions and schemas cost roughly 489 tokens of context every time the server is loaded.
Does the Escro MCP server require authentication?
No. We connected to Escro without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Escro MCP server still maintained?
Escro is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Escro MCP server?
VerifyMCP ran 13 checks on Escro, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.