# Stabledrop escrow payments (remote · api.stabledrop.me)

Stablecoin escrow payments the buyer can dispute, with a signed receipt. Pay a wallet or an email.

- Trust score: 64/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `api.stabledrop.me`: 64/100 (this document), [markdown](https://verifymcp.io/servers/me-stabledrop-escrow-payments/api-ap2-mcp.md), [page](https://verifymcp.io/servers/me-stabledrop-escrow-payments/api-ap2-mcp)

## Channel facts

- Endpoint: `https://api.stabledrop.me/api/ap2/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `2.0.3`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 76/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2363 tokens (~181/item across 13 items; 6 tools + 7 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 77/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 19% of tool parameters carry a description.
  - Structured output schemas are declared (83% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Stabledrop escrow payments MCP server?

Stabledrop escrow payments is a hosted endpoint at https://api.stabledrop.me/api/ap2/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http me-stabledrop-escrow-payments 'https://api.stabledrop.me/api/ap2/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "me-stabledrop-escrow-payments": {
      "url": "https://api.stabledrop.me/api/ap2/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "me-stabledrop-escrow-payments": {
      "type": "http",
      "url": "https://api.stabledrop.me/api/ap2/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.me-stabledrop-escrow-payments]
url = "https://api.stabledrop.me/api/ap2/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "me-stabledrop-escrow-payments": {
      "type": "remote",
      "url": "https://api.stabledrop.me/api/ap2/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add me-stabledrop-escrow-payments --url 'https://api.stabledrop.me/api/ap2/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  me-stabledrop-escrow-payments:
    url: "https://api.stabledrop.me/api/ap2/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "me-stabledrop-escrow-payments": {
      "Transport": "http",
      "Url": "https://api.stabledrop.me/api/ap2/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add me-stabledrop-escrow-payments -t streamable-http -u 'https://api.stabledrop.me/api/ap2/mcp'
```

### Other

```json
{
  "mcpServers": {
    "me-stabledrop-escrow-payments": {
      "type": "http",
      "url": "https://api.stabledrop.me/api/ap2/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-19 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-18 (score 63, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “prepare_escrow_payment” rewrote its description, which is the text the model reads
- [security] Tool “settle_escrow_payment” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 135 → 181
- [functional improvement] Tool coverage: 0% → 19%
- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: unknown → 2.0.3
- [functional] Server version: 4.0.4 → unknown
- [cosmetic] “prepare_escrow_payment” reworded the description of “nominal_buyer”
- [cosmetic] “prepare_escrow_payment” reworded the description of “seller”
- [cosmetic] “settle_escrow_payment” reworded the description of “nominal_buyer”
- [cosmetic] “settle_escrow_payment” reworded the description of “seller”

### 2026-09-17 (score 63)

First indexed and scored.

## MCP tools (6)

### `read_published_page` (~174 tokens)

Read Published Page

Read 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 escrow payment works, start to finish
    faq                  Common questions about escrow, 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

Input parameters:

- `page` (string, required)

Output parameters:

- `result` (string)

### `prepare_escrow_payment` (~1022 tokens)

Prepare Escrow Payment

Work 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.

Returns the escrow 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 escrow never asks who paid: it reads its own balance. Then call
\`settle_escrow_payment` with no signature and we create the escrow 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 address derives from.

\`expiry_timestamp` is an absolute Unix time — when the dispute window closes. `0` settles
instantly with no recourse. There is no default: "instant, deliberately" and "nobody said"
are different, and a caller must not discover afterwards which one they got.

\`nominal_buyer` is who may dispute and receives a refund. For an agentic payment this should
be the PERSON, not the agent — they are the one who will later read a report and decide
whether to object.

\**`seller` and `nominal_buyer` may each be a wallet address…

Input parameters:

- `amount` (integer, required)
- `description` (string)
- `expiry_timestamp` (integer, required)
- `external_id`
- `nominal_buyer` (string, required): Who 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, created for them if they have never sig…
- `payer`
- `seller` (string, required): Who 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; the same email always gives the same wa…
- `token_symbol` (string)

### `settle_escrow_payment` (~532 tokens)

Settle Escrow Payment

Create the escrow 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 escrow 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 escrow'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.

⚠️ 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.

Input parameters:

- `amount` (integer, required)
- `authorization`
- `description` (string)
- `expiry_timestamp` (integer, required)
- `external_id` (string, required)
- `nominal_buyer` (string, required): Who 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, created for them if they have never sig…
- `seller` (string, required): Who 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; the same email always gives the same wa…
- `signature`
- `token_symbol` (string)

### `payment_qr` (~214 tokens)

Payment Qr

A 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.

⚠️ 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 — an escrow
   funded with the wrong figure is not the escrow these terms derive to, and the money sits
   at an address nothing can deploy to.

Input parameters:

- `payment_uri` (string, required)

### `check_escrow_payment` (~37 tokens)

Check Escrow Payment

What has happened to a settled payment, from the `status_url` on its receipt.

Input parameters:

- `status_url` (string, required)

### `verify_escrow_receipt` (~102 tokens)

Verify Escrow Receipt

Check 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.

Input parameters:

- `payment_receipt` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/me-stabledrop-escrow-payments/api-ap2-mcp#diagnostics

## Score history

- 2026-09-20: 64
- 2026-09-19: 64
- 2026-09-18: 63
- 2026-09-17: 63

## Common questions

### What is the Stabledrop escrow payments MCP server?

Stabledrop escrow payments is an MCP server listed in the public MCP registry as me.stabledrop/escrow-payments. Stablecoin escrow payments the buyer can dispute, with a signed receipt. Pay a wallet or an email. This page covers its hosted endpoint (https://api.stabledrop.me/api/ap2/mcp).

### Is the Stabledrop escrow payments MCP server safe to use?

Stabledrop escrow payments scores 64 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Stabledrop escrow payments MCP server expose?

Stabledrop escrow payments exposes 6 tools: read_published_page, prepare_escrow_payment, settle_escrow_payment, payment_qr, check_escrow_payment, verify_escrow_receipt. Their descriptions and schemas cost roughly 2,081 tokens of context every time the server is loaded.

### Does the Stabledrop escrow payments MCP server require authentication?

No. We connected to Stabledrop escrow payments without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Stabledrop escrow payments MCP server still maintained?

Stabledrop escrow payments is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://api.stabledrop.me/api/ap2/mcp
- Repository: https://github.com/conduit-ucpi/ap2service
- Website: https://stabledrop.me/
- Changelog RSS feed: https://verifymcp.io/servers/me-stabledrop-escrow-payments/api-ap2-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/me-stabledrop-escrow-payments/api-ap2-mcp.json
- HTML version of this page: https://verifymcp.io/servers/me-stabledrop-escrow-payments/api-ap2-mcp