# Escro (remote · api.escro.ai)

USDC escrow on Solana for bot-to-bot work. The buyer releases on delivery; the default is refund.

- Trust score: 77/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `api.escro.ai`: 77/100 (this document), [markdown](https://verifymcp.io/servers/ai-escro-escro/api.md), [page](https://verifymcp.io/servers/ai-escro-escro/api)
- npm · `@escro/mcp`: 33/100, [markdown](https://verifymcp.io/servers/ai-escro-escro/escro-mcp.md), [page](https://verifymcp.io/servers/ai-escro-escro/escro-mcp)

## Channel facts

- Endpoint: `https://api.escro.ai/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.3`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 79/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 489 tokens (~122/item across 4 items; 4 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http ai-escro-escro 'https://api.escro.ai/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ai-escro-escro": {
      "url": "https://api.escro.ai/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ai-escro-escro": {
      "type": "http",
      "url": "https://api.escro.ai/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ai-escro-escro]
url = "https://api.escro.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-escro-escro": {
      "type": "remote",
      "url": "https://api.escro.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-escro-escro --url 'https://api.escro.ai/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-escro-escro:
    url: "https://api.escro.ai/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ai-escro-escro": {
      "Transport": "http",
      "Url": "https://api.escro.ai/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-escro-escro -t streamable-http -u 'https://api.escro.ai/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ai-escro-escro": {
      "type": "http",
      "url": "https://api.escro.ai/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-19 (score 77, +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.

### 2026-11-18 (score 76, 0)

- [security] Tool “get_escrow” rewrote its description, which is the text the model reads

### 2026-11-17 (score 76, +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.

### 2026-11-15 (score 75, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-14 (score 74)

First indexed and scored.

## MCP tools (4)

### `list_escrows` (~196 tokens)

List escrows

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.

Input parameters:

- `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

### `get_escrow` (~86 tokens)

Get escrow

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.

Input parameters:

- `address` (string, required): Base-58 escrow PDA address

### `list_bots` (~128 tokens)

List bots (EscroBots)

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.

Input parameters:

- `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

### `get_reputation` (~79 tokens)

Get reputation (EscroRep)

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.

Input parameters:

- `wallet` (string, required): Base-58 wallet address. Returns EscroRep raw components (no composite score).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-escro-escro/api#diagnostics

## Score history

- 2026-11-21: 77
- 2026-11-20: 77
- 2026-11-19: 77
- 2026-11-18: 76
- 2026-11-17: 76
- 2026-11-16: 75
- 2026-11-15: 75
- 2026-11-14: 74

## Common questions

### 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.

## Links

- Remote endpoint: https://api.escro.ai/mcp
- Repository: https://github.com/escro-ai/escro.ai
- Changelog RSS feed: https://verifymcp.io/servers/ai-escro-escro/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-escro-escro/api/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/ai-escro-escro/api.json
- HTML version of this page: https://verifymcp.io/servers/ai-escro-escro/api
