# Agent Payment Guard (remote · agent-payment-guard.agent-data-apis.workers.dev)

Check wallets and tokens before an agent pays or trades: sanctions, honeypots, taxes, reputation.

- Trust score: 66/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `agent-payment-guard.agent-data-apis.workers.dev`: 66/100 (this document), [markdown](https://verifymcp.io/servers/dagu3371-agent-payment-guard/agent-payment-guard.md), [page](https://verifymcp.io/servers/dagu3371-agent-payment-guard/agent-payment-guard)

## Channel facts

- Endpoint: `https://agent-payment-guard.agent-data-apis.workers.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-11-21.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - 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**: 66/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 491 tokens (~163/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 90/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 71% 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 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 Agent Payment Guard MCP server?

Agent Payment Guard is a hosted endpoint at https://agent-payment-guard.agent-data-apis.workers.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 dagu3371-agent-payment-guard 'https://agent-payment-guard.agent-data-apis.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dagu3371-agent-payment-guard": {
      "url": "https://agent-payment-guard.agent-data-apis.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dagu3371-agent-payment-guard": {
      "type": "http",
      "url": "https://agent-payment-guard.agent-data-apis.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dagu3371-agent-payment-guard]
url = "https://agent-payment-guard.agent-data-apis.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dagu3371-agent-payment-guard": {
      "type": "remote",
      "url": "https://agent-payment-guard.agent-data-apis.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dagu3371-agent-payment-guard --url 'https://agent-payment-guard.agent-data-apis.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dagu3371-agent-payment-guard:
    url: "https://agent-payment-guard.agent-data-apis.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dagu3371-agent-payment-guard": {
      "Transport": "http",
      "Url": "https://agent-payment-guard.agent-data-apis.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dagu3371-agent-payment-guard -t streamable-http -u 'https://agent-payment-guard.agent-data-apis.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dagu3371-agent-payment-guard": {
      "type": "http",
      "url": "https://agent-payment-guard.agent-data-apis.workers.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-11-20 (score 66, +1)

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

### 2026-11-19 (score 65, −1)

- [security] Tool “check_token” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: pass → fail
- [functional] Server version: 1.0.0 → 1.1.0
- [cosmetic] “check_payment_counterparty” reworded the description of “chain”
- [cosmetic] “check_token” reworded the description of “address”
- [cosmetic] “check_token” reworded the description of “chain”

### 2026-11-18 (score 66, +1)

- [security] Tool “check_token” rewrote its description, which is the text the model reads
- [functional improvement] Stability: unverified → 0.03

### 2026-11-17 (score 65)

First indexed and scored.

## MCP tools (3)

### `check_payment_counterparty` (~140 tokens)

Pre-payment counterparty check

Check a wallet/payTo address before paying it: sanctioned crypto address (OFAC/UK/EU), x402 seller reputation, live Base facts, optional counterparty-name screening, signed receipt. Verdict block/review/clear. $0.005 per call after the free daily quota.

Input parameters:

- `address` (string, required): Wallet / payTo address (EVM 0x..., BTC, TRX, ...)
- `chain` (string): Chain for live on-chain facts (default base; solana inferred for Solana addresses). The sanctions check covers every chain.
- `name` (string): Optional counterparty person or company name to sanctions-screen

### `check_token` (~245 tokens)

Pre-trade token risk check (honeypot, taxes, owner powers)

Before buying or accepting a token: simulates a buy and sell on the deepest pool (Uniswap V2/V3/V4 + Aerodrome on Base, Uniswap V2/V3/V4 on Ethereum, Uniswap V2/V3 on Arbitrum, Uniswap V2/V3 + Velodrome on Optimism) to detect honeypots and taxes, and checks owner powers (mint/pause/blacklist/fees), upgradeable proxy, liquidity, copycat symbols and sanctioned owner. Solana mints: freeze/mint authority, permanent delegate, transfer fees and hooks (Token-2022), holder concentration, Jupiter quote round trip and an on-chain sell simulation for a real holder. Verdict avoid/caution/ok with a signed receipt. $0.01 per call after the free daily quota.

Input parameters:

- `address` (string, required): Token contract address (0x...) or Solana mint (base58)
- `chain` (string): Default base (solana is inferred from a base58 address). Buy/sell simulation on base, ethereum, arbitrum and optimism; solana gets mint/freeze authority and Token-2022 extension checks.

### `verify_receipt` (~48 tokens)

Verify a Payment Guard receipt (free)

Free. Verify that a receipt (payload_json + signature) was issued by Agent Payment Guard and has not been altered.

Input parameters:

- `payload_json` (string, required)
- `signature` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dagu3371-agent-payment-guard/agent-payment-guard#diagnostics

## Score history

- 2026-11-21: 66
- 2026-11-20: 66
- 2026-11-19: 65
- 2026-11-18: 66
- 2026-11-17: 65

## Common questions

### What is the Agent Payment Guard MCP server?

Agent Payment Guard is an MCP server listed in the public MCP registry as io.github.dagu3371/agent-payment-guard. Check wallets and tokens before an agent pays or trades: sanctions, honeypots, taxes, reputation. This page covers its hosted endpoint (https://agent-payment-guard.agent-data-apis.workers.dev/mcp).

### Is the Agent Payment Guard MCP server safe to use?

Agent Payment Guard scores 66 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 Agent Payment Guard MCP server expose?

Agent Payment Guard exposes 3 tools: check_payment_counterparty, check_token, verify_receipt. Their descriptions and schemas cost roughly 433 tokens of context every time the server is loaded.

### Does the Agent Payment Guard MCP server require authentication?

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

### Is the Agent Payment Guard MCP server still maintained?

Agent Payment Guard is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Agent Payment Guard MCP server?

VerifyMCP ran 12 checks on Agent Payment Guard, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Agent Payment Guard: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://agent-payment-guard.agent-data-apis.workers.dev/mcp
- Website: https://agent-payment-guard.agent-data-apis.workers.dev/llms.txt
- Changelog RSS feed: https://verifymcp.io/servers/dagu3371-agent-payment-guard/agent-payment-guard.xml
- Changelog JSON feed: https://verifymcp.io/servers/dagu3371-agent-payment-guard/agent-payment-guard/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/dagu3371-agent-payment-guard/agent-payment-guard.json
- HTML version of this page: https://verifymcp.io/servers/dagu3371-agent-payment-guard/agent-payment-guard
