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.
Check x402 payment terms and preview observed endpoint history on Arc mainnet.
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 4/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 | 24/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 Veyra Trust. Follow https://mcp.popnx.com/i/mioku50-veyra-trust.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 (agent-commerce-six.vercel.app) · ✓ Commands checked Nov 20, 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
Veyra Trusthttps://agent-commerce-six.vercel.app/api/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
+ConnectorsVeyra Trust
Use Veyra Trust and tell me what you can do for me, then show me one thing✓ If Claude says it is using Veyra Trust or shows a Veyra Trust 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
Veyra Trusthttps://agent-commerce-six.vercel.app/api/mcpStart a new chat and pick Veyra Trust from your plugins before typing
Use Veyra Trust and tell me what you can do for me, then show me one thing✓ If ChatGPT says it is using Veyra Trust or shows a Veyra Trust 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 veyra-trust https://agent-commerce-six.vercel.app/api/mcpYou should see Veyra Trust listed as connected
Use Veyra Trust and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using Veyra Trust or shows a Veyra Trust 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 Veyra Trust and tell me what you can do for me, then show me one thing✓ If Cursor says it is using Veyra Trust or shows a Veyra Trust 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 Veyra Trust and tell me what you can do for me, then show me one thing✓ If VS Code says it is using Veyra Trust or shows a Veyra Trust 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://agent-commerce-six.vercel.app/api/mcpJSON settings are under “For developers” below
Claude Code
claude mcp add --transport http --scope user veyra-trust https://agent-commerce-six.vercel.app/api/mcpCursor (~/.cursor/mcp.json)
{
"mcpServers": {
"veyra-trust": {
"url": "https://agent-commerce-six.vercel.app/api/mcp"
}
}
}VS Code (mcp.json)
{
"servers": {
"veyra-trust": {
"type": "http",
"url": "https://agent-commerce-six.vercel.app/api/mcp"
}
}
}These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Based 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
Tool names and descriptions exactly as the server reported them on Nov 20, 2026. The maker wrote them, not us; we show them as plain text.
veyra_check_endpointCheck the live USDC offer for an x402 endpoint on Arc mainnet before paying. Returns an unsigned verdict and evidence.
veyra_endpoint_historyPreview the recency and coverage of stored Arc USDC observations. Full history and change details are sold separately.
veyra_list_resourcesList Veyra's published free and paid x402 API resources and their HTTP methods.
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 20, 2026
The registry name was verified with the GitHub account mioku50, which owns the repo
Code last changed today
Uses Apache-2.0
Responded in 88 ms (HTTP 200)
No sign-in needed
Read 3 tool descriptions and found no hidden instructions to the AI
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/mioku50-veyra-trust)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.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed today, and the latest version (1.0.0) 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 Veyra Trust | Stripe MCP | flightclaw | Trade It | Marketplace Ad Pros: Amazon Ads & Seller Central | idealo MCP Server | |
|---|---|---|---|---|---|---|
| Runs where | 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 | 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 | 5/5 | 4/4 | 4/4 |
| License | Apache-2.0 | 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.
## Veyra decides. Circle pays.
Before an agent spends USDC, Veyra decides whether it should pay, whom, and how much.
Circle gives an agent a wallet, a marketplace, and a way to pay. Veyra is the independent layer in front of that: it measures the evidence available about a counterparty, ranks the alternatives, enforces budget and risk policy, and issues a signed authorization bound to one endpoint and one amount. After execution, the observed outcome becomes new reputation on Arc.
ERC-8004 · ERC-8183 · x402 · Gateway Nanopayments · USDC · Arc
Live — [agent-commerce-six.vercel.app](https://agent-commerce-six.vercel.app) · Create an agent, the front door — a personal agent, its brief, and what it has earned on Arc · Choose and pay yourself, the same decision driven by hand · Decision log, every trust-routed action, authorization and onchain settlement as it happened
On Arc mainnet Veyra is ERC-8004 agent #298. It sells its Trust API there, paid through Circle Gateway. Its own contracts (the Trust Gate, the evaluator and the proof registry) stay on Arc Testnet until they are audited.
The front door creates Nova, a personal agent owned by the person who made it. Nova starts from an owner-stated goal, interests, and a short owner-confirmed account of where the work already is. It reads official publications and release notes, explains significant changes against what has already been built, with source excerpts, and keeps ordinary commit counts and API listings in background history. Nova may propose a change to that project context and can never confirm one itself. Public-source analysis uses the app's model without charging the owner's wallet.
GOAL a concrete result the owner wants
↓ STATE what is already true about the work, confirmed by the owner ↓ OBSERVE official publications · release notes · payment changes ↓ EXPLAIN what changed · why it matters against work already done · next step · source excerpts ↓ FEEDBACK was this result useful? ↓ only for a specific unanswered question PROPOSE suitable tool · expected result · exact price · Veyra policy ↓ only after owner approval and existing execution checks SIGN → EXECUTE → VERIFY → RECEIPT / ARC ATTESTATION
Ask Nova. The owner can put a question to Nova directly.
The brief reads Arc first and Base after, with one card per endpoint. The cards come from Circle's catalogue and from the ERC-8004 registry on Arc.
A missing answer is a research hypothesis, not permission to spend. Financial permission remains Veyra's separate deterministic decision. The owner signs every payment, because autonomous spending is frozen.
Nova never holds money and there is no signing path in its code. It can want to spend and it says so, with a price and a verdict on the item; the payment goes through the same selection, clearance and wallet signature as any other Veyra purchase.
An identity is earned, not granted. The rule is a verified purchase and an attestation somebody else can read — not because Arc re-checks Veyra's verdict (it does not; the verdict stays Veyra's) but because a claim that lives only in Veyra's database is a claim whose only witness is the party making it.
INTENT "Research the latest developments in Ambient"
budget 0.10 USDC · optimize for trust ↓ DISCOVER ERC-8004 agents on Arc · Circle x402 marketplace 4 candidates ↓ VERIFY live endpoint probe · catalog drift · latency settlement history · onchain identity evidence coverage caps the tier ↓ DECIDE ALLOW · ALLOW_WITH_LIMITS · REQUIRE_EVALUATOR · REVIEW · DENY fails closed, never silently ↓ EIP-712 clearance, bound to endpoint + amount EXECUTE x402 / Gateway Nanopayments · ERC-8183 escrow on Arc ↓ LEARN observed outcome → reputation on Arc
One decision core. Two ways to spend. Every score traceable to the evidence that produced it.
Nova proposes, and the owner signs every payment. On 26 September autonomous spending was frozen for every user:
AUTONOMY_FROZEN is a constant in lib/execution/autonomy-freeze.ts, not a setting, so no environment variable can undo it.AUTOPILOT mandates are refused.Before the freeze, Nova rehearsed spending it could not do:
ExecutionMandate (EIP-712, v2, mode: PREVIEW). It named the capabilities, rails, spending ceilings and minimum trust score.That epoch ended on 22 September, when its mandate expired. It was not renewed.
A PREVIEW mandate can never authorize a live payment. Execution refuses any
mode but
AUTOPILOT. The decision table has no column for a signature, a
clearance, a transaction or a settled amount.
The next step keeps the owner in control. Nova will propose hiring a specific ERC-8004 agent for a task at a price, and the owner will confirm every hire.
Deterministic evaluator: lib/nova/autonomy.ts · the one mandate it issues: lib/nova/autonomy-mandate.ts
An autonomous agent with a funded wallet pays whoever answers first. It cannot tell a service that has settled 147 payments from one listed an hour ago, and it does not notice when the catalog price is no longer what the endpoint charges. Veyra answers the question that comes first: should I pay this endpoint at all, and for how much.
A first-contact endpoint never reaches ALLOW — not because it is bad, but because no settlement history exists for a counterparty nobody has paid yet. Veyra reports the absence of evidence instead of scoring around it.
A complete ERC-8183 job — creation, USDC escrow, deliverable, independent evaluation, payout — executed on Arc Testnet, with every step backed by a transaction hash:
| Job | #186207 on Arc Testnet |
| Lifecycle cost | 560,260 gas — 0.0118 USDC, about 1.2 cents |
| Time to payout | 19 seconds, createJob → USDC in the provider's wallet |
| Policy checks | 11 of 11 passed, deliverable re-fetched and re-hashed by the evaluator |
The same engine, policy tiers, and EIP-712 clearance serve both. What differs is the candidate source and the shape of the evidence.
| API purchase | Agent job | |
|---|---|---|
| Discover | Circle x402 marketplace · offers declared in the ERC-8004 registry on Arc | ERC-8004 IdentityRegistry on Arc |
| Evidence | live 402 probe, catalog drift, latency | onchain settlement history, evaluator verdicts |
| Execute | x402 / Gateway Nanopayments | ERC-8183 job with USDC escrow |
| Verify | response validity, settlement | independent evaluator verdict, signed EIP-712 |
An x402 purchase settles wherever the endpoint sells, and Nova reads Arc first. On 23 September Circle's catalogue listed 482 offers on Arc mainnet and 1,009 on Base. Identity, authorization, attestation and escrow stay on Arc. The product says which chain a price is on, rather than letting the Arc heading imply one.
Settlement is a property of the endpoint too:
A trust score is worth nothing if you cannot see what produced it, so every decision exposes its evidence: the live 402 challenge against the advertised one, settled ERC-8183 jobs and evaluator verdicts on Arc, observed latency and uptime over time, and project and treasury signals. These are inputs to a decision, not separate products.
The standards Veyra is built on, in the role each one actually plays:
| Primitive | Role |
|---|---|
| Nova | The personal agent in front of all of it — watches, proposes, holds no key |
| ERC-8004 | Agent identity and reputation registries on Arc |
| ERC-8183 | Job lifecycle: escrow, deliverable, evaluation, settlement |
| Veyra Trust Gate | EIP-712 clearance, verified and consumed onchain |
| Veyra Evaluator | Independent, fail-closed verdicts that authorize ERC-8183 payout |
| x402 / Nanopayments | Gas-free USDC payment for an API call — a direct EIP-3009 authorization, or a batched Gateway accept where the endpoint takes one |
| Mandates | EIP-712 budget and capability limits an agent operates under — PREVIEW rehearses, AUTOPILOT pays |
| Arc Proof Registry | Verified purchases written onchain: parties, amount, request and response hashes |
The language model turns a request into a structured intent — capability, budget, priority — and decides what is worth asking. It does not choose who gets paid and it cannot reach the evaluator's inputs except by producing a proposal the market priced. Ranking, policy, exposure limits and the signed authorization are deterministic and reproducible from the evidence, so the same inputs always produce the same decision, and it can be audited later.
Discoverable and payable by the machinery it verifies, at /.well-known/x402. The verdict is free, with its evidence; the signed clearance costs, because a contract can consume an attestation and cannot consume an opinion. Reporting what happened after a purchase earns a credit toward the next one.
On Arc mainnet Veyra sells two answers of its own:
history, what it has observed of an endpoint, at 0.005 USDC;select, a ranked choice of sellers for a task, at 0.02 USDC.Both are paid only on Arc, through Circle Gateway, to Veyra's own Circle wallet. Credits do not pay there, and no clearance is signed there, because the Trust Gate is on Arc Testnet. See the OpenAPI document and the ERC-8004 registration.
| | Arc mainn