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.

PayStage — x402 payment safety and spend policy

REMOTE · API.PAYSTAGE.XYZ · 2 COMPONENTS

x402 payment safety: judge a payment against your policy before signing. No keys, never signs.

63 Trust /100

Last scanned (23 hours ago)

Scores higher than 45% of remote servers

Reachable. Last reached 21 Nov 2026.

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 Usability60
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1656 tokens (~165/item across 10 items; 10 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 Management10
  • Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 13% 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 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (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 0
    • Tool “evaluate_hip3_trade” rewrote its description, which is the text the model reads security
    • Tool “evaluate_outstanding_auths” rewrote its description, which is the text the model reads security
    • Tool “evaluate_velocity” rewrote its description, which is the text the model reads security
    • Tool “list_outstanding_auths” rewrote its description, which is the text the model reads security
    • Tool “request_testnet_funds” rewrote its description, which is the text the model reads security
    • Tool “validate_policy” rewrote its description, which is the text the model reads security
    • Tool “verify_receipt” rewrote its description, which is the text the model reads security
    • Tool “decode_payment_required” rewrote its description, which is the text the model reads security
    • Tool “evaluate_batch” rewrote its description, which is the text the model reads security
    • Tool “evaluate_mcp_payment” rewrote its description, which is the text the model reads security
    • Schema quality: 128 → 165 ▼ functional
    • Schema quality: 128 → 142 ▼ functional
    • “evaluate_mcp_payment” added an optional parameter “payment_identifier” cosmetic
  • 19 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 18 Nov 26 62

    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://api.paystage.xyz/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=paystage.xyz CN=WE1,O=Google Trust Services,C=US 30 Oct 2026 28 Jan 2027 ECDSA 256 ECDSA-SHA256 6c7711760ab8fd6f0e4733bf76b1da6e
SANs: paystage.xyz, api.paystage.xyz, *.api.paystage.xyz
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 api.paystage.xyz. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
xyz. DS published 3599, 18130 8, 8 Verified
paystage.xyz. 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://api.paystage.xyz/mcp Verified 200
http (plaintext) http://api.paystage.xyz/mcp Inconclusive 405
MCP tools · 10 exposed · ~1,656 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
decode_payment_required ~140

verify the recipient. Call this first when a 402 response arrives and you cannot read the payment-required header. Returns the decoded x402 v2 challenge: scheme, network, asset, atomic amount, payee, resource and timeout. Pure decoding: no network call, no signature, no verdict — use evaluate_mcp_payment when you want a decision. Fails closed with a named error if the header is malformed or not base64. Fails closed: do not invent authority — a missing policy, identity, cost or evidence is a refusal, never a default.

NameTypeReqDescription
headerstringyesThe raw base64 value of the payment-required header

No output schema declared.

No examples provided.

evaluate_batch ~141

transaction scope. Call this when an agent might pay several times in one turn and you want one policy decision covering all of them. Verdict is pay | review | do_not_pay per item, in input order, with reason codes — so the agent can stop at the first refusal rather than discovering it after three payments. Read-only, holds no keys, never signs. Cheaper and more consistent than calling evaluate_mcp_payment in a loop: same policy, one round trip. Fails closed: do not invent authority — a missing policy, identity, cost or evidence is a refusal, never a default.

NameTypeReqDescription
paymentsarrayyes–
policy–yes–

No output schema declared.

No examples provided.

evaluate_hip3_trade ~149

transaction scope. Call this BEFORE an agent places a HIP-3 / trade.xyz order. Verdict is allow | review | do_not_trade, with the rule that fired (notional above cap, market not allowed, leverage too high). Returns the decision and a one-line reason. Local policy only: this is not financial advice, holds no keys, and cannot place or cancel an order. Prices come from a read-only market query. Fails closed: do not invent authority — a missing policy, identity, cost or evidence is a refusal, never a default.

NameTypeReqDescription
policy–––
policy_pathstring––
proposalobjectyes–
snapshot–––

No output schema declared.

No examples provided.

evaluate_mcp_payment ~270

verify the recipient. Call this BEFORE signing any x402 payment. Verdict is pay | review | do_not_pay, each with stable reason codes (e.g. 'amount 1.00 USDC exceeds max_amount 0.05 USDC'). Fail-closed by design: do not invent authority — when policy, identity, cost or evidence is missing the answer is a refusal or a review, never a pay. Returns the decision plus a signed receipt you can verify offline with verify_receipt. Read-only: holds no keys, never signs, never moves funds. A refusal costs nothing. This tool evaluates locally, so it makes no network calls and returns no seller reputation; the hosted HTTP API adds `seller_reputation` (domain and certificate age) because it can reach the network.

NameTypeReqDescription
agent_idstring–Which agent is asking. Required to reach per-agent budgets in policy.agents.
payment_identifierstring–The x402 payment-identifier for this challenge, if the seller or client supplies one. Passing the same value on a retry turns the second verdict into `review` instead of a second `pay`, because a ret…
payment_required–yes–
policy–––
policy_pathstring––

No output schema declared.

No examples provided.

evaluate_outstanding_auths ~186

spending limits. Call this when an agent already holds authorisations and you need to know which are dangerous. Verdict is pay | review | do_not_pay per authorisation, with reason codes naming the rule that fired (unlimited allowance, expiry already passed, spender not on the allow-list). Returns per-authorisation decisions plus a summary action. Read-only: never revokes, never signs. Revocation is a transaction you send yourself. Fails closed: do not invent authority — a missing policy, identity, cost or evidence is a refusal, never a default.

NameTypeReqDescription
eip3009_noncesarray––
networkstring––
policy–––
policy_pathstring––
rpc_urlstring––
spendersarray––
tokensarray––
walletstringyes–

No output schema declared.

No examples provided.

evaluate_velocity ~155

transparent risk assessments. Call this when an agent is about to make its Nth payment and you need to know whether the rate itself is the risk. Verdict is pay | review | do_not_pay over a rolling window (per-hour and per-day spend, count of payees). Returns the decision plus which window was breached. Read-only: it reads the history you pass in, holds no keys, and calls no external service. Fails closed: do not invent authority — a missing policy, identity, cost or evidence is a refusal, never a default.

NameTypeReqDescription
historyarray––
now_msinteger––
policy–––
policy_pathstring––
proposedobjectyes–

No output schema declared.

No examples provided.

list_outstanding_auths ~181

spending limits. Call this when auditing what an agent could still spend without a new signature — ERC-20 allowances, Permit2 and EIP-3009 authorisations. Returns each authorisation with spender, amount and expiry. Read-only and needs only a public RPC; no key, no funds moved. Use it after an incident to see what remains exposed, not to revoke anything (this tool cannot revoke). Fails closed: do not invent authority — a missing policy, identity, cost or evidence is a refusal, never a default.

NameTypeReqDescription
eip3009_noncesarray––
networkstring––
policy–––
policy_pathstring––
rpc_urlstring––
spendersarray––
tokensarray––
walletstringyes–

No output schema declared.

No examples provided.

request_testnet_funds ~162

test funds. Call this when you need Base Sepolia USDC to exercise the paid path end to end — one drip of 0.5 USDC per address per 24 hours, and the refusal tells you when it resets rather than just failing. Reads a public faucet: no key needed, no account, and it can only ever send testnet USDC. Use a throwaway address for anything automated; the cap is per address, so a script that generates a new address per call is not clever, it is why faucets get closed. Fails closed: do not invent authority — a missing policy, identity, cost or evidence is a refusal, never a default.

NameTypeReqDescription
addressstringyes–
faucetUrlstring––

No output schema declared.

No examples provided.

validate_policy ~111

spending limits. Call this before wiring a policy into anything: a policy that fails validation makes every evaluation refuse, which looks like a product bug and is not one. Returns valid: true, or the exact field and message that is wrong. No payment needed, no network call, no key. Use it in CI on the policy file your agent ships with. Fails closed: do not invent authority — a missing policy, identity, cost or evidence is a refusal, never a default.

NameTypeReqDescription
policy–yes–

No output schema declared.

No examples provided.

verify_receipt ~161

verify the recipient. Call this when you have a receipt and want to know whether it is genuine, without trusting the server that issued it. Returns VALID with the verdict it attests to, INVALID if the payload was altered, or UNVERIFIABLE when the key cannot be fetched — and UNVERIFIABLE is a refusal, not a pass. Needs only the receipt JSON and a network connection; no account, no shared secret. Fetches the signing key from a published URL you can pin with key_url. Fails closed: do not invent authority — a missing policy, identity, cost or evidence is a refusal, never a default.

NameTypeReqDescription
key_urlstring–Override the published key location
receipt–yesThe receipt object as issued

No output schema declared.

No examples provided.

Install

How do I install the PayStage — x402 payment safety and spend policy MCP server?

PayStage — x402 payment safety and spend policy is a hosted endpoint at https://api.paystage.xyz/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 · api.paystage.xyz

# add to Claude Code
claude mcp add --transport http base-buzz-x402-payment-safety 'https://api.paystage.xyz/mcp'
Common questions

What is the PayStage — x402 payment safety and spend policy MCP server?

PayStage — x402 payment safety and spend policy is an MCP server listed in the public MCP registry as io.github.base-buzz/x402-payment-safety. x402 payment safety: judge a payment against your policy before signing. No keys, never signs. This page covers its hosted endpoint (https://api.paystage.xyz/mcp).

Is the PayStage — x402 payment safety and spend policy MCP server safe to use?

PayStage — x402 payment safety and spend policy scores 63 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 PayStage — x402 payment safety and spend policy MCP server expose?

PayStage — x402 payment safety and spend policy exposes 10 tools: evaluate_mcp_payment, list_outstanding_auths, evaluate_outstanding_auths, evaluate_hip3_trade, evaluate_velocity, and 5 more. Their descriptions and schemas cost roughly 1,656 tokens of context every time the server is loaded.

Does the PayStage — x402 payment safety and spend policy MCP server require authentication?

No. We connected to PayStage — x402 payment safety and spend policy without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the PayStage — x402 payment safety and spend policy MCP server still maintained?

PayStage — x402 payment safety and spend policy 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 PayStage — x402 payment safety and spend policy MCP server?

VerifyMCP ran 12 checks on PayStage — x402 payment safety and spend policy, 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 PayStage — x402 payment safety and spend policy: 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.