Stripe MCP
Stripe’s official server lets AI view and manage customers, products, payments and invoices. Connect to Stripe’s cloud and sign in with OAuth.
x402 payment safety: judge a payment against your policy before signing. No keys, never signs.
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 32/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 12/12 | Full marks for a release or code change within 30 days |
| Still answering | 8/8 | The cloud endpoint answered at the last check |
| Usage score | 52/100 |
Quality: Passed 5/5 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Pick the AI app you use, then copy the settings.
Let your AI install it with one sentence
Please install PayStage — x402 payment safety and spend policy. Follow https://mcp.popnx.com/i/base-buzz-x402-payment-safety.md, show me the commands and wait for my OK before running them.Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads
Passed 5/5 checks · What you ask goes through the maker’s server (api.paystage.xyz) · ✓ Commands checked Nov 18, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude · about 2 min
No key, nothing to install · Set it up once on claude.ai or the desktop app, then use it in chat · free accounts can add 1 · on Team/Enterprise an Owner adds it
CustomizeConnectors
Copy each value into the field with the same name in Claude, then click Continue
PayStage — x402 payment safety and spend policyhttps://api.paystage.xyz/mcpClick Continue past the sign-in settings Claude detected · under Authentication choose what the maker says (Sign in now, Sign in when needed or No sign in), then click Add
+ConnectorsPayStage — x402 payment safety and spend policy
Use PayStage — x402 payment safety and spend policy and tell me what you can do for me, then show me one thing✓ If Claude says it is using PayStage — x402 payment safety and spend policy or shows a PayStage — x402 payment safety and spend policy tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with ChatGPT, depending on your plan
Full MCP: ChatGPT Business, Enterprise or Edu on the web · Pro: connects with read/fetch permissions, so tools that change data may not work · Plus: not confirmed in OpenAI’s docs; if you see an add-custom-MCP option on the Plugins page you can try these steps · web only
Plugins+Add custom MCP server
Enter a name, paste the address under Connection, tick the risk warning and click Create as a plugin
PayStage — x402 payment safety and spend policyhttps://api.paystage.xyz/mcpStart a new chat and pick PayStage — x402 payment safety and spend policy from your plugins before typing
Use PayStage — x402 payment safety and spend policy and tell me what you can do for me, then show me one thing✓ If ChatGPT says it is using PayStage — x402 payment safety and spend policy or shows a PayStage — x402 payment safety and spend policy tool in the answer, you are connected
Menu names checked against OpenAI’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Claude Code · about 2 min
No key, nothing to install
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add --transport http --scope user x402-payment-safety https://api.paystage.xyz/mcpYou should see PayStage — x402 payment safety and spend policy listed as connected
Use PayStage — x402 payment safety and spend policy and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using PayStage — x402 payment safety and spend policy or shows a PayStage — x402 payment safety and spend policy tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor · about 2 min
No key, nothing to install
Use PayStage — x402 payment safety and spend policy and tell me what you can do for me, then show me one thing✓ If Cursor says it is using PayStage — x402 payment safety and spend policy or shows a PayStage — x402 payment safety and spend policy tool in the answer, you are connected
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code · about 2 min
No key, nothing to install
Use PayStage — x402 payment safety and spend policy and tell me what you can do for me, then show me one thing✓ If VS Code says it is using PayStage — x402 payment safety and spend policy or shows a PayStage — x402 payment safety and spend policy tool in the answer, you are connected
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.
Address for apps that connect over the web
https://api.paystage.xyz/mcpJSON settings are under “For developers” below
Claude Code
claude mcp add --transport http --scope user x402-payment-safety https://api.paystage.xyz/mcpCursor (~/.cursor/mcp.json)
{
"mcpServers": {
"x402-payment-safety": {
"url": "https://api.paystage.xyz/mcp"
}
}
}VS Code (mcp.json)
{
"servers": {
"x402-payment-safety": {
"type": "http",
"url": "https://api.paystage.xyz/mcp"
}
}
}Claude Code
claude mcp add --scope user x402-payment-safety -- npx -y @paystage/mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"x402-payment-safety": {
"command": "npx",
"args": [
"-y",
"@paystage/mcp"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"x402-payment-safety": {
"command": "npx",
"args": [
"-y",
"@paystage/mcp"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"x402-payment-safety": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@paystage/mcp"
]
}
}
}PAYSTAGE_POLICY_PATH envPAYSTAGE_RPC_URL envDescriptions are as written by the maker.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
npm: @paystage/mcpBased on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Connect over the internet in
ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Tool names and descriptions exactly as the server reported them on Nov 18, 2026. The maker wrote them, not us; we show them as plain text.
evaluate_mcp_paymentverify 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
list_outstanding_authsspending 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. Us
evaluate_outstanding_authsspending 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 all
evaluate_hip3_tradetransaction 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 no
evaluate_velocitytransparent 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 whi
verify_receiptverify 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 UNVER
decode_payment_requiredverify 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 —
validate_policyspending 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
request_testnet_fundstest 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 se
evaluate_batchtransaction 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 discover
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 18, 2026
The registry name was verified with the GitHub account base-buzz, which owns the repo
Code last changed today
Uses MIT
Responded in 335 ms (HTTP 200)
No sign-in needed
Read 10 tool descriptions and found no hidden instructions to the AI
No entries on OSV.dev for @paystage/mcp@0.8.14
Checks only this package version, not every dependency · checked Nov 18, 2026
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/base-buzz-x402-payment-safety)Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 5 of 5 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
Either way works: install it on your computer or connect to the cloud version.
The GitHub repo last changed today, and the latest version (0.8.14) reached the registry today.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT on the web (full MCP on Business and above; Pro read-only).
In the same category: Stripe MCP, flightclaw, Trade It, Marketplace Ad Pros: Amazon Ads & Seller Central, idealo MCP Server
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Stripe’s official server lets AI view and manage customers, products, payments and invoices. Connect to Stripe’s cloud and sign in with OAuth.
Search ~300 airlines and book flights with a checkout link. OAuth sign-in by email code.
Connect brokerage accounts to AI assistants: holdings, orders, asset lookup, and approved trading.
Amazon Ads, Seller Central, Vendor Central and AMC data for AI agents. Read-only by default.
Search products, compare prices and discover deals across 6 European markets with your AI assistant.
| This one PayStage — x402 payment safety and spend policy | Stripe MCP | flightclaw | Trade It | Marketplace Ad Pros: Amazon Ads & Seller Central | idealo MCP Server | |
|---|---|---|---|---|---|---|
| Runs where | Cloud or install on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install |
| Needs a key | No | No | No | No | No | No |
| Add with + in Claude | No | Yes | No | No | No | No |
| Basic checks | 5/5 | 4/4 | 4/4 | 4/4 | 4/4 | 4/4 |
| License | MIT | MIT | MIT | CC0-1.0 | MIT | MIT |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
PayStage umbrella MCP server: payment preflight, auth watch, HIP-3 trade preflight, and velocity checks.
Not financial advice. The trade preflight tool is a local policy gate only — it does not
place orders or recommend trades.
Published on npm as `@paystage/mcp` — see the npm page for the current version rather than a number here that can go stale.
paystage-verify returning exit 0 means the key it verified against signed this receipt and it has not been altered. That is all it means — and which key that was matters:
key_source: "published" → PayStage's published key: the issuer signed it.key_source: "supplied" (you passed --key or --key-url) → the key you named signed it, which is a weaker claim and not evidence about PayStage at all. Exit 0 on that path says nothing more than that the holder of that key produced the receipt.It does not mean the payment happened — settlement is a separate on-chain event. It does not mean the verdict was correct — a receipt records a decision, not the soundness of the policy behind it. And it does not identify the caller; no caller identity is bound into the payload, by design.
Two narrower points a careful reader should know:
published (PayStage's endpoint) or supplied (someone passed --key). A receipt verified against a supplied key proves only that the holder of *that* key signed it.npx -y -p @paystage/mcp paystage-mcp
The server waits silently for an agent app to connect. That's normal; press Ctrl+C to exit. To try the tools without an app, run npx @modelcontextprotocol/inspector npx -y -p @paystage/mcp paystage-mcp.
Or:
npm install @paystage/mcp
The package exposes a stdio MCP server (bin: paystage-mcp).
{
"mcpServers": { "paystage": { "command": "npx", "args": ["-y", "-p", "@paystage/mcp", "paystage-mcp"], "env": { "PAYSTAGE_POLICY_PATH": "./policy.json" } } } }
Environment variables (all optional):
PAYSTAGE_POLICY_PATH — path to policy.json spending rulesPAYSTAGE_RPC_URL — Base RPC URL overrideevaluate_mcp_payment — Available nowEvaluates a proposed x402 payment against a local policy file and returns a verdict before the agent signs anything.
list_outstanding_auths — Available nowLists outstanding ERC-20, Permit2, and EIP-3009 authorizations.
evaluate_outstanding_auths — Available nowFlags outstanding authorizations that need attention (e.g. authorized but never settled).
evaluate_hip3_trade — Available nowEvaluates a proposed HIP-3 / trade.xyz order against a local TradePolicy and returns a decision: allow | review | do_not_trade.
Backed by @paystage/trade-preflight (published separately), which can also be run standalone:
npx -y @paystage/trade-preflight
The policy is passed as a tool argument; no extra environment variables are required for this tool.
evaluate_velocity — Available nowIs this spend a burst, a spike, or a runaway cadence? Takes the recent action history and a policy.velocity block, and returns pay | review | do_not_pay with the window that was breached.
verify_receipt — Available nowChecks a receipt against the published signing key and returns the verdict it attests to, or why it cannot be trusted. VALID, INVALID (altered), EXPIRED (past its own lifetime), payment-mismatch (genuine, but about a different payment), or UNVERIFIABLE — which is a refusal, not a pass.
decode_payment_required — Available nowDecodes a base64 payment-required header from a 402 response into the JSON challenge: scheme, network, asset, atomic amount, payee, resource and timeout. Pure decoding — no network call, no verdict. Use evaluate_mcp_payment when you want a decision.
validate_policy — Available nowChecks a policy document without evaluating a payment, and returns the exact field and message when it is wrong. Worth running in CI on the policy an agent ships with: an invalid policy makes every evaluation refuse, which looks like a product bug and is not one.
evaluate_batch — Available nowThe same question for several payments at once, one verdict each in input order — so an agent settling a batch stops at the first refusal instead of discovering it after three payments.
Ten packages. Only @paystage/mcp exposes ten MCP tools; the rest are the evaluator, guards for other frameworks, a policy schema and a skill — hence ten packages and ten tools in the same breath.
| Package | Role | Links |
|---|---|---|
@paystage/mcp | umbrella MCP server — start here | npm |
@paystage/x402-guard | policy gate for x402 clients, before the wallet signs | npm |
@paystage/ai-sdk | the same gate as Vercel AI SDK tools | npm |
@paystage/auth-watch | outstanding ERC-20 / Permit2 / EIP-3009 authorisations | npm |
@paystage/policy | policy schema and loader | npm |
@paystage/preflight | x402 payment preflight (the evaluator) | npm |
@paystage/skill | agent skill manifest | npm |
@paystage/trade-preflight | HIP-3 / trade.xyz order preflight | npm |
@paystage/velocity | rate and spend-pattern checks | npm |
@paystage/x-evm | chain-agnostic EVM helpers | npm |
Every verdict can carry a signed receipt. paystage-verify checks one without trusting us — it fetches the published key and verifies the signature over the canonical payload.
npx -y -p @paystage/mcp paystage-verify receipt.json
cat receipt.json | npx -y -p @paystage/mcp paystage-verify -
Exit codes are distinct on purpose:
| Code | Meaning |
|---|---|
| 0 | signature matches the payload |
| 1 | invalid — altered, or signed by a different key |
| 2 | unsigned — a record of the decision, with no proof of who made it |
| 3 | unverifiable — the key could not be fetched, or an input file could not be read, so nothing can be checked |
| 4 | inputs-mismatch — the receipt is genuine but does not cover the --request/--policy you supplied |
| 5 | stale — the receipt is genuine but older than --max-age allows |
"Invalid" and "could not check" are different facts and must not collapse into one failure. --key verifies against a local JWK for point-in-time checks.
This is the umbrella, so its install tree is wider than any single tool and Socket flags it accordingly. What it actually contains:
| Flag | Where it comes from |
|---|---|
| Network access, URL strings | @paystage/auth-watch (Base RPC reads) and @paystage/trade-preflight (one Hyperliquid info query). |
| Filesystem access | @paystage/policy reading your policy file. |
| Environment variable access | PAYSTAGE_POLICY_PATH, PAYSTAGE_RPC_URL. |
| "AI-detected code anomaly" | The official @modelcontextprotocol/server SDK's bundled JSON-schema validator, not PayStage code. |
The umbrella itself is ~16 KB with no network, no filesystem and no eval — the capability lives in the dependencies, because that is what the tools are for.
Install a narrower surface if you only need part of it: @paystage/preflight and @paystage/policy make no network calls at all.
Full table: SECURITY.md.
npx -y -p @paystage/mcp paystage-verify MIT
Every one is read-only. None of them signs, holds a key, or moves money — the agent stays the only signer, which is the entire product.
| tool | what it answers |
|---|---|
evaluate_mcp_payment | should this x402 payment be signed? → pay · review · do_not_pay |
list_outstanding_auths | which ERC-20 / Permit2 / EIP-3009 authorisations are still outstanding |
evaluate_outstanding_auths | which of those need attention before the next payment |
evaluate_hip3_trade | should this HIP-3 / trade.xyz order be placed? → allow · review · do_not_trade |
evaluate_velocity | is this spend a burst, a spike, or a runaway cadence |
verify_receipt | is this receipt really ours — and is it about *this* payment, still in date |
decode_payment_required | what does this base64 402 header actually say |
validate_policy | is this policy document valid, and if not which field |
request_testnet_funds | 0.5 Base Sepolia USDC for testing — one drip per address per 24h, with the reset time |
evaluate_batch | the same question for several payments, one verdict each |
npx -y -p @paystage/mcp paystage-policy check policy.json
Exit 0 valid, 1 invalid (one line per offending field), 2 unreadable. Offline, no key, no signup — the same schema the evaluator enforces, so a file that passes here is a file that will load there.
npx -y -p @paystage/mcp paystage-explain receipt.json
Decision: do_not_pay
signature valid — this receipt is what PayStage issued issued 2026-11-15T18:27:34Z by @paystage/hosted
· It asks for 1 USDC, and the policy allows at most 0.05 USDC.
It verifies the signature first and says plainly when a receipt cannot be trusted. Rules it does not recognise are quoted, not paraphrased — guessing at a refusal's meaning is worse than repeating it.