Stabledrop escrow payments
me.stabledrop/escrow-payments
Stablecoin escrow payments the buyer can dispute, with a signed receipt. Pay a wallet or an email.
Connect this server
One click to install, or copy the config below. Suits: Cursor · HTTP clients.
Or add it manually — claude_desktop_config.json (Claude Desktop) or .cursor/mcp.json (Cursor):
{
"mcpServers": {
"escrow-payments": {
"url": "https://api.stabledrop.me/api/ap2/mcp"
}
}
}claude mcp add --transport http escrow-payments https://api.stabledrop.me/api/ap2/mcpcode --add-mcp '{"name":"escrow-payments","type":"http","url":"https://api.stabledrop.me/api/ap2/mcp"}'Syntax from each client's docs (Claude Code: claude mcp add; Codex: codex mcp add; VS Code: code --add-mcp). Placeholders in angle brackets are values you fill in. Codex takes hosted servers in config.toml ([mcp_servers.<name>] url = …) rather than on the command line.
A starting point — check the repository for exact arguments and setup. Restart your client after editing the config.
- Category
- Finance
- Version
- 14.1.1
- Registry
- active
- Published
- 11/17/2026
Is it safe? Is it maintained?
Serverdex check: Nov 22, 2026Mostly fine: Stabledrop escrow payments is hosted endpoint answering without a key.
- Maintained
- No commit data
- The repository has not been read yet, so the last-commit date is unknown.
- Official registry
- Active
- Published as me.stabledrop/escrow-payments in the official MCP registry, version 14.1.1.
- Source
- No licence found
- Public repository, but GitHub reports no recognised licence. Check the README before shipping it in a product.
- Runs
- Hosted by the publisher
- Your client talks to api.stabledrop.me: prompts and tool arguments leave your machine for that host.
- Credentials
- None needed to connect
- The hosted endpoint completed the Serverdex initialize + tools/list handshake with no key (checked Nov 22, 2026); individual tools may still ask for one.
- Owner
- Unclaimed
- Nobody has claimed this page yet; the data above comes from the registry, GitHub and the live check.
Facts only: last commit and licence from GitHub, the entry's status from the official registry, credentials from the live check. Not a code audit — run the security scan on the endpoint yourself and see the status history.
Live check
checked Nov 22, 2026, 00:07 UTCStatus history & uptime →The endpoint answered the MCP handshake as "Protected payments with a dispute window" and listed 6 tools. Answering since Nov 18, 2026.
Context cost ≈ 4.3k tokens of tool definitions a client loads per conversation (estimate: characters ÷ 4) across 6 tools.
Tools (6)
read_published_page1 paramRead one of the published pages, for answering questions about how any of this works. Use it rather than guessing. What the fees are, how a dispute is decided and who decides it, what a buyer is agreeing to — all of it is written down, and none of it is safe to invent. how-it-works How an protected payment works, start to finish faq Common questions about protected payments, fees, disputes and timing arbitration-policy How a dispute is decided, by whom, and on what evidence terms-of-service The terms a buyer and seller are agreeing to privacy-policy What is collected and why plugins The WordPress and Shopify integrations home What the product is and who it is for
Show parametersHide parameters
pagestringrequiredWhich page: how-it-works, faq, arbitration-policy, terms-of-service, privacy-policy, plugins or home.
prepare_escrow_payment11 paramsWork out where a payment must go, before anybody signs or sends anything. `seller` and `nominal_buyer` may each be a wallet address OR AN EMAIL ADDRESS — an email is converted to the wallet that person owns, so you never need to know a wallet to use this. The parties are checked against the sanctions lists before an address is given. If any of them is listed the answer is `error: sanctioned_party` with no address, and the payment cannot be made through this service. The same answer comes back for terms whose payment contract was already refused on sanctions grounds when its money arrived: its address is not handed out again. If the check cannot be done right now the answer is `error: service_unavailable` with `retryable: true` and no address; try again shortly. Returns the payment address these terms produce, and TWO ways to fund it. Both end at the same address holding the same money; they differ only in who sends the transaction. **Transfer it yourself.** Send the tokens to the address from any wallet — a browser wallet, a hardware wallet, an exchange withdrawal. Nothing to sign for us, and no `payer` needed, because the payment contract never asks who paid: it reads its own balance. Then call `settle_escrow_payment` with no signature and we create the payment contract around what is there. **Or let us relay it.** Pass `payer` and this returns an EIP-3009 authorization for them to sign. We broadcast it and pay the gas, so **the payer needs no gas at all**. This is the only one an agent can complete unattended, and the only one that needs a key anywhere. Either way the address is the same, because it is a pure function of the terms. That is also what makes the relayed form safe: the payer signs `to` as part of the authorization, committing to every term at once — alter any of them afterwards and the address moves and the signature stops matching. `amount` is in the TOKEN's base units (1 USDC = 1000000), because that exact figure is one of the terms the addre
Show parametersHide parameters
sellerstringrequiredWho gets paid: a wallet address (0x…) OR an email address. An email is converted to the wallet that person owns, created for them if they have never signed in;amountintegerrequiredHow much, in the token's base units: 1 USDC = 1000000, so 25 USDC is 25000000. One of the terms the payment address derives from.expiry_timestampintegerrequiredWhen the dispute window closes, as an absolute Unix time in seconds, e.g. 1764547200. 0 settles instantly with no recourse. There is no default.nominal_buyerstringrequiredWho may dispute and receives any refund — the PERSON, not the agent: a wallet address (0x…) OR an email address. An email is converted to that person's wallet,external_idYour own id for this payment, e.g. a checkout hash, so re-presenting the same purchase derives the same address. Omit and a unique one is generated; pass back tpayerWallet address (0x…) that will sign an EIP-3009 authorization for us to relay, gas-free. Omit when the payer transfers the tokens to the address themselves.token_symbolstringThe token to pay in, e.g. USDC. Must be one the service supports.descriptionstringWhat the payment is for, in the buyer's own words, 1 to 160 characters, e.g. 'Logo design, final files'. Shown on the dashboard; does not affect the address.brandThe white-label partner the payment is made under, if any: the site's `?b=` id, e.g. escrow-me. Attribution only; does not affect the address.product_nameWhat is being bought, e.g. 'Blue ceramic vase'. Shown on both parties' dashboards; display only.arbiterWallet address (0x…) of who decides a dispute. Omit for the default arbiter. One of the terms the address derives from, so pass the same value to both tools.
settle_escrow_payment11 paramsCreate the payment contract around the money and return a signed receipt. `seller` and `nominal_buyer` may be wallet addresses OR EMAIL ADDRESSES, exactly as in `prepare_escrow_payment`; an email converts to the same wallet it did there. Works both ways, and which one runs is decided by whether you pass a signature: **Already transferred it yourself** — omit `authorization` and `signature`. We check the address holds the amount and build the payment contract around what is there. If the transfer has not arrived it says so, and nothing is spent finding out. **Want us to relay it** — pass the payer's `authorization` and `signature`. We broadcast it and pay the gas, so the payer needs none. This process holds no key and signs nothing; it is handed a signature and carries it. Pass the terms exactly as they were prepared. They ARE the payment contract's address, so a single altered figure moves it — and with a signature, stops matching what the payer signed. `seller` and `nominal_buyer` may be wallet addresses or email addresses, as in `prepare_escrow_payment`; an email resolves to the same wallet it did there. ⚠️ `external_id` MUST BE THE ONE `prepare_escrow_payment` RETURNED. It generates one when you leave it out, and that generated value is only knowable from its result — send a different one and this derives a different address, while the money is at the first. ⚠️ `error: sanctioned_party` IS FINAL. A party scored above 0 on the sanctions check when the money arrived (or the payment contract was refused before): the money is frozen at its address, and nothing more may be paid into it. Do not retry and do not offer to pay again. ⚠️ The receipt reports what the seller will actually RECEIVE in `token_amount`, with the platform fee named beside it. That is less than the amount authorised, and the two reconcile: token_amount + creator_fee = amount. `brand` is the white-label partner, as in `prepare_escrow_payment`: attribution only, and ignore
Show parametersHide parameters
sellerstringrequiredWho gets paid: a wallet address (0x…) OR an email address. An email is converted to the wallet that person owns, created for them if they have never signed in;amountintegerrequiredHow much, in the token's base units: 1 USDC = 1000000, so 25 USDC is 25000000. One of the terms the payment address derives from.expiry_timestampintegerrequiredWhen the dispute window closes, as an absolute Unix time in seconds, e.g. 1764547200. 0 settles instantly with no recourse. There is no default.external_idstringrequiredThe external_id prepare_escrow_payment returned, exactly. A different id derives a different address while the money sits at the first.nominal_buyerstringrequiredWho may dispute and receives any refund — the PERSON, not the agent: a wallet address (0x…) OR an email address. An email is converted to that person's wallet,authorizationThe EIP-3009 authorization object prepare_escrow_payment returned for the payer, unchanged. Omit when the payer transferred the tokens themselves.signatureThe payer's hex signature (0x…) over that authorization. Omit together with `authorization`.token_symbolstringThe token to pay in, e.g. USDC. Must be one the service supports.descriptionstringWhat the payment is for, in the buyer's own words, 1 to 160 characters, e.g. 'Logo design, final files'. Shown on the dashboard; does not affect the address.brandThe white-label partner the payment is made under, if any: the site's `?b=` id, e.g. escrow-me. Attribution only; does not affect the address.arbiterWallet address (0x…) of who decides a dispute. Omit for the default arbiter. One of the terms the address derives from, so pass the same value to both tools.
payment_qr1 paramA scannable code for a payment request, so nobody retypes an address. Pass the `payment_uri` from `prepare_escrow_payment`. Returns a QR a phone wallet can scan, with the token, network, destination and amount already in it. Or pass its `share_with_payer.pay_link`, for a code that opens the payment on the site instead — what to hand someone who is being asked to pay, as the site's own requests do. ⚠️ A SEPARATE TOOL RATHER THAN PART OF `prepare`, because the two have different audiences. `prepare` answers a machine and has to stay parseable; an image in its result would make the structured fields something a client has to dig for. A person who needs the code asks for it. ⚠️ AND IT ENCODES THE URI, NOT THE BARE ADDRESS. A QR holding only an address leaves the amount and the token to be entered by hand, which is the part worth removing — a payment contract funded with the wrong figure is not the payment contract these terms derive to, and the money sits at an address nothing can deploy to.
Show parametersHide parameters
payment_uristringrequiredThe `payment_uri` prepare_escrow_payment returned, for a code a wallet scans; or its `share_with_payer.pay_link`, for a code that opens the payment page.
check_escrow_payment1 paramWhat has happened to a settled payment, from the `status_url` on its receipt.
Show parametersHide parameters
status_urlstringrequiredThe `status_url` on the receipt settle_escrow_payment returned, as is.
verify_escrow_receipt1 paramCheck a receipt's signature against the key its issuer publishes. ⚠️ THE KEY IS FETCHED FROM THE RECEIPT'S OWN `iss`, NOT FROM WHOEVER HANDED IT OVER. Otherwise anything that can serve a receipt can also serve the key that vouches for it, and the signature stops meaning anything. Use this on receipts from anywhere, including ones this server did not produce.
Show parametersHide parameters
payment_receiptstringrequiredThe receipt as a compact JWS string (header.payload.signature), e.g. the `payment_receipt` settle_escrow_payment returned, or one from anywhere else.
Checked by Serverdex with a plain initialize + tools/list call to api.stabledrop.me/api/ap2/mcp, no credentials, about once a day. A failed check is never a removal.
Remotes
- streamable-http
https://api.stabledrop.me/api/ap2/mcp
Alternatives to Stabledrop escrow payments
All Stabledrop escrow payments alternatives →Best Finance servers →The most-starred Finance servers in the index, with their live-check result.
| Server | Stars | Last push | Live check |
|---|---|---|---|
| CCXT | 44,949 | Nov 2026 | Local / not checked |
| QR Rápido | 7,477 | Nov 2026 | Needs sign-in |
| Finance Toolkit | 5,554 | Nov 2026 | Needs sign-in |
| AKQuant | 2,627 | Nov 2026 | Local / not checked |
| com.stripe MCP | 2,072 | Nov 2026 | Needs sign-in |
Stabledrop escrow payments: questions people ask
- Is Stabledrop escrow payments a remote or a local MCP server?
- According to its entry in the official MCP registry, Stabledrop escrow payments ships as a hosted endpoint (streamable-http) that your client connects to by URL.
- Does Stabledrop escrow payments need an API key?
- Its hosted endpoint completed the Serverdex live check — an MCP initialize + tools/list call — with no credentials on Nov 22, 2026. Individual tools may still ask for a key when called.
- Is Stabledrop escrow payments safe to use?
- Mostly fine: Stabledrop escrow payments is hosted endpoint answering without a key. In detail — maintained: No commit data; official registry: Active; source: No licence found; runs: Hosted by the publisher; credentials: None needed to connect. Serverdex check of Nov 22, 2026. This is a reading of the repository, the registry entry and the live check, not a code audit; run the Serverdex security scan on the endpoint before trusting it with real data.
- What tools does Stabledrop escrow payments expose?
- 6 tools as listed by the server itself during the live check, including read_published_page, prepare_escrow_payment, settle_escrow_payment, payment_qr, check_escrow_payment. The full list with parameters is in the Live check section above.
- How do I add Stabledrop escrow payments to Claude, Cursor or VS Code?
- Copy the config in "Connect this server" into your client's MCP config file (claude_desktop_config.json, ~/.cursor/mcp.json or .vscode/mcp.json), or use the one-click Add to Cursor / Add to VS Code buttons and the one-line commands for Claude Code and Codex; then restart the client.
More Finance servers
Browse all Finance →arc
ashrithps
Your arc budget in any agent: 121 tools for accounts, transactions, debts and reports
BankBridge
bankbridge-money
Works in any MCP agent, including local models. Read-only bank accounts, spending, investments.
Candor Finance
candorsystems
Personal finance for your AI agent: money goals, a budget, and a review of your accounts.
Simple Balance
thtmnisamnstr
Free budget app and spending tracker: ask about your money, and queue or record transactions.
Stables
stables-money
Stablecoin payments for AI agents: customers, quotes, transfers, payment routes.
Timbrix — CFDI 4.0 para México
Timbrix
Official Timbrix MCP server: stamp, cancel, and query Mexican CFDI 4.0 invoices from AI agents.
Add the badge to your site
Show visitors that Stabledrop escrow payments is listed here — it’s also the link we check for a free listing.
HTML — for your website
<a href="https://serverdex.io/server/me-stabledrop-escrow-payments?utm_source=badge"><img src="https://serverdex.io/brand/badge.svg" alt="Stabledrop escrow payments — listed on Serverdex" width="123" height="40" loading="lazy"></a>Recommended. A dofollow link from your own domain is the one that counts for search engines, and it's the link we check for a free listing.
Markdown — for your README
[](https://serverdex.io/server/me-stabledrop-escrow-payments?utm_source=badge)Nice for visibility, but GitHub marks README links nofollow, so it doesn't pass authority. Use the HTML badge on your site as well.
Install buttons — for your README
[](https://serverdex.io/install/cursor/me-stabledrop-escrow-payments) [](https://serverdex.io/install/vscode/me-stabledrop-escrow-payments) [](https://serverdex.io/install/claude-code/me-stabledrop-escrow-payments)One click opens Cursor or VS Code with this server's config prefilled; the Claude Code button lands on the one-line command. The links point at Serverdex, so when your config changes the buttons keep working.
Install buttons — HTML for your docs
<a href="https://serverdex.io/install/cursor/me-stabledrop-escrow-payments"><img src="https://serverdex.io/brand/install-cursor.svg" alt="Add to Cursor — via Serverdex" width="140" height="28"></a>
<a href="https://serverdex.io/install/vscode/me-stabledrop-escrow-payments"><img src="https://serverdex.io/brand/install-vscode.svg" alt="Add to VS Code — via Serverdex" width="147" height="28"></a>
<a href="https://serverdex.io/install/claude-code/me-stabledrop-escrow-payments"><img src="https://serverdex.io/brand/install-claude-code.svg" alt="Open in Claude Code — via Serverdex" width="180" height="28"></a>Same buttons as plain links for a docs page or website.
Prefer a live badge with the score, stars and live check? Score badge (links to a page that explains the number and back to this listing).