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.

io.github.AgentTanuki/x402-payment-safety

REMOTE · AGENT-GUILD-5D5R.ONRENDER.COM

Authorize x402 payments before signing with request-bound, signed safety decisions.

0 this week 79 Trust /100

Last scanned (21 hours ago)

Scores higher than 74% 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 Security74
  • 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 is enforced; there's no plaintext access path. View diagnostics → Pass
  • 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 Usability54
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 340 tokens (~340/item across 1 items; 1 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage76
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 17% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 2 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 (13)

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

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.

  • 19 Nov 26 0
    • Server version: 2.7.4 → 2.8.0 functional
  • 10 Nov 26 0
    • Server version: 2.7.3 → 2.7.4 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Oct 26 0
    • Server version: 2.7.2 → 2.7.3 functional
  • 19 Oct 26 0
    • Server version: 2.7.1 → 2.7.2 functional
    • Server version: 2.7.0 → 2.7.1 functional
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 14 Sept 26 0
    • Stability: 0.97 → pass security
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-guild-5d5r.onrender.com/mcp/payment-safety/

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=onrender.com CN=WE1,O=Google Trust Services,C=US 19 Nov 2026 17 Feb 2027 ECDSA 256 ECDSA-SHA256 8d72a13c2c41648513b9d014eb5e0339
SANs: onrender.com, *.onrender.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of agent-guild-5d5r.onrender.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
onrender.com. 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-guild-5d5r.onrender.com/mcp/payment-safety/ Verified 200
http (plaintext) http://agent-guild-5d5r.onrender.com/mcp/payment-safety/ HTTPS enforced 301 https://agent-guild-5d5r.onrender.com/mcp/payment-safety/
MCP tools · 1 exposed · ~278 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
guild_x402_payment_safety ~278

PAID. Call this immediately BEFORE signing an x402 payment envelope. Returns one short-lived, Guild-signed AGPD-1 allow/block credential bound to the exact target payment: scheme, CAIP-2 network, asset contract, atomic amount, payee and resource URL, plus optional capability and policy thresholds. Verify it offline with POST /wallet-binding/decision/verify. This is the native MCP transport for the existing HTTP POST /wallet-binding/decision product. An unpaid call returns a complete x402 v2 challenge for the exact request digest. Retry with the official ``_meta['x402/payment']`` carrier; adapters that cannot set request metadata may pass the identical signed PaymentPayload as ``x402_payment``. Conflicting carriers fail closed before facilitator verification or settlement. The decision is issued before metering, so malformed inputs or signing failures are never charged. ``api_key`` uses sandbox credits and is never external revenue. The free identity-only alternative is GET /wallet-binding/resolve.

NameTypeReqDescription
api_keystring––
capabilitystring––
paymentobjectyesThe exact target payment being authorized before wallet signing.
policy–––
ttl_secondsinteger––
x402_payment–––

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the io.github.AgentTanuki/x402-payment-safety MCP server?

io.github.AgentTanuki/x402-payment-safety is a hosted endpoint at https://agent-guild-5d5r.onrender.com/mcp/payment-safety/, 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-guild-5d5r.onrender.com

# add to Claude Code
claude mcp add --transport http agenttanuki-x402-payment-safety 'https://agent-guild-5d5r.onrender.com/mcp/payment-safety/'
Common questions

What is the io.github.AgentTanuki/x402-payment-safety MCP server?

io.github.AgentTanuki/x402-payment-safety is an MCP server listed in the public MCP registry as io.github.AgentTanuki/x402-payment-safety. Authorize x402 payments before signing with request-bound, signed safety decisions. This page covers its hosted endpoint (https://agent-guild-5d5r.onrender.com/mcp/payment-safety/).

Is the io.github.AgentTanuki/x402-payment-safety MCP server safe to use?

io.github.AgentTanuki/x402-payment-safety 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 io.github.AgentTanuki/x402-payment-safety MCP server expose?

io.github.AgentTanuki/x402-payment-safety exposes 1 tool: guild_x402_payment_safety. Their descriptions and schemas cost roughly 278 tokens of context every time the server is loaded.

Does the io.github.AgentTanuki/x402-payment-safety MCP server require authentication?

No. We connected to io.github.AgentTanuki/x402-payment-safety without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the io.github.AgentTanuki/x402-payment-safety MCP server still maintained?

io.github.AgentTanuki/x402-payment-safety 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 io.github.AgentTanuki/x402-payment-safety MCP server?

VerifyMCP ran 13 checks on io.github.AgentTanuki/x402-payment-safety, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.