iEscrow MCP server
Commit Nov 1, 2026Lets an AI agent manage cryptocurrency escrow trades, marketplace ads, and balance inquiries while requiring human 2FA for all money movements.
Also known as iEscrow/mcp-docs, mcp-docs
- Stars
- 0
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 0.3.1
- Last commit
- Nov 1, 2026
- License
- —
What is iEscrow MCP?
iEscrow lets an AI agent manage cryptocurrency escrow trades, marketplace ads, and balance inquiries while requiring human 2FA for all money movements.
Summary generated from the project's README
About iEscrow MCP server
iEscrow provides an MCP server that allows AI agents to manage cryptocurrency escrow operations on behalf of a user. This server connects to the iEscrow platform via streamable HTTP and uses OAuth 2.1 with PKCE for secure authentication. It is designed for users of Claude, ChatGPT, or other MCP hosts who want to automate marketplace activities while maintaining strict control over their funds.
The system operates on a principle where the agent prepares actions but the human must commit them. While an agent can use tools to get quotes, check balances, or prepare marketplace ads, it cannot move money independently. Any action involving funds requires the user to open a specific link and provide a two-factor authentication code. This architecture ensures the agent can never withdraw funds, change payment accounts, or deliver crypto to external wallets without explicit human approval.
To use this server, you need an iEscrow account that has completed email verification, identity verification (KYC), and enabled TOTP two-factor authentication. The server includes 25 tools and enforces rate limits, such as 60 calls per minute and 10 trade openings per hour.
What you can do with it
- 1Automate marketplace trade preparationAn AI agent can find suitable cryptocurrency offers and prepare the necessary details to open a trade.
- 2Manage private escrow requestsA developer can instruct an agent to initiate a private escrow or swap with a specific person using their reference number.
- 3Monitor trade status and balancesThe agent can check the current state of user trades and verify available wallet balances.
- 4Execute cryptocurrency swapsAn agent can facilitate a direct swap between two different cryptocurrencies when no bank transfer is required.
Written from the project's README. Every use case is checked against a quote from it.
How to install iEscrow MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall iEscrow MCP in Claude Code
$ claude mcp add --transport http mcp-docs https://api.iescrow.io/mcpInstall iEscrow MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"mcp-docs": {
"url": "https://api.iescrow.io/mcp"
}
}
}Install iEscrow MCP in VS Code
.vscode/mcp.json
{
"servers": {
"mcp-docs": {
"type": "http",
"url": "https://api.iescrow.io/mcp"
}
}
}Install iEscrow MCP in VS Code CLI
$ code --add-mcp '{"name":"mcp-docs","type":"http","url":"https://api.iescrow.io/mcp"}'Install iEscrow MCP in Codex
$ codex mcp add mcp-docs --url https://api.iescrow.io/mcpInstall iEscrow MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.mcp-docs] url = "https://api.iescrow.io/mcp"
Install iEscrow MCP in Gemini CLI
$ gemini mcp add -s user --transport http mcp-docs https://api.iescrow.io/mcpInstall iEscrow MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"mcp-docs": {
"url": "https://api.iescrow.io/mcp",
"type": "http"
}
}
}Automated checks
Ran Nov 15, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachableiescrow/mcp-docs is public and reachablegithub.com/iescrow/mcp-docs ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)No licenseFinding
- Commit or release in the last yearLast commit or release 2026-11-01github.com/iescrow/mcp-docs ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeHTTPS endpoint answered 401 (sign-in required)Pass
README
View on GitHubiEscrow MCP server
iEscrow is a cryptocurrency escrow platform: in every trade the crypto is held by iEscrow until both sides have delivered, so nobody has to hand over first. This repository documents the iEscrow MCP server, which lets an AI agent (Claude, ChatGPT or any MCP host) operate an iEscrow account on behalf of the user who authorized it.
- Endpoint:
https://api.iescrow.io/mcp - Transport: Streamable HTTP, stateless
- Auth: OAuth 2.1 (authorization server at
https://api.iescrow.io), PKCE, dynamic client registration - Tools: 25, listed in TOOLS.md
- Website: https://iescrow.io · For AI agents: https://iescrow.io/ai
The principle: the agent prepares, the human commits
The agent can quote, open trades, read balances and states, and prepare marketplace ads. Anything that moves money is not executed by the agent: the tool creates an approval and returns a link. The account owner opens that link, sees exactly what is about to happen, and approves it with their two-factor code.
What the agent can never do, by design:
- withdraw funds from the account,
- add or change payment accounts,
- upload a payment receipt (only the human can, through a dedicated link),
- lock crypto into escrow or confirm that a payment arrived without the human's approval,
- deliver crypto to an external wallet (everything lands in the user's iEscrow balance).
The API enforces this with an allow-list of routes for agent tokens; the MCP server only wraps those routes.
Requirements
An iEscrow account with:
- a verified email,
- approved identity verification (KYC),
- two-factor authentication (TOTP) enabled.
The connection screen (/connect) checks the three before issuing a token. Trades can be executed by an agent only in the countries where iEscrow is enabled for agents; get_readiness tells you which.
Connecting
Claude (claude.ai, desktop, mobile)
Settings → Connectors → Add custom connector → name iEscrow, URL https://api.iescrow.io/mcp. Claude discovers the authorization server, opens the iEscrow consent screen, and the connection is ready once you approve it.
Claude Code
claude mcp add --transport http iescrow https://api.iescrow.io/mcp
Then run /mcp inside Claude Code to complete the login.
ChatGPT
Settings → Connectors → Create (developer mode) → name iEscrow, MCP server URL https://api.iescrow.io/mcp, authentication OAuth. ChatGPT registers itself as a client and sends you to the iEscrow consent screen.
Any other MCP host
Point the host to the URL above with the Streamable HTTP transport. The server publishes /.well-known/oauth-protected-resource, and the authorization server publishes /.well-known/oauth-authorization-server; hosts that implement the MCP authorization spec need nothing else. See examples/ for configuration snippets.
Scopes
| Scope | Grants |
|---|---|
profile:read |
who the user is and whether the account is ready to trade |
quotes:read |
executable offers and prices on the marketplace |
wallet:read |
balances and masked payment accounts |
trades:read |
state of the user's trades and ads |
trades:write |
open trades, request approvals to lock crypto or confirm payments, cancel own requests |
ads:write |
prepare marketplace ads (always subject to the human's approval) |
Scopes are chosen on the consent screen and can be revoked at any time from Connected apps in the user's iEscrow settings.
Rate limits
Per connection: 60 calls per minute, 10 openings per hour (taking a marketplace offer, requesting a private escrow or buying from the catalog), 20 money-moving approval requests per hour. One concurrent long-poll (wait_for_trade_update) per user. A limited call returns error_key and retry_after_s.
A typical flow (buying crypto with a bank transfer)
get_readiness— confirm the account can trade.get_quotewithside=buy, the crypto, the fiat and the amount — pick an offer; notecompatible_account_ids.open_tradewith the offer id, the amount and a compatiblepayment_account_id.get_trade— wait untilcrypto_fundedis true. The human must not pay before that.get_proof_upload_link— give the user the link; it shows the exact amount (the cents are the payment key) and the account to pay. The user pays, attaches the receipt and declares the payment there.wait_for_trade_update— the trade moves toreleasedwhen the seller confirms. The crypto is now in the user's iEscrow balance.
Selling is the mirror image: open_trade with side=sell, then fund_escrow (the human approves the lock by link), then confirm_received once the fiat arrives (again approved by link).
Swapping one crypto for another is shorter, because no bank is involved and nobody has to confirm a transfer: get_swap_quote, then open_trade with the offer's open_trade_args, then fund_escrow. Both legs are verified on chain and the escrow settles by itself once each side has funded.
To deal with one specific person instead of the market, use open_private_request (a product or a service, paid milestone by milestone if you want) or open_private_swap. Both need that person's reference number, which they share with you from their own account, so ask the user for it rather than guessing: that requirement is what keeps an agent from firing requests at a list of usernames.
Errors
Every error is returned as structured content with error: true, an HTTP-like status, a stable error_key and a human-readable message. When an action needs the human, the response carries approval_required: true and approval.approve_url; poll check_approval with approval.public_id to learn the outcome.
Security
The MCP server never opens the database and holds no secrets of its own: it verifies the user's access token (RS256, issuer and audience pinned) and forwards the same bearer to the API. Reports about the agent channel: contact@iescrow.io.
About this repository
This repository holds the public documentation of the server and the manifest used to list it in MCP registries. The server's source code is not published here.
iEscrow MCP questions
How do I add iEscrow MCP to Claude Code?
Run claude mcp add --transport http mcp-docs https://api.iescrow.io/mcp in your terminal. Add --scope user to make it available in every project.
How do I add iEscrow MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
Can the AI agent withdraw money from my account?
No, the agent is restricted from withdrawing funds, changing payment accounts, or delivering crypto to external wallets.
What are the requirements to use an iEscrow account with an agent?
You need an account with a verified email, approved identity verification (KYC), and two-factor authentication (TOTP) enabled.