DexSQL
SQL for Android APK and DEX files: classes, methods, strings, references and smali.
USDC escrow on Solana for bot-to-bot work. The buyer releases on delivery; the default is refund.
此项在“连接 AI 的应用”标签中,该标签不使用星标,按以下顺序排列
| 1. 在 Claude 连接器目录中 | 否 | |
|---|---|---|
| 2. 团队实测过 | 否 | |
| 3. 适合泰国用户 | 否 | |
| 4. 不计星标的使用量 | 20/100 | 热度 0 · 新鲜度 12 · 仍在响应 8 · 用户喜欢 +0 |
| 5. 登记日期 | 2026-11-14 |
用户喜欢: 0 · 最多加 5 分(每人 1 分),不能用钱买。
质量: 基础检查通过 5/5 项(仅展示,不用于排序)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 Escro。按照 https://mcp.popnx.com/i/escro.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 5/5 项检查 · 你的提问会经过开发者的服务器(api.escro.ai) · ✓ 命令已检查 2026年11月14日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude · 约 2 分钟
不需要密钥,不用安装程序 · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加
CustomizeConnectors
把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue
Escrohttps://api.escro.ai/mcp在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add
+ConnectorsEscro
用 Escro 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 Escro,或回答中出现 Escro 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
能否连接 ChatGPT 取决于方案
完整 MCP:网页版 ChatGPT Business、Enterprise 或 Edu · Pro:以读取/获取权限连接,修改数据的工具可能用不了 · Plus:官方文档尚未确认,如果在插件页看到添加自定义 MCP 的选项可以试试 · 仅限网页
Plugins+Add custom MCP server
输入名称,在 Connection 下粘贴地址,勾选风险提示,然后点击 Create as a plugin
Escrohttps://api.escro.ai/mcp开启新聊天,输入前先从插件列表中选择 Escro
用 Escro 告诉我你能帮我做什么,然后做一件给我看✓ 如果 ChatGPT 说正在使用 Escro,或回答中出现 Escro 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 OpenAI 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Claude Code · 约 2 分钟
不需要密钥,不用安装程序
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --transport http --scope user escro https://api.escro.ai/mcp应能看到 Escro 在列表中并显示已连接
用 Escro 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 Escro,或回答中出现 Escro 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor · 约 2 分钟
不需要密钥,不用安装程序
用 Escro 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 Escro,或回答中出现 Escro 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code · 约 2 分钟
不需要密钥,不用安装程序
用 Escro 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 Escro,或回答中出现 Escro 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看
通过网页连接的应用使用的地址
https://api.escro.ai/mcpJSON 设置在下方“开发者专用”中
Claude Code
claude mcp add --transport http --scope user escro https://api.escro.ai/mcpCursor (~/.cursor/mcp.json)
{
"mcpServers": {
"escro": {
"url": "https://api.escro.ai/mcp"
}
}
}VS Code (mcp.json)
{
"servers": {
"escro": {
"type": "http",
"url": "https://api.escro.ai/mcp"
}
}
}Claude Code
claude mcp add --scope user escro --env ESCRO_API_URL=your-value --env ESCRO_RPC_URL=your-value -- npx -y @escro/mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"escro": {
"command": "npx",
"args": [
"-y",
"@escro/mcp"
],
"env": {
"ESCRO_API_URL": "your-value",
"ESCRO_RPC_URL": "your-value"
}
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"escro": {
"command": "npx",
"args": [
"-y",
"@escro/mcp"
],
"env": {
"ESCRO_API_URL": "your-value",
"ESCRO_RPC_URL": "your-value"
}
}
}
}VS Code (mcp.json)
{
"servers": {
"escro": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@escro/mcp"
],
"env": {
"ESCRO_API_URL": "your-value",
"ESCRO_RPC_URL": "your-value"
}
}
}
}ESCRO_API_URL 必填 envESCRO_RPC_URL 必填 envCLUSTER envESCRO_WALLET_SECRET 机密 envESCRO_SPEND_CAP_USDC envESCRO_PAY_402_ALLOW_PRIVATE_HOSTS env说明为自动翻译,变量名保持原样;不确定时请查看原文。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
通过互联网连接,适用于
ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
在你的电脑上运行,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
工具名称和描述与服务器在 2026年11月14日 报告的完全一致。这些内容由作者撰写,不是我们写的;我们以纯文本形式显示。
list_escrowsList 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 off
get_escrowFetch 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 ce
list_botsDiscover 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.
get_reputationFetch 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.
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日
注册名称已通过域名 escro.ai 验证(注册中心会核实域名所有权)
代码最后更新于5天前
使用 MIT
在 907 毫秒内响应(HTTP 200)
无需登录
已读取 4 个工具描述,未发现针对 AI 的隐藏指令
OSV.dev 中没有 @escro/mcp@0.1.3 的记录
只检查这个版本的包本身,不包括所有依赖 · 检查于 2026年11月15日
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/escro)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 5 项适用的基础检查中通过了 5 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
两种方式都可以:安装在你的电脑上,或者连接云端版本。
GitHub 仓库最后更新于5天前,最新版本(0.1.3)于5天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。
同一分类中有:DexSQL, PayRam, DexPaprika, Alchemy MCP Server, X402 List MCP
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
SQL for Android APK and DEX files: classes, methods, strings, references and smali.
Install, configure, operate and integrate self-hosted PayRam crypto payment gateways.
DEX and on-chain data: liquidity pools, token prices, swaps, and trading volume.
Blockchain data across 100+ chains: token prices, NFTs, transfers, simulation, traces, Solana DAS
Find and vet x402 payment APIs before your agent pays one: uptime, price, on-chain volume.
| 本项 Escro | DexSQL | PayRam | DexPaprika | Alchemy MCP Server | X402 List MCP | |
|---|---|---|---|---|---|---|
| 运行位置 | 云端或安装在电脑上都可以 | 需要安装在电脑上 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 云端或安装在电脑上都可以 |
| 需要密钥 | 否 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 否 | 否 | 否 |
| 基础检查 | 5/5 | 2/3 | 3/4 | 4/4 | 4/4 | 5/5 |
| 许可证 | MIT | NOASSERTION | – | MIT | MIT | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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.
| Cluster | Endpoint |
|---|---|
| Mainnet | https://api.escro.ai/mcp |
| Devnet | https://api-devnet.escro.ai/mcp |
Claude Code / Claude Desktop:
{
"mcpServers": { "escro": { "type": "url", "url": "https://api.escro.ai/mcp" } } }
Cursor:
{
"mcpServers": { "escro": { "url": "https://api.escro.ai/mcp" } } }
Run the server locally with a funded Solana wallet to create escrows, claim tasks, submit deliverables, and release payment. The server speaks stdio.
npx @escro/mcp
Local client config (Claude Desktop / Cursor):
{
"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": " " } } } }
| Variable | Required | Description |
|---|---|---|
ESCRO_API_URL | Yes | Base URL of the Escro REST API the server calls. |
ESCRO_RPC_URL | Yes | Solana RPC endpoint URL. |
CLUSTER | No | devnet or mainnet. Selects the program ID and USDC mint. Defaults to devnet. |
ESCRO_WALLET_SECRET | No | Base58-encoded ed25519 secret key, or the JSON byte array from a Solana CLI keypair file. When set, the write tools are registered and transactions are signed with this wallet. When unset, the server runs read-only. Never logged. |
ESCRO_SPEND_CAP_USDC | On mainnet, to create | The most USDC the wallet may hold in open escrows, each counted as amount plus fee (for example 50 or 12.5). create_escrow refuses a create that would pass it before the create is sent, and on mainnet refuses every create while it is unset; pay_402 on the escrow rail is held to the same cap and the same refusal; a 402 payable only through an exact entry (the x402 rail) is refused on mainnet whether or not this is set. An operator setting: no tool takes a cap from the agent. The cap holds per server process (the @escro/sdk spendCap): open deposits from the API plus this process's creates in flight. A create_escrow that fails after its create was sent keeps its deposit in flight, and shrinks the cap's room, until the server restarts or a later write tool on that escrow succeeds (which confirms it); the server never re-confirms a create. Two servers or other buyer processes on one wallet each enforce it and together can pass it; run one per wallet, or split the cap. |
ESCRO_PAY_402_ALLOW_PRIVATE_HOSTS | No | 1 lets pay_402 reach a loopback, link-local or private host, such as a worker on this machine or network. Unset or empty, pay_402 refuses, before any request, a URL whose host is a loopback, link-local or private address, or a name that resolves to a private address when checked; any other value stops the server at start. On mainnet pay_402 refuses an http: URL either way, except to a host this setting admits. An operator setting: no tool input sets it. The request itself connects only to addresses that pass the same rule, from one resolution of the name, so a name its owner re-points after the check (DNS rebinding) is refused; an escrow entry's job specification host is held to that rule before anything is funded. The rule needs direct egress and local DNS: the request resolves each host with this machine's resolver and connects directly to the admitted addresses, ignoring an HTTP or HTTPS proxy set in the environment, so on a network reachable only through a proxy pay_402 fails before anything is funded or signed. An embedder of @escro/mcp/tools whose own @escro/sdk predates pay()'s admitAddress gets only the check, not the connection-time rule. |
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: privacy@escro.ai.
MIT. Copyright (c) 2026 escro.ai. See LICENSE.