# agpay (remote · agpay.shveik.dev)

Payments held between two agents: buyer pays, seller delivers, buyer confirms. Pay per call.

- Trust score: 79/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-17

## Components

- remote · `agpay.shveik.dev`: 79/100 (this document), [markdown](https://verifymcp.io/servers/dev-shveik-agpay/agpay.md), [page](https://verifymcp.io/servers/dev-shveik-agpay/agpay)

## Channel facts

- Endpoint: `https://agpay.shveik.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## 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-10-17.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 85/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).
  - Tool/resource definitions use about 926 tokens (~92/item across 10 items; 6 tools + 4 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 95/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 86% of tool parameters carry a description.
- **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 current MCP spec version (2026-07-28).

## Install

### How do I install the agpay MCP server?

agpay is a hosted endpoint at https://agpay.shveik.dev/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 dev-shveik-agpay 'https://agpay.shveik.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-shveik-agpay": {
      "url": "https://agpay.shveik.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-shveik-agpay": {
      "type": "http",
      "url": "https://agpay.shveik.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-shveik-agpay]
url = "https://agpay.shveik.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-shveik-agpay": {
      "type": "remote",
      "url": "https://agpay.shveik.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-shveik-agpay --url 'https://agpay.shveik.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-shveik-agpay:
    url: "https://agpay.shveik.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-shveik-agpay": {
      "Transport": "http",
      "Url": "https://agpay.shveik.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-shveik-agpay -t streamable-http -u 'https://agpay.shveik.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dev-shveik-agpay": {
      "type": "http",
      "url": "https://agpay.shveik.dev/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-10-16 (score 79, +1)

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

### 2026-10-14 (score 78, +1)

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

### 2026-10-12 (score 77, +1)

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

### 2026-10-10 (score 76)

First indexed and scored.

## MCP tools (6)

### `create_deal` (~233 tokens)

Open a deal

Open an escrow deal with a seller agent. Pay in stablecoins with x402 like the HTTP route: call without a payment to get the quote, then again with the signed payment in _meta. The answer is the receipt; act only on state funded. Choose the buyer secret yourself and send only its SHA-256 hash as secret_hash; keep the secret to confirm or dispute the deal.

Input parameters:

- `amount_usd` (string, required): what the seller receives on release, in dollars with at most 2 decimals
- `deadline_hours` (integer): hours from funding until the seller must deliver
- `instant` (boolean): the job is delivered at once and may be confirmed at once
- `network` (string, required)
- `ref` (string): a public reference; never put a secret in it
- `review_hours` (integer): hours you have to dispute after delivery
- `secret_hash` (string, required): SHA-256 hex of the secret you keep to confirm or dispute the deal
- `seller_address` (string, required): the seller's EVM address; it proves control of it with one signature later

### `get_deal` (~58 tokens)

Get a deal

Get the status of a deal: its state, amounts, deadlines and outcome. Free; needs only the deal id. Act only on state funded.

Input parameters:

- `deal_id` (string, required): the deal id, as returned when the deal was created

### `list_deals` (~98 tokens)

List deals

List the deals of an address, as seller or as buyer, newest first. Free; give exactly one of seller or buyer, an address. Everything except statements is visible to anyone who knows the address.

Input parameters:

- `before` (string): the next_before id of the previous page
- `buyer` (string): the buyer address (0x...)
- `limit` (integer)
- `seller` (string): the seller address (0x...)

### `confirm_deal` (~86 tokens)

Confirm a deal

Confirm a deal as its buyer: the seller is paid now and the deal closes. Free; needs the deal id and the buyer secret. Confirming is final.

Input parameters:

- `deal_id` (string, required): the deal id, as returned when the deal was created
- `secret` (string, required): the buyer secret the buyer chose when creating the deal (agp_ and 32 hex)

### `add_statement` (~108 tokens)

Add a statement

Add a statement to a deal as its buyer, up to 2000 characters. Free; needs the deal id, the buyer secret and the text. Statements are visible to the operator only.

Input parameters:

- `deal_id` (string, required): the deal id, as returned when the deal was created
- `secret` (string, required): the buyer secret the buyer chose when creating the deal (agp_ and 32 hex)
- `text` (string, required): the statement, 1 to 2000 characters

### `feedback` (~117 tokens)

Send feedback

Free. Tell the people who run this service what worked, what failed or what you miss: a bug, an idea or a thanks. A person reads it. No payment, no account; limited to a few messages an hour.

Input parameters:

- `contact` (string): optional: how we can reach you or your operator
- `kind` (string)
- `message` (string, required): what worked, what did not, what you miss; no secrets or private data
- `route` (string): the route the feedback is about, if any

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-shveik-agpay/agpay#diagnostics

## Score history

- 2026-10-17: 79
- 2026-10-16: 79
- 2026-10-15: 78
- 2026-10-14: 78
- 2026-10-13: 77
- 2026-10-12: 77
- 2026-10-11: 76
- 2026-10-10: 76

## Common questions

### What is the agpay MCP server?

agpay is an MCP server listed in the public MCP registry as dev.shveik/agpay. Payments held between two agents: buyer pays, seller delivers, buyer confirms. Pay per call. This page covers its hosted endpoint (https://agpay.shveik.dev/mcp).

### Is the agpay MCP server safe to use?

agpay scores 79 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 agpay MCP server expose?

agpay exposes 6 tools: create_deal, get_deal, list_deals, confirm_deal, add_statement, feedback. Their descriptions and schemas cost roughly 700 tokens of context every time the server is loaded.

### Does the agpay MCP server require authentication?

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

### Is the agpay MCP server still maintained?

agpay is still listed as active in the MCP registry. We last reached this channel on 17 October 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://agpay.shveik.dev/mcp
- Website: https://agpay.shveik.dev/
- Changelog RSS feed: https://verifymcp.io/servers/dev-shveik-agpay/agpay.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-shveik-agpay/agpay.json
- HTML version of this page: https://verifymcp.io/servers/dev-shveik-agpay/agpay