Spec Driven Development
by formulahendry
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Runs on your computer★ 440MITUpdated 14 months ago
Install
iEscrow
Overview
Description from the maker (original English)
Buy products and services with escrow, or trade crypto P2P. Money moves only with human 2FA.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi3 of 3 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs in the cloud
- Transport: Streamable HTTP
- Category: Other
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 3 of 3 passed
- Runs on the maker’s server: what you ask it goes through their server.
- The registry lists no key to fill in.
You need
- Runs in the cloudNothing to install; it connects over the internet
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
- Open Settings → Connectors
- Press Add custom connector
- Paste the address below and press Add
- If it asks you to sign in, sign in with the maker
https://api.iescrow.io/mcpRun this in your terminal
claude mcp add --transport http iescrow https://api.iescrow.io/mcpOr copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"iescrow": {
"url": "https://api.iescrow.io/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"iescrow": {
"type": "http",
"url": "https://api.iescrow.io/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
- Open ChatGPT on the web → Settings → Connectors (Apps)
- Press Create or Add (some plans need Developer mode under Advanced first)
- Paste the address below, give it a name and save
- If it asks you to sign in, sign in with the maker
https://api.iescrow.io/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
The server asks you to sign in before it lists its tools.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account iEscrow, which owns the repo
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- ✓ Pass
Endpoint responds
Responded in 416 ms (HTTP 401)
- ✓ Pass
Sign-in with OAuth
Declares OAuth sign-in, so your AI app can take you to log in
- … Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint
Compared with others in Otheri
- More stars than 0% of the other 32583 servers in this category
- Published to the registry more recently than 86% of the other 32583 servers in this category
- Basic checks equal to or better than 100% of the other 32583 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is iEscrow safe?
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
Is it still maintained?
The GitHub repo last changed –, and the latest version (0.3.1) reached the registry 5 days ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
What can I use instead?
In the same category: Spec Driven Development, Remote Desktop Commander, sync. labs
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Remote Desktop Commander
by desktop-commander
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Runs in the cloud★ 211Updated yesterday
Install
sync. labs
by synchronicity-labs
Lipsync videos, dub them into other languages, make talking videos and open sync. Studio.
Computer or cloudUpdated today
Install
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
iEscrow 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/mcpThen 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.