PayStage — x402 payment safety and spend policy
● Activeio.github.base-buzz/x402-payment-safety
x402 payment safety: judge a payment against your policy before signing. No keys, never signs.
Connect this server
One click to install, or copy the config below. Suits: Claude Desktop · Cursor.
Or add it manually — claude_desktop_config.json (Claude Desktop) or .cursor/mcp.json (Cursor):
{
"mcpServers": {
"x402-payment-safety": {
"command": "npx",
"args": [
"-y",
"@paystage/mcp@0.8.15"
]
}
}
}claude mcp add x402-payment-safety -- npx -y @paystage/mcp@0.8.15codex mcp add x402-payment-safety -- npx -y @paystage/mcp@0.8.15code --add-mcp '{"name":"x402-payment-safety","type":"stdio","command":"npx","args":["-y","@paystage/mcp@0.8.15"]}'Syntax from each client's docs (Claude Code: claude mcp add; Codex: codex mcp add; VS Code: code --add-mcp). Placeholders in angle brackets are values you fill in.
A starting point — check the repository for exact arguments and setup. Restart your client after editing the config.
- Category
- Finance
- Version
- 0.8.15
- Registry
- active
- Published
- 11/18/2026
Live check
checked Nov 19, 2026, 22:07 UTCThe endpoint answered the MCP handshake as "paystage" and listed 10 tools. Answering since Nov 18, 2026.
Context cost ≈ 2.6k tokens of tool definitions a client loads per conversation (estimate: characters ÷ 4) across 10 tools.
Tools (10)
tool list changed Nov 19, 2026, 22:07 UTCevaluate_mcp_payment5 paramsverify 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'). 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.
Show parametersHide parameters
payment_requiredrequiredpolicy_pathstringpolicyagent_idstringWhich agent is asking. Required to reach per-agent budgets in policy.agents.payment_identifierstringThe 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` i
list_outstanding_auths8 paramsspending 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).
Show parametersHide parameters
walletstringrequirednetworkstringtokensarrayspendersarraypolicy_pathstringpolicyeip3009_noncesarrayrpc_urlstring
evaluate_outstanding_auths8 paramsspending 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.
Show parametersHide parameters
walletstringrequirednetworkstringtokensarrayspendersarraypolicy_pathstringpolicyeip3009_noncesarrayrpc_urlstring
evaluate_hip3_trade4 paramstransaction 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.
Show parametersHide parameters
proposalobjectrequiredpolicypolicy_pathstringsnapshot
evaluate_velocity5 paramstransparent 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.
Show parametersHide parameters
historyarrayproposedobjectrequiredpolicypolicy_pathstringnow_msinteger
verify_receipt2 paramsverify 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.
Show parametersHide parameters
receiptrequiredThe receipt object as issuedkey_urlstringOverride the published key location
decode_payment_required1 paramverify 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.
Show parametersHide parameters
headerstringrequiredThe raw base64 value of the payment-required header
validate_policy1 paramspending 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.
Show parametersHide parameters
policyrequired
request_testnet_funds2 paramstest 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.
Show parametersHide parameters
addressstringrequiredfaucetUrlstring
evaluate_batch2 paramstransaction 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.
Show parametersHide parameters
paymentsarrayrequiredpolicyrequired
Checked by Serverdex with a plain initialize + tools/list call to api.paystage.xyz/mcp, no credentials, about once a day. A failed check is never a removal.
On GitHub
read Nov 18, 2026- Stars
- 6
- Forks
- 11
- Last push
- Nov 18, 2026
- License
- MIT
TypeScriptagent-paymentsai-agentsbasemcpmcp-serverpayment-safetyusdcx402
From the README
PayStage Your agent's wallet should not sign because a server asked it to. PayStage sits between an agent and the x402 payment it is about to make, and answers one question before the signature exists: should this payment happen? Every tool returns pay, review, or donotpay, with the rule that fired and a receipt you can keep. The gap it fills is narrow and load-bearing. x402 makes paying trivial and leaves deciding to the caller: a wallet enforces signatures, not intent. @paystage/x402-guard evaluates the challenge before the wallet signs, so a wrong payee, an over-cap amount or an unknown asset never reaches the signing step at all. Where the money does not move The design point is the arrow that is missing. The wallet signs only after the challenge has been judged; a refusal returns the seller's own 402 with a verdict header attached, so there is nothing to revoke afterwards. review is reported as review either way. When onReview: "pay" lets an ambiguous payment through, the header still says review, because the evaluator's finding and the caller's instruction to tolerate it are different facts — a caller that cannot tell "clean" from "warned but paid" cannot audit itself. The rule that fires travels in x-paystage-reason-codes. What decides donotpay is a real refusal, not a warning: a payee on the known-drainer or OFAC list, an over-cap amount, a wrong network or asset, a policy that denies the payee, or a challenge that cannot be parsed.…
Read the full README on GitHub →Remotes
- streamable-http
https://api.paystage.xyz/mcp
Alternatives to PayStage — x402 payment safety and spend policy
Best Finance servers →The most-starred Finance servers in the index, with their live-check result.
| Server | Stars | Last push | Live check |
|---|---|---|---|
| CCXT | 44,881 | Nov 2026 | Local / not checked |
| QR Rápido | 7,477 | Nov 2026 | Needs sign-in |
| Finance Toolkit | 5,522 | Nov 2026 | Needs sign-in |
| AKQuant | 2,607 | Nov 2026 | Local / not checked |
| com.stripe MCP | 2,072 | Nov 2026 | Needs sign-in |
PayStage — x402 payment safety and spend policy: questions people ask
- Is PayStage — x402 payment safety and spend policy a remote or a local MCP server?
- According to its entry in the official MCP registry, PayStage — x402 payment safety and spend policy ships as a hosted endpoint (streamable-http) that your client connects to by URL and as a local package (npm) that your client starts on your machine. Use the hosted endpoint when your client supports Streamable HTTP; use the package when you want it to run locally.
- Does PayStage — x402 payment safety and spend policy need an API key?
- Its hosted endpoint completed the Serverdex live check — an MCP initialize + tools/list call — with no credentials on Nov 19, 2026. Individual tools may still ask for a key when called.
- Is PayStage — x402 payment safety and spend policy still maintained?
- Active: the repository's last commit today. Last push Nov 18, 2026, 6 GitHub stars, MIT licence. Read from GitHub on Nov 18, 2026.
- What tools does PayStage — x402 payment safety and spend policy expose?
- 10 tools as listed by the server itself during the live check, including evaluate_mcp_payment, list_outstanding_auths, evaluate_outstanding_auths, evaluate_hip3_trade, evaluate_velocity. The full list with parameters is in the Live check section above.
- How do I add PayStage — x402 payment safety and spend policy to Claude, Cursor or VS Code?
- Copy the config in "Connect this server" into your client's MCP config file (claude_desktop_config.json, ~/.cursor/mcp.json or .vscode/mcp.json), or use the one-click Add to Cursor / Add to VS Code buttons and the one-line commands for Claude Code and Codex; then restart the client.
More Finance servers
Browse all Finance →MIDAS Protocol
BbrainFrance
Complete financial infrastructure for AI agents — payments, lending, escrow & more.
AESO MCP
bchoi-qwe
Typed Alberta electricity market data and analytics via official AESO APIs.
Polymarket MCP
beejmaxx
Polymarket market data, live CLOB books, replay, simulation, and opt-in trading in Rust.
Financial Evidence
beepboop2025
Read-only public financial evidence from LiquiLens, Undertow, Seiche and Palimpsest.
Financial Evidence Workspace
beepboop2025
Read-only cited financial datasets, bounded research queries and source diagnostics.
Seiche, LiquiLens and Undertow source data
beepboop2025
Funding histories, bank filings and settlement data with source receipts, units and capture clocks.
Add the badge to your site
Show visitors that PayStage — x402 payment safety and spend policy is listed here — it’s also the link we check for a free listing.
HTML — for your website
<a href="https://serverdex.io/server/io-github-base-buzz-x402-payment-safety?utm_source=badge"><img src="https://serverdex.io/brand/badge.svg" alt="PayStage — x402 payment safety and spend policy — listed on Serverdex" width="123" height="40" loading="lazy"></a>Recommended. A dofollow link from your own domain is the one that counts for search engines, and it's the link we check for a free listing.
Markdown — for your README
[](https://serverdex.io/server/io-github-base-buzz-x402-payment-safety?utm_source=badge)Nice for visibility, but GitHub marks README links nofollow, so it doesn't pass authority. Use the HTML badge on your site as well.