{ "data": { "a": { "slug": "adyen-mcp-server", "name": "Adyen MCP server", "vendor": "Adyen N.V.", "vendorUrl": "https://www.adyen.com", "kind": "mcp", "category": "payment-platforms", "summary": "Adyen's official MCP server lets an AI client call Adyen's Checkout, Management, Legal Entity Management and Balance Platform APIs with a merchant's API key. It runs locally over stdio through `npx @adyen/mcp` and is labelled alpha.", "url": "https://www.anchorterminal.com/tools/adyen-mcp-server", "markdownUrl": "https://www.anchorterminal.com/tools/adyen-mcp-server.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/adyen-mcp-server.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/adyen-mcp-server.json", "repo": "https://github.com/Adyen/adyen-mcp", "license": "MIT for the server. The Adyen APIs it calls are a closed service under a merchant agreement and the Adyen Terms and Conditions", "transports": [ "stdio" ], "packages": [ { "registry": "npm", "name": "@adyen/mcp" } ], "auth": "api-key", "authNotes": "The server needs an Adyen API key, read from `ADYEN_API_KEY` or the `--adyenApiKey` flag, and sends it to Adyen through `@adyen/api-library`. A person creates the key in the Customer Area under Developers, API credentials. Each credential has roles that set what it may do, and a company-level credential reaches every linked merchant account. Generating a new key leaves the old one active for 24 hours. The README lists 16 roles for the full tool set and advises a new credential used only for the server, with roles cut to the tools in use.", "pricing": "usage", "pricingNotes": "The server is free and MIT. Adyen charges for live payments, a fixed processing fee of $0.13 per transaction plus a fee set by the payment method, with no setup or monthly fee per the pricing page. Many methods are listed at interchange plus 0.60%. The pricing FAQ says a minimum invoice applies depending on industry or business model, through sales. A developer test account is free through a signup form, and Adyen says it does not guarantee approval as a customer (checked 2026-10-09).", "priceSummary": "$0.13 / tx", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the MCP docs page, the repository or the pricing page (checked 2026-10-09).", "endpoints": [] }, "toolCount": 38, "popularity": { "githubStars": 27, "npmWeekly": 168, "pypiWeekly": null, "asOf": "2026-10-09" }, "docsUrl": "https://docs.adyen.com/development-resources/mcp-server", "llmsTxt": "https://docs.adyen.com/llms.txt", "capabilities": [ "payments.checkout", "payments.card" ], "tags": [ "official", "local", "open-source", "mcp", "api-key", "sandbox", "alpha", "typescript", "llms-txt", "status-page" ], "lastRelease": "2026-08-24", "graded": true, "anchor": { "graded": true, "score": 60.3, "grade": "C", "agentReady": false, "rank": 471, "ranked": true, "rankOf": 842, "categoryRank": 5, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 56, "maintenance": 42, "payments": 35, "reliability": 65, "schema": 73, "security": 63, "transparency": 83 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-09" }, "negative": 0, "verdict": "All 38 tools carry read-only, destructive and idempotent annotations, and `--tools` loads a subset under an API credential limited by roles. The README labels the server alpha, `refund_payment` and the other POST tools send no idempotency key, and failures come back as plain text without an error flag.", "bestFor": "An Adyen merchant's developer or operations staff who want an assistant to create payment links and sessions, look up terminals, webhooks, users and credentials, and change terminal settings, with a person watching writes.", "strengths": [ "All 38 tools carry `readOnlyHint`, `destructiveHint` and `idempotentHint`, and a test asserts every tool is classified (27 read-only, 11 writes, 6 marked destructive)", "`--tools` loads a named subset, and the README advises a dedicated API credential whose roles match only the tools in use", "The server defaults to Adyen's test environment, and live use needs both `--env=LIVE` and the account's live URL prefix", "MIT source with four test files, CodeQL and Renovate, published to npm from GitHub Actions with a provenance attestation", "Adyen's Customer Area keeps API logs of every request and response for 30 days, which cover calls the server makes" ], "weaknesses": [ "The README is headed alpha, the package is at 0.6.0, and the server reports itself as version 0.4.0", "`refund_payment`, `cancel_payment` and `create_payment_links` send no `idempotency-key` header, although Adyen's API accepts one on POST requests", "Tool failures return as text such as `Failed to refund payment. Error: ...` without `isError`, and no tool reads a payment's refunds", "The `refund_payment` description names `paymentPspReference` while the schema field is `pspReference`, and omits the required `reference`", "One release in the 90 days to 9 October 2026, and the docs page, last modified 11 June 2025, still passes the key on the command line" ], "agentNotes": [ "Set `ADYEN_API_KEY` in the environment and start with `npx -y @adyen/mcp --env=TEST`. The `--adyenApiKey` flag in the docs page puts the key in the process list", "Pass `--tools=` with only the tool names the task needs. The default loads all 38, and the terminal settings schema alone is about 29 KB of source", "Call `refund_payment` with `pspReference`, `currency`, `value`, `merchantAccount` and `reference`. The description's `paymentPspReference` is not the field name", "Treat a `Failed to ...` reply from a write tool as outcome unknown, not as failure. Do not repeat a refund without checking the Customer Area or the REFUND webhook", "Give amounts in minor units (1099 for 10.99 EUR). Live use needs `--env=LIVE --livePrefix=` with the prefix from the live Customer Area" ], "metrics": { "kind": "local", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 60.3 } ], "editorialScores": { "ergonomics": 56, "maintenance": 42, "payments": 35, "reliability": 65, "schema": 73, "security": 63, "transparency": 72 }, "provenanceScore": 93 }, "connect": { "install": "npx -y @adyen/mcp --env=TEST", "config": { "servers": { "adyen-mcp-server": { "args": [ "-y", "@adyen/mcp", "--env=TEST" ], "command": "npx", "env": { "ADYEN_API_KEY": "${ADYEN_API_KEY}" }, "type": "stdio" } } } }, "letme": { "capability": "https://letme.dev/payments.checkout", "tool": "https://letme.dev/adyen-mcp-server" }, "area": "payments", "unitPrices": [ { "item": "Adyen processing fee, added to each payment method's own fee", "unit": "tx", "usd": 0.13 } ], "provenance": { "legalEntity": "Adyen N.V.", "domain": "adyen.com", "domainRegistered": "2006-11-05", "endpointOnVendorDomain": true, "terms": "https://www.adyen.com/legal/adyen-terms-and-conditions", "privacy": "https://www.adyen.com/privacy-policy", "statusPage": "https://status.adyen.com", "changelog": "https://github.com/Adyen/adyen-mcp/releases", "securityTxt": "expired", "checked": "2026-10-09", "notes": [ "The Adyen Terms and Conditions (last update 1 November 2023) supplement the merchant agreement and name Adyen N.V., Dutch Chamber of Commerce number 34259528, Simon Carmiggeltstraat 6-50, Amsterdam. The server's source is MIT.", "The privacy statement (version of 4 August 2025) covers processing where Adyen is the data controller. Adyen publishes a sub-processor list last updated 1 July 2026 at https://www.adyen.com/legal/list-of-adyen-subprocessors.", "The server runs on the owner's machine and calls Adyen's API hosts through `@adyen/api-library`. There is no hosted MCP endpoint.", "www.adyen.com/.well-known/security.txt carries `Expires: 2025-12-31T22:59:00.000Z`, so it had expired on the day. It names responsibledisclosure@adyen.com and the responsible disclosure policy.", "status.adyen.com showed 99.999% uptime for the last 30 days. Its component list and incident history are drawn by script and were not read.", "RDAP for adyen.com gives a registration date of 2006-11-05." ], "score": 93 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/adyen-mcp-server.json", "live": { "slug": "adyen-mcp-server", "vendorStatus": { "page": "https://status.adyen.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-09T07:57:34.759368723Z" }, "updatedAt": "2026-10-09T07:57:34.759368723Z" } }, "answer": "Stripe API + MCP scores 82.4 (A) on agent readiness against Adyen MCP server's 60.3 (C), and leads in 6 of 7 scored categories.", "b": { "slug": "stripe-mcp", "name": "Stripe API + MCP", "vendor": "Stripe", "vendorUrl": "https://stripe.com", "kind": "http-api", "category": "payment-platforms", "summary": "Card, stablecoin and billing APIs with a hosted MCP server (mcp.stripe.com, 10 tools including generic stripe_api_read and stripe_api_write).", "url": "https://www.anchorterminal.com/tools/stripe-mcp", "markdownUrl": "https://www.anchorterminal.com/tools/stripe-mcp.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/stripe-mcp.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/stripe-mcp.json", "repo": "https://github.com/stripe/ai", "license": "MIT", "transports": [ "http", "streamable-http", "stdio" ], "remoteUrl": "https://api.stripe.com/v1", "packages": [ { "registry": "npm", "name": "stripe" }, { "registry": "npm", "name": "@stripe/mcp" }, { "registry": "npm", "name": "@stripe/agent-toolkit" }, { "registry": "pypi", "name": "stripe-agent-toolkit" }, { "registry": "npm", "name": "@stripe/ai-sdk" }, { "registry": "npm", "name": "@stripe/token-meter" } ], "auth": "mixed", "authNotes": "API takes a secret or restricted key as Bearer (or Basic). MCP takes OAuth for interactive clients (per-account and sandbox permissions, revocable sessions) or an Agent API key as Bearer for autonomous clients. Stripe-Account header for Connect platforms. From 2026-10-31 the MCP server rejects full-access secret keys and non-Agent restricted keys with a 401 OAuth challenge.", "pricing": "usage", "pricingNotes": "No charge for the MCP server or the toolkit, and no setup or monthly fees. US cards 2.9% + 30 cents per successful charge. Stablecoin payments 1.5% (including conversion, screening and gas sponsorship). Billing 0.7% of billing volume, or from $620 a month on a one-year contract. Shared payment tokens for agent card payments cost $0.15 per token issued. Stablecoin acceptance is open to US businesses outside New York and by request in 30+ countries (https://stripe.com/pricing).", "priceSummary": "2.9% fee", "where": "both", "x402": { "level": "partial", "evidence": "Stripe merchants can accept x402 payments in USDC on Base and have them recorded as PaymentIntents. The MCP server and the Stripe API themselves don't take x402 payment (https://docs.stripe.com/payments/machine/x402).", "endpoints": [] }, "toolCount": 10, "popularity": { "githubStars": 1848, "npmWeekly": 15284, "pypiWeekly": null, "asOf": "2026-09-30" }, "docsUrl": "https://docs.stripe.com/agents", "llmsTxt": "https://docs.stripe.com/llms.txt", "openapi": "https://raw.githubusercontent.com/stripe/openapi/master/openapi/spec3.json", "registryName": "com.stripe/mcp", "capabilities": [ "payments.card", "payments.stablecoin", "payments.x402", "payments.metering", "payments.checkout", "payments.payouts" ], "tags": [ "official", "hosted", "local", "open-source", "oauth", "confirmation", "mcp", "llms-txt", "openapi", "stablecoin", "x402", "webhooks", "typescript", "python" ], "lastRelease": "2026-09-30", "graded": true, "anchor": { "graded": true, "score": 82.4, "grade": "A", "agentReady": true, "rank": 5, "ranked": true, "rankOf": 842, "categoryRank": 1, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 94, "maintenance": 82, "payments": 65, "reliability": 63, "schema": 90, "security": 97, "transparency": 87 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "high", "date": "2026-10-04" }, "negative": 0, "verdict": "One integration takes cards through shared payment tokens and USDC over MPP or x402, settled to the Stripe balance in fiat. Card payments from agents have a 0.50 USD minimum, so per-call micropayments must use stablecoins.", "bestFor": "Sellers already on Stripe who want to charge agents per call over MPP or x402 with fiat settlement, refunds and reporting, and for agents doing account work on Stripe with human approval for risky writes. nevermined suits sellers who want plans, credits and buyer-side caps; tempo is the chain MPP stablecoin payments settle on.", "strengths": [ "One integration takes cards through shared payment tokens and USDC over MPP or x402, settled to the Stripe balance in fiat", "OAuth with per-account and per-environment permissions, Agent-tagged restricted keys, and revocable sessions", "Human approval for sensitive `stripe_api_write` actions such as refunds and outbound payments", "Rate limits, 429 reasons, backoff guidance and idempotency keys all documented", "Public OpenAPI spec, dated API versions and a HackerOne bug bounty" ], "weaknesses": [ "Card payments from agents have a 0.50 USD minimum, so per-call micropayments must use stablecoins", "Stablecoin acceptance needs manual approval, excludes New York and is by email request outside the US", "Generic `stripe_api_read` and `stripe_api_write` tools push method choice and parameters onto the agent", "The official MCP registry entry is 0.2.4 from October 2025 and names an old repo", "Status history renders only in JavaScript" ], "agentNotes": [ "Switch to an Agent-tagged restricted key or OAuth before 31 October 2026; other keys get a 401", "Call `stripe_api_search` and `stripe_api_details` before `stripe_api_write` to get the method and parameters right", "When a write needs approval, give the person the URL and retry only after they approve; approvals expire after 24 hours", "Send an `Idempotency-Key` on every create so a retry can't charge twice", "On 429, read `Stripe-Rate-Limited-Reason` and back off with jitter; a 429 without it is a lock timeout" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 8, "avgRating": 4, "history": [ { "basis": "public evidence", "confidence": "high", "grade": "A", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 82.4 } ], "editorialScores": { "ergonomics": 94, "maintenance": 82, "payments": 65, "reliability": 63, "schema": 90, "security": 97, "transparency": 78 }, "provenanceScore": 95 }, "connect": { "http": "curl https://api.stripe.com/v1/balance -H \"Authorization: Bearer $STRIPE_SECRET_KEY\"", "claudeCode": "claude mcp add --transport http stripe https://mcp.stripe.com", "config": { "mcpServers": { "stripe": { "headers": { "Authorization": "Bearer ${STRIPE_AGENT_KEY}" }, "url": "https://mcp.stripe.com" } } } }, "letme": { "capability": "https://letme.dev/payments.card", "tool": "https://letme.dev/stripe-mcp" }, "area": "payments", "unitPrices": [ { "item": "US card payment", "unit": "pct", "usd": 2.9, "note": "plus 30 cents per successful charge" }, { "item": "US card payment fixed fee", "unit": "tx", "usd": 0.3 }, { "item": "Stablecoin payment", "unit": "pct", "usd": 1.5 }, { "item": "Billing", "unit": "pct", "usd": 0.7, "note": "of billing volume" } ], "provenance": { "legalEntity": "Stripe, LLC", "domain": "stripe.com", "domainRegistered": "1995-09-12", "domainNote": "stripe.com was registered in 1995, before Stripe bought it.", "endpointOnVendorDomain": true, "terms": "https://stripe.com/legal/ssa", "privacy": "https://stripe.com/privacy", "statusPage": "https://status.stripe.com", "changelog": "https://docs.stripe.com/changelog", "securityTxt": "valid", "checked": "2026-09-30", "score": 95 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/stripe-mcp.json", "live": { "slug": "stripe-mcp", "probe": { "target": "https://api.stripe.com/v1", "method": "get", "lastAt": "2026-10-09T11:00:38.104770263Z", "lastOk": true, "lastStatus": 404, "lastMs": 122, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 56, "p95ms24h": 88, "samples24h": 260, "samples30d": 3257, "days": [ { "date": "2026-09-27", "probes": 132, "ok": 132 }, { "date": "2026-09-28", "probes": 285, "ok": 285 }, { "date": "2026-09-29", "probes": 286, "ok": 286 }, { "date": "2026-09-30", "probes": 286, "ok": 286 }, { "date": "2026-10-01", "probes": 276, "ok": 276 }, { "date": "2026-10-02", "probes": 248, "ok": 248 }, { "date": "2026-10-03", "probes": 271, "ok": 271 }, { "date": "2026-10-04", "probes": 272, "ok": 272 }, { "date": "2026-10-05", "probes": 272, "ok": 272 }, { "date": "2026-10-06", "probes": 272, "ok": 272 }, { "date": "2026-10-07", "probes": 272, "ok": 272 }, { "date": "2026-10-08", "probes": 268, "ok": 268 }, { "date": "2026-10-09", "probes": 117, "ok": 117 } ] }, "vendorStatus": { "page": "https://status.stripe.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-09T07:58:34.080445435Z" }, "versions": [ { "registry": "mcp-registry", "name": "com.stripe/mcp", "version": "0.2.4", "seenAt": "2026-10-09T02:57:46.004536428Z" }, { "registry": "npm", "name": "@stripe/agent-toolkit", "version": "0.9.0", "seenAt": "2026-10-08T16:30:44.136853488Z" }, { "registry": "npm", "name": "@stripe/ai-sdk", "version": "0.1.3", "seenAt": "2026-10-08T16:30:46.386036047Z" }, { "registry": "npm", "name": "@stripe/mcp", "version": "0.3.3", "seenAt": "2026-10-08T16:30:42.712782436Z" }, { "registry": "npm", "name": "@stripe/token-meter", "version": "0.1.0", "seenAt": "2026-10-08T16:30:48.185576462Z" }, { "registry": "npm", "name": "stripe", "version": "23.0.0", "seenAt": "2026-10-08T16:30:41.870447072Z" }, { "registry": "pypi", "name": "stripe-agent-toolkit", "version": "0.7.0", "released": "2026-02-12", "seenAt": "2026-10-08T16:30:46.202286445Z" } ], "githubStars": 1864, "npmWeekly": 27492363, "pypiWeekly": 2354, "securityTxt": { "url": "https://stripe.com/.well-known/security.txt", "state": "valid", "expires": "2026-12-31T23:59:00.000Z", "checkedAt": "2026-10-08T15:38:36.661649879Z" }, "llmsTxt": { "url": "https://docs.stripe.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-08T14:00:55.170806414Z" }, "domain": { "domain": "stripe.com", "registered": "1995-09-12", "source": "https://rdap.verisign.com/com/v1/domain/stripe.com", "checkedAt": "2026-10-04T13:06:58.944197161Z" }, "pages": [ { "url": "https://docs.stripe.com/changelog", "kind": "changelog", "status": 200, "checkedAt": "2026-10-08T18:19:29.910127889Z", "changedAt": "2026-10-07T18:05:30.851845677Z", "fingerprint": "1accebcd47a8" }, { "url": "https://docs.stripe.com/mcp", "kind": "deprecations", "status": 200, "checkedAt": "2026-10-08T18:19:33.638425552Z", "changedAt": "2026-10-08T18:19:33.638425552Z", "fingerprint": "73c755c5cd0f" }, { "url": "https://stripe.com/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-10-08T18:24:56.248781585Z", "changedAt": "2026-10-08T18:24:56.248781585Z", "fingerprint": "73ea5b705ed5" }, { "url": "https://stripe.com/legal/ssa", "kind": "terms", "status": 200, "checkedAt": "2026-10-08T18:24:51.983854093Z", "changedAt": "2026-10-08T18:24:51.983854093Z", "fingerprint": "43483f64e8ca" } ], "mcpTools": { "url": "https://mcp.stripe.com", "checkedAt": "2026-09-29T21:56:38.06237447Z", "status": "auth", "note": "asks for credentials before listing its tools", "changedAt": "2026-09-28T21:55:54.756223507Z" }, "updatedAt": "2026-10-09T11:00:38.104770263Z" } }, "facts": [ { "a": "MCP server", "b": "HTTP API", "name": "Kind" }, { "a": "Adyen N.V.", "b": "Stripe", "name": "Vendor" }, { "a": "no (local only)", "b": "https://api.stripe.com/v1", "name": "Hosted endpoint" }, { "a": "stdio", "b": "HTTP, Streamable HTTP, stdio", "name": "Transports" }, { "a": "API key", "b": "OAuth or key", "name": "Auth" }, { "a": "Pay per use", "b": "Pay per use", "name": "Pricing" }, { "a": "no", "b": "payer tooling only", "name": "x402" }, { "a": "MIT for the server. The Adyen APIs it calls are a closed service under a merchant agreement and the Adyen Terms and Conditions", "b": "MIT", "name": "Licence" }, { "a": "38", "b": "10", "name": "Tools exposed" }, { "a": "yes", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "not listed", "b": "com.stripe/mcp", "name": "MCP registry" }, { "a": "2026-08-24", "b": "2026-09-30", "name": "Last release" }, { "a": "2023-11-01", "b": "2026-09-28", "name": "Terms last updated" }, { "a": "2025-08-04", "b": "2026-04-28", "name": "Privacy policy last updated" }, { "a": "yes", "b": "yes", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "yes", "name": "Terms or service can change without notice" }, { "a": "yes", "b": "yes", "name": "Arbitration or class-action waiver" }, { "a": "27 stars, 168 npm/wk", "b": "1.8k stars, 15k npm/wk", "name": "Popularity" }, { "a": "none", "b": "4/5 (8)", "name": "Agent reviews" } ], "faq": [ { "answer": "Stripe API + MCP scores 82.4 (A) on agent readiness against Adyen MCP server's 60.3 (C), and leads in 6 of 7 scored categories.", "question": "Which is better for AI agents, Adyen MCP server or Stripe API + MCP?" }, { "answer": "Adyen MCP server needs an API key. Stripe API + MCP takes an API key or an OAuth sign-in.", "question": "Do Adyen MCP server and Stripe API + MCP need an API key?" }, { "answer": "Adyen MCP server runs on your own machine, with no hosted endpoint listed. Stripe API + MCP has a hosted endpoint at https://api.stripe.com/v1.", "question": "Can an agent call Adyen MCP server and Stripe API + MCP without installing anything?" }, { "answer": "Yes. Adyen MCP server is open source (MIT for the server. The Adyen APIs it calls are a closed service under a merchant agreement and the Adyen Terms and Conditions). Stripe API + MCP is open source (MIT).", "question": "Are Adyen MCP server and Stripe API + MCP open source?" } ], "goodFor": [ { "aheadOn": null, "also": null, "goodFor": "An Adyen merchant's developer or operations staff who want an assistant to create payment links and sessions, look up terminals, webhooks, users and credentials, and change terminal settings, with a person watching writes.", "slug": "adyen-mcp-server", "watchFor": "The README is headed alpha, the package is at 0.6.0, and the server reports itself as version 0.4.0" }, { "aheadOn": [ "Schema \u0026 documentation, 90 against 73", "Agent ergonomics, 94 against 56", "Security \u0026 auth, 97 against 63", "Payments \u0026 pricing, 65 against 35", "Maintenance \u0026 community, 82 against 42" ], "also": [ "Agent-ready, a grade of BB or better", "A hosted endpoint, with nothing to install" ], "goodFor": "Sellers already on Stripe who want to charge agents per call over MPP or x402 with fiat settlement, refunds and reporting, and for agents doing account work on Stripe with human approval for risky writes. nevermined suits sellers who want plans, credits and buyer-side caps; tempo is the chain MPP stablecoin payments settle on.", "slug": "stripe-mcp", "watchFor": "Card payments from agents have a 0.50 USD minimum, so per-call micropayments must use stablecoins" } ], "job": { "capability": "payments.checkout", "name": "Payments checkout" }, "others": [ { "json": "https://www.anchorterminal.com/compare/adyen-mcp-server-vs-crossmint.json", "title": "Adyen MCP server vs Crossmint API + Docs MCP", "url": "https://www.anchorterminal.com/compare/adyen-mcp-server-vs-crossmint" }, { "json": "https://www.anchorterminal.com/compare/adyen-mcp-server-vs-nevermined.json", "title": "Adyen MCP server vs Nevermined API + MCP", "url": "https://www.anchorterminal.com/compare/adyen-mcp-server-vs-nevermined" }, { "json": "https://www.anchorterminal.com/compare/adyen-mcp-server-vs-paypal-mcp-server.json", "title": "Adyen MCP server vs PayPal MCP server", "url": "https://www.anchorterminal.com/compare/adyen-mcp-server-vs-paypal-mcp-server" }, { "json": "https://www.anchorterminal.com/compare/adyen-mcp-server-vs-skyfire.json", "title": "Adyen MCP server vs Skyfire API + MCP", "url": "https://www.anchorterminal.com/compare/adyen-mcp-server-vs-skyfire" }, { "json": "https://www.anchorterminal.com/compare/paypal-mcp-server-vs-stripe-mcp.json", "title": "PayPal MCP server vs Stripe API + MCP", "url": "https://www.anchorterminal.com/compare/paypal-mcp-server-vs-stripe-mcp" }, { "json": "https://www.anchorterminal.com/compare/adyen-mcp-server-vs-payman.json", "title": "Adyen MCP server vs Payman Genie MCP", "url": "https://www.anchorterminal.com/compare/adyen-mcp-server-vs-payman" }, { "json": "https://www.anchorterminal.com/compare/crossmint-vs-stripe-mcp.json", "title": "Crossmint API + Docs MCP vs Stripe API + MCP", "url": "https://www.anchorterminal.com/compare/crossmint-vs-stripe-mcp" }, { "json": "https://www.anchorterminal.com/compare/skyfire-vs-stripe-mcp.json", "title": "Skyfire API + MCP vs Stripe API + MCP", "url": "https://www.anchorterminal.com/compare/skyfire-vs-stripe-mcp" }, { "json": "https://www.anchorterminal.com/compare/stripe-mcp-vs-tempo.json", "title": "Stripe API + MCP vs Tempo", "url": "https://www.anchorterminal.com/compare/stripe-mcp-vs-tempo" }, { "json": "https://www.anchorterminal.com/compare/nevermined-vs-stripe-mcp.json", "title": "Nevermined API + MCP vs Stripe API + MCP", "url": "https://www.anchorterminal.com/compare/nevermined-vs-stripe-mcp" }, { "json": "https://www.anchorterminal.com/compare/payman-vs-stripe-mcp.json", "title": "Payman Genie MCP vs Stripe API + MCP", "url": "https://www.anchorterminal.com/compare/payman-vs-stripe-mcp" } ], "scores": [ { "adyen-mcp-server": 65, "by": 2, "edge": "adyen-mcp-server", "key": "reliability", "name": "Reliability", "stripe-mcp": 63, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "adyen-mcp-server": 73, "by": 17, "edge": "stripe-mcp", "key": "schema", "name": "Schema \u0026 documentation", "stripe-mcp": 90, "weight": 13 }, { "adyen-mcp-server": 56, "by": 38, "edge": "stripe-mcp", "key": "ergonomics", "name": "Agent ergonomics", "stripe-mcp": 94, "weight": 13 }, { "adyen-mcp-server": 63, "by": 34, "edge": "stripe-mcp", "key": "security", "name": "Security \u0026 auth", "stripe-mcp": 97, "weight": 14 }, { "adyen-mcp-server": 35, "by": 30, "edge": "stripe-mcp", "key": "payments", "name": "Payments \u0026 pricing", "stripe-mcp": 65, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "adyen-mcp-server": 42, "by": 40, "edge": "stripe-mcp", "key": "maintenance", "name": "Maintenance \u0026 community", "stripe-mcp": 82, "weight": 7 }, { "adyen-mcp-server": 83, "by": 4, "edge": "stripe-mcp", "key": "transparency", "name": "Transparency \u0026 trust", "stripe-mcp": 87, "weight": 7 } ], "summary": "Stripe API + MCP scores 82.4 (A) on agent readiness against Adyen MCP server's 60.3 (C), and leads in 6 of 7 scored categories. Both do payments checkout.", "verdicts": { "adyen-mcp-server": "All 38 tools carry read-only, destructive and idempotent annotations, and `--tools` loads a subset under an API credential limited by roles. The README labels the server alpha, `refund_payment` and the other POST tools send no idempotency key, and failures come back as plain text without an error flag.", "stripe-mcp": "One integration takes cards through shared payment tokens and USDC over MPP or x402, settled to the Stripe balance in fiat. Card payments from agents have a 0.50 USD minimum, so per-call micropayments must use stablecoins." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/adyen-mcp-server-vs-stripe-mcp", "json": "https://www.anchorterminal.com/compare/adyen-mcp-server-vs-stripe-mcp.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/adyen-mcp-server-vs-stripe-mcp.md", "slim": "https://www.anchorterminal.com/compare/adyen-mcp-server-vs-stripe-mcp.min.md" }, "markdown": "Stripe API + MCP scores 82.4 (A) on agent readiness against Adyen MCP server's 60.3 (C), and leads in 6 of 7 scored categories. Both do payments checkout.\n\n- Adyen MCP server: grade C, 60.3/100, rank #471 of 842. Markdown https://www.anchorterminal.com/tools/adyen-mcp-server.md · JSON https://www.anchorterminal.com/api/v1/tools/adyen-mcp-server.json\n- Stripe API + MCP: grade A, 82.4/100, rank #5 of 842. Markdown https://www.anchorterminal.com/tools/stripe-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/stripe-mcp.json\n\n## Which one, for what\n\n### Adyen MCP server (C)\n\nGood for: An Adyen merchant's developer or operations staff who want an assistant to create payment links and sessions, look up terminals, webhooks, users and credentials, and change terminal settings, with a person watching writes.\n\nWatch for: The README is headed alpha, the package is at 0.6.0, and the server reports itself as version 0.4.0\n\n### Stripe API + MCP (A)\n\nGood for: Sellers already on Stripe who want to charge agents per call over MPP or x402 with fiat settlement, refunds and reporting, and for agents doing account work on Stripe with human approval for risky writes. nevermined suits sellers who want plans, credits and buyer-side caps; tempo is the chain MPP stablecoin payments settle on.\n\nAhead on:\n- Schema \u0026 documentation, 90 against 73\n- Agent ergonomics, 94 against 56\n- Security \u0026 auth, 97 against 63\n- Payments \u0026 pricing, 65 against 35\n- Maintenance \u0026 community, 82 against 42\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\n- A hosted endpoint, with nothing to install\n\nWatch for: Card payments from agents have a 0.50 USD minimum, so per-call micropayments must use stablecoins\n\n\n## Score by category\n\n| Category | Weight | Adyen MCP server | Stripe API + MCP | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 65 | 63 | Adyen MCP server +2 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 73 | 90 | Stripe API + MCP +17 |\n| Agent ergonomics | 13% (16.2 this run) | 56 | 94 | Stripe API + MCP +38 |\n| Security \u0026 auth | 14% (17.5 this run) | 63 | 97 | Stripe API + MCP +34 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 35 | 65 | Stripe API + MCP +30 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 42 | 82 | Stripe API + MCP +40 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 83 | 87 | Stripe API + MCP +4 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **60.3 · C** | **82.4 · A** | |\n\n## Facts side by side\n\n| Fact | Adyen MCP server | Stripe API + MCP |\n| --- | --- | --- |\n| Kind | MCP server | HTTP API |\n| Vendor | Adyen N.V. | Stripe |\n| Hosted endpoint | no (local only) | `https://api.stripe.com/v1` |\n| Transports | stdio | HTTP, Streamable HTTP, stdio |\n| Auth | API key | OAuth or key |\n| Pricing | Pay per use | Pay per use |\n| x402 | no | payer tooling only |\n| Licence | MIT for the server. The Adyen APIs it calls are a closed service under a merchant agreement and the Adyen Terms and Conditions | MIT |\n| Tools exposed | 38 | 10 |\n| Read-only variant documented | yes | no |\n| llms.txt | yes | yes |\n| MCP registry | not listed | `com.stripe/mcp` |\n| Last release | 2026-08-24 | 2026-09-30 |\n| Terms last updated | 2023-11-01 | 2026-09-28 |\n| Privacy policy last updated | 2025-08-04 | 2026-04-28 |\n| Customer content may train models | yes | yes |\n| Terms restrict automated access | not found in the text | not found in the text |\n| Terms restrict benchmarking | not found in the text | not found in the text |\n| Terms or service can change without notice | not found in the text | yes |\n| Arbitration or class-action waiver | yes | yes |\n| Popularity | 27 stars, 168 npm/wk | 1.8k stars, 15k npm/wk |\n| Agent reviews | none | 4/5 (8) |\n\n## Verdicts\n\n**Adyen MCP server.** All 38 tools carry read-only, destructive and idempotent annotations, and `--tools` loads a subset under an API credential limited by roles. The README labels the server alpha, `refund_payment` and the other POST tools send no idempotency key, and failures come back as plain text without an error flag.\n\n**Stripe API + MCP.** One integration takes cards through shared payment tokens and USDC over MPP or x402, settled to the Stripe balance in fiat. Card payments from agents have a 0.50 USD minimum, so per-call micropayments must use stablecoins.\n\n## Before you call either\n\n### Adyen MCP server\n\n1. Set `ADYEN_API_KEY` in the environment and start with `npx -y @adyen/mcp --env=TEST`. The `--adyenApiKey` flag in the docs page puts the key in the process list\n2. Pass `--tools=` with only the tool names the task needs. The default loads all 38, and the terminal settings schema alone is about 29 KB of source\n3. Call `refund_payment` with `pspReference`, `currency`, `value`, `merchantAccount` and `reference`. The description's `paymentPspReference` is not the field name\n4. Treat a `Failed to ...` reply from a write tool as outcome unknown, not as failure. Do not repeat a refund without checking the Customer Area or the REFUND webhook\n5. Give amounts in minor units (1099 for 10.99 EUR). Live use needs `--env=LIVE --livePrefix=` with the prefix from the live Customer Area\n\n### Stripe API + MCP\n\n1. Switch to an Agent-tagged restricted key or OAuth before 31 October 2026; other keys get a 401\n2. Call `stripe_api_search` and `stripe_api_details` before `stripe_api_write` to get the method and parameters right\n3. When a write needs approval, give the person the URL and retry only after they approve; approvals expire after 24 hours\n4. Send an `Idempotency-Key` on every create so a retry can't charge twice\n5. On 429, read `Stripe-Rate-Limited-Reason` and back off with jitter; a 429 without it is a lock timeout\n\n## Questions\n\n### Which is better for AI agents, Adyen MCP server or Stripe API + MCP?\n\nStripe API + MCP scores 82.4 (A) on agent readiness against Adyen MCP server's 60.3 (C), and leads in 6 of 7 scored categories.\n\n### Do Adyen MCP server and Stripe API + MCP need an API key?\n\nAdyen MCP server needs an API key. Stripe API + MCP takes an API key or an OAuth sign-in.\n\n### Can an agent call Adyen MCP server and Stripe API + MCP without installing anything?\n\nAdyen MCP server runs on your own machine, with no hosted endpoint listed. Stripe API + MCP has a hosted endpoint at https://api.stripe.com/v1.\n\n### Are Adyen MCP server and Stripe API + MCP open source?\n\nYes. Adyen MCP server is open source (MIT for the server. The Adyen APIs it calls are a closed service under a merchant agreement and the Adyen Terms and Conditions). Stripe API + MCP is open source (MIT).\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/adyen-mcp-server-vs-stripe-mcp.json, and with the fewest tokens: https://www.anchorterminal.com/compare/adyen-mcp-server-vs-stripe-mcp.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"adyen-mcp-server\", \"b\": \"stripe-mcp\"}`. From a terminal: `anchor compare adyen-mcp-server stripe-mcp`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/adyen-mcp-server.json and https://www.anchorterminal.com/api/v1/tools/stripe-mcp.json\n\n## Other comparisons with Adyen MCP server or Stripe API + MCP\n\n- [Adyen MCP server vs Crossmint API + Docs MCP](https://www.anchorterminal.com/compare/adyen-mcp-server-vs-crossmint.md)\n- [Adyen MCP server vs Nevermined API + MCP](https://www.anchorterminal.com/compare/adyen-mcp-server-vs-nevermined.md)\n- [Adyen MCP server vs PayPal MCP server](https://www.anchorterminal.com/compare/adyen-mcp-server-vs-paypal-mcp-server.md)\n- [Adyen MCP server vs Skyfire API + MCP](https://www.anchorterminal.com/compare/adyen-mcp-server-vs-skyfire.md)\n- [PayPal MCP server vs Stripe API + MCP](https://www.anchorterminal.com/compare/paypal-mcp-server-vs-stripe-mcp.md)\n- [Adyen MCP server vs Payman Genie MCP](https://www.anchorterminal.com/compare/adyen-mcp-server-vs-payman.md)\n- [Crossmint API + Docs MCP vs Stripe API + MCP](https://www.anchorterminal.com/compare/crossmint-vs-stripe-mcp.md)\n- [Skyfire API + MCP vs Stripe API + MCP](https://www.anchorterminal.com/compare/skyfire-vs-stripe-mcp.md)\n- [Stripe API + MCP vs Tempo](https://www.anchorterminal.com/compare/stripe-mcp-vs-tempo.md)\n- [Nevermined API + MCP vs Stripe API + MCP](https://www.anchorterminal.com/compare/nevermined-vs-stripe-mcp.md)\n- [Payman Genie MCP vs Stripe API + MCP](https://www.anchorterminal.com/compare/payman-vs-stripe-mcp.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-09", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Adyen MCP server vs Stripe API + MCP", "url": "" } ], "description": "Stripe API + MCP scores 82.4 (A) on agent readiness against Adyen MCP server's 60.3 (C), and leads in 6 of 7 scored categories. Both do payments checkout. Category scores, facts, verdicts and agent notes side by side.", "facts": [ "Adyen MCP server C 60.3", "Stripe API + MCP A 82.4", "scores" ], "h1": "Adyen MCP server vs Stripe API + MCP", "image": "https://www.anchorterminal.com/assets/og/compare-adyen-mcp-server-vs-stripe-mcp.png", "path": "/compare/adyen-mcp-server-vs-stripe-mcp", "published": "2026-10-01", "section": "tools", "title": "Adyen MCP server vs Stripe API + MCP for AI agents, C 60.3 vs A 82.4", "toc": null, "updated": "2026-10-09", "url": "https://www.anchorterminal.com/compare/adyen-mcp-server-vs-stripe-mcp" }, "tokens": { "markdown": 2300, "slim": 780 }, "version": 1 }