Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

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.

66 Trust /100

Last scanned (21 hours ago)

Scores higher than 51% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Crypto and Web3

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security63
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • 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. See how to fix → View diagnostics → Partial
  • HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability66
  • AI-judged instruction clarity (good).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
  • Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage90
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 71% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (12)

  • TLS certificate
  • Authorization
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Nov 26 +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.

  • 19 Nov 26 −1
    • Tool “check_token” rewrote its description, which is the text the model reads security
    • Schema quality: pass → fail ▼ functional
    • Server version: 1.0.0 → 1.1.0 functional
    • “check_payment_counterparty” reworded the description of “chain” cosmetic
    • “check_token” reworded the description of “address” cosmetic
    • “check_token” reworded the description of “chain” cosmetic
  • 18 Nov 26 +1
    • Tool “check_token” rewrote its description, which is the text the model reads security
    • Stability: unverified → 0.03 ▲ functional
  • 17 Nov 26 65

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://agent-payment-guard.agent-data-apis.workers.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=agent-data-apis.workers.dev CN=YE2,O=Let's Encrypt,C=US 16 Nov 2026 14 Feb 2027 ECDSA 256 ECDSA-SHA384 64cf7ac3d877ec5b2507eed48671eea713f
SANs: *.agent-data-apis.workers.dev, agent-data-apis.workers.dev
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of agent-payment-guard.agent-data-apis.workers.dev. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
dev. DS published 60074 8 Verified
workers.dev. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://agent-payment-guard.agent-data-apis.workers.dev/mcp Verified 200
http (plaintext) http://agent-payment-guard.agent-data-apis.workers.dev/mcp Inconclusive 405
MCP tools · 3 exposed · ~433 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
check_payment_counterparty ~140

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.

NameTypeReqDescription
addressstringyesWallet / payTo address (EVM 0x..., BTC, TRX, ...)
chainstring–Chain for live on-chain facts (default base; solana inferred for Solana addresses). The sanctions check covers every chain.
namestring–Optional counterparty person or company name to sanctions-screen

No output schema declared.

No examples provided.

check_token ~245

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.

NameTypeReqDescription
addressstringyesToken contract address (0x...) or Solana mint (base58)
chainstring–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.

No output schema declared.

No examples provided.

verify_receipt ~48

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

NameTypeReqDescription
payload_jsonstringyes–
signaturestringyes–

No output schema declared.

No examples provided.

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.

remote · agent-payment-guard.agent-data-apis.workers.dev

# add to Claude Code
claude mcp add --transport http dagu3371-agent-payment-guard 'https://agent-payment-guard.agent-data-apis.workers.dev/mcp'
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.