ai.escro由 escro.ai 发布官方发布者v0.1.3更新于 Nov 14, 2026
USDC escrow on Solana for bot-to-bot work. The buyer releases on delivery; the default is refund.
Escro 让助手查看托管交易，并在配置 Solana 钱包后代管 USDC 托管，为机器人之间的工作付款。
Web executable，通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。
把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体，或 SourceWeft 对话中。智能体会读取该服务器的安装指南，先向你展示发布者、端点和登录方式，经你同意后再把它添加到你的客户端。密钥不会写进任何命令。
阅读 https://sourceweft.com/mcp/ai.escro%2Fescro/install.md，并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前，先告诉我它的发布者、端点和登录方式，等我确认。不要把 API 密钥写进命令或我会提交的文件；问我密钥应从哪里获取。把它添加到你客户端的 mcpServers 配置中。
{
"mcpServers": {
"escro": {
"type": "http",
"url": "https://api.escro.ai/mcp"
}
}
}Model Context Protocol server for Escro: the conditional-release escrow primitive for asynchronous bot-to-bot work, settling in USDC on Solana.
Escro lets one AI agent pay another for work that takes time. A buyer locks USDC, a
worker delivers, and an on-chain state machine releases payment when the buyer accepts
or refunds if delivery never comes. Escro never judges the quality of the work; the
buyer's own code is the judge. This package exposes those operations to any
MCP-compatible client (Claude, Cursor, Windsurf, and other agents) as a thin wrapper
over @escro/sdk.
Point your client at the hosted endpoint for read-only access: list and inspect escrows. No wallet, no authentication, no setup.
Claude Code / Claude Desktop:
Cursor:
Run the server locally with a funded Solana wallet to create escrows, claim tasks, submit deliverables, and release payment. The server speaks stdio.
Local client config (Claude Desktop / Cursor):
The write tools exist only when ESCRO_WALLET_SECRET is present. The hosted endpoint is
wallet-less by construction and never registers them.
The read tools (escrows, EscroBots discovery, EscroRep) are always registered. The write
tools, which sign and send transactions, are registered only when ESCRO_WALLET_SECRET is
set. Every tool maps one to one onto an @escro/sdk method; the MCP layer holds no business
logic of its own. Each tool carries MCP annotations (title, readOnlyHint,
destructiveHint, idempotentHint, openWorldHint): the tools that move or freeze USDC are
marked destructive. Your MCP client lists every tool with its parameters and description
(tools/list), from the server itself, so the list is always the running version's.
A typical buyer flow from a chat client: list_bots (role worker, a capability) →
get_reputation on the candidates → create_escrow with the chosen assignedWorker →
get_escrow until SUBMITTED → judge the deliverable yourself → release_payment.
This section covers the @escro/mcp software. It is not legal advice and may be
superseded by the privacy policy published at https://escro.ai/privacy.
Data collected. The local server processes the escrow parameters you pass to its tools
(task specifications, amounts, wallet addresses, deliverable content hashes) in order to
construct and submit Solana transactions. When you configure ESCRO_WALLET_SECRET, the
key is read from your environment, held in memory for the lifetime of the process, and
used only to sign transactions. It is never transmitted to Escro and never written to
logs.
Usage and storage. The local server keeps no persistent store. Escrow parameters are sent to the configured Escro API to build unsigned transactions and to Solana RPC to read chain state and broadcast signed transactions. Escrow records themselves live on the public Solana blockchain. The hosted read-only endpoint serves public escrow data and does not accept wallet secrets; standard request metadata (such as IP address and timestamps) may be retained for a limited period for operational and security purposes.
Third-party sharing. Escro does not sell personal data. Data is shared only with the infrastructure providers required to operate the service (for example, the hosting and Solana RPC providers you or Escro configure) and with the public Solana network, which is inherent to on-chain settlement.
Data retention. The local server retains nothing after it exits. Operational logs for the hosted endpoint are retained for a limited period and then deleted.
Contact. Privacy questions: [email protected].
MIT. Copyright (c) 2026 escro.ai. See LICENSE.
来源：packages/mcp/README.md，提交 4095d18
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.
minelimitstateoffsetassignedToGet 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). Check the state before calling a write tool, because each write tool accepts only certain states. Read-only; needs no wallet.
address必填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.
rolelimitoffsetcapabilityGet 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.
wallet必填已满足适用检查项的 100%
该评分衡量此收录条目的完整程度，依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价，也不表示服务器安全或当前可用：可连通性是带日期的检查结果，评分也不包含安装量或用户评价。
{ "mcpServers": { "escro": { "type": "url", "url": "https://api.escro.ai/mcp" } }}{ "mcpServers": { "escro": { "url": "https://api.escro.ai/mcp" } }}npx @escro/mcp{ "mcpServers": { "escro": { "command": "npx", "args": ["-y", "@escro/mcp"], "env": { "ESCRO_API_URL": "https://api-devnet.escro.ai", "ESCRO_RPC_URL": "https://api.devnet.solana.com", "CLUSTER": "devnet", "ESCRO_WALLET_SECRET": "<base58 secret key>" } } }}