{ "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": 520, "ranked": true, "rankOf": 950, "categoryRank": 9, "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-10T00:50:03.247356481Z" }, "versions": [ { "registry": "github", "name": "Adyen/adyen-mcp", "version": "0.6.0", "released": "2026-08-24", "seenAt": "2026-10-09T16:36:40.43163815Z" }, { "registry": "npm", "name": "@adyen/mcp", "version": "0.6.0", "seenAt": "2026-10-09T16:36:38.520388429Z" } ], "githubStars": 27, "npmWeekly": 230, "securityTxt": { "url": "https://adyen.com/.well-known/security.txt", "state": "expired", "expires": "2025-12-31T22:59:00.000Z", "checkedAt": "2026-10-09T15:39:45.357872494Z" }, "llmsTxt": { "url": "https://docs.adyen.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-09T14:01:06.187072024Z" }, "pages": [ { "url": "https://www.adyen.com/privacy-policy", "kind": "privacy", "status": 200, "checkedAt": "2026-10-09T18:47:43.281034945Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "8c4fb9788099" }, { "url": "https://www.adyen.com/legal/adyen-terms-and-conditions", "kind": "terms", "status": 200, "checkedAt": "2026-10-09T18:47:41.16986984Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "91266ad1ad0d" } ], "updatedAt": "2026-10-10T00:50:03.247356481Z" } }, "answer": "Lago scores 65.7 (B) on agent readiness against Adyen MCP server's 60.3 (C), and leads in 5 of 7 scored categories. Adyen MCP server leads on security \u0026 auth and transparency \u0026 trust.", "b": { "slug": "lago", "name": "Lago", "vendor": "Get Lago Corp.", "vendorUrl": "https://getlago.com", "kind": "http-api", "category": "payment-platforms", "summary": "Lago is open-source billing software from Get Lago Corp. for usage metering, subscriptions, prepaid credits and invoicing. It is self-hosted under AGPL-3.0 or bought as Lago Cloud, and driven through a REST API, SDKs, a CLI and an MCP server.", "url": "https://www.anchorterminal.com/tools/lago", "markdownUrl": "https://www.anchorterminal.com/tools/lago.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/lago.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/lago.json", "repo": "https://github.com/getlago/lago", "license": "AGPL-3.0 (platform). The MCP server and agent SDKs are MIT. Premium capabilities and Lago Cloud are commercial", "transports": [ "http" ], "packages": [ { "registry": "oci", "name": "getlago/lago" }, { "registry": "pypi", "name": "lago-python-client" }, { "registry": "npm", "name": "lago-javascript-client" }, { "registry": "go", "name": "github.com/getlago/lago-go-client" } ], "auth": "api-key", "authNotes": "The REST API takes an organisation API key as a Bearer token. On a self-hosted instance a person signs up in the local UI and copies the key from the Developers section, or the Compose files create the organisation and key from `LAGO_CREATE_ORG` and `LAGO_ORG_API_KEY`. The free edition has one key with full access, which can be rotated. More keys need a Premium licence and per-resource `read`, `write` or `read_write` permissions need an enterprise add-on. No OAuth flow exists.", "pricing": "freemium", "pricingNotes": "The open-source edition is free to self-host under AGPL-3.0, with no card or account. Lago Cloud and Premium self-hosted are sold by custom quote. The pricing summary states a five-figure minimum annual commitment for Cloud and publishes no rate. It also says a Cloud free trial is available, which the docs FAQ contradicts. No sandbox exists, so tests run on a separate instance or organisation (https://getlago.com/pricing.md, checked 2026-10-09).", "priceSummary": "Freemium", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402. Lago's llms.txt says direct x402 and general agent-wallet support are not available. Stripe Shared Payment Token collection is a public preview behind a feature flag (checked 2026-10-09).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 10665, "npmWeekly": 48093, "pypiWeekly": null, "asOf": "2026-10-09" }, "docsUrl": "https://getlago.com/docs/welcome", "llmsTxt": "https://getlago.com/docs/llms.txt", "openapi": "https://swagger.getlago.com/openapi.yaml", "capabilities": [ "payments.metering", "payments.card" ], "tags": [ "open-source", "self-hosted", "agpl", "openapi", "llms-txt", "webhooks", "mcp", "cli", "python", "typescript", "ruby", "go", "docker", "soc2" ], "lastRelease": "2026-10-07", "graded": true, "anchor": { "graded": true, "score": 65.7, "grade": "B", "agentReady": false, "rank": 311, "ranked": true, "rankOf": 950, "categoryRank": 8, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 71, "maintenance": 91, "payments": 50, "reliability": 86, "schema": 87, "security": 37, "transparency": 59 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-09" }, "negative": -3, "negativeNotes": [ "9 October 2026. https://getlago.com/llms.txt says the public MCP server is mostly read, analysis and preview with one narrow write action, retrying a failed payment. The server's source at https://github.com/getlago/lago-agent-toolkit (mcp/src/server.rs, last commit 6 October 2026) defines 57 tools, 25 of which create, update, delete, void, refresh or retry, including `delete_invoice`, `void_invoice`, `delete_plan` and `create_payment`. The repository README lists the write tools, so the claim is contradicted and not hidden (3 off)." ], "verdict": "Lago's open-source edition runs usage metering, plans, wallets and invoicing on the owner's servers at no charge, with an OpenAPI 3.1 file of 217 operations and releases about every two weeks. The free edition has one unscoped API key and no audit logs, and Lago's llms.txt understates what its MCP server can change.", "bestFor": "A team that wants usage metering, plans, wallets and invoicing under its own control and can run PostgreSQL and Redis.", "strengths": [ "The whole platform is AGPL-3.0 and installs from the official `getlago/lago` Docker image or Helm charts, with no software fee", "Public OpenAPI 3.1 description with 217 operations, 339 schemas and 76 webhook events, plus llms.txt, a full-text docs export and Markdown twins", "Six tagged releases between 27 July and 7 October 2026, and the five latest test runs on the API's main branch passed on 8 and 9 October", "Usage events are deduplicated on `transaction_id`, so a retried event is billed once when it is resent unchanged", "Self-hosted analytics are listed event by event and switched off with `LAGO_DISABLE_SEGMENT=true`, which the source confirms" ], "weaknesses": [ "The free edition has one organisation API key with full access. Creating more keys needs a Premium licence and per-resource permissions need an enterprise add-on", "Activity logs are closed to free users, and activity, API and security logs also need ClickHouse", "Lago's llms.txt says the MCP server has one write action. Its source defines 57 tools, 25 of which create, update, delete, void or retry, with no read-only mode", "Lago Cloud and Premium have no public price. The pricing summary states a five-figure minimum annual commitment and a custom quote", "The pricing summary says a Lago Cloud free trial is available, and the docs FAQ says Premium plans have no free trial", "No security.txt, repository security policy or published advisory was found, and the privacy policy does not cover data held in the product" ], "agentNotes": [ "Call `\u003cyour Lago API origin\u003e/api/v1` with `Authorization: Bearer \u003ckey\u003e`. On Lago Cloud the hosts are `api.getlago.com` and `api.eu.getlago.com`", "Send every usage event with a deterministic `transaction_id` and an explicit `timestamp`, and resend the same payload on retry. On the ClickHouse event store a changed timestamp is billed again", "Expect 422 `value_already_exist` for a repeated event on the Postgres event store. Treat it as success for a retry", "Page with `page` and `per_page` and read `meta.next_page` and `meta.total_count`. The default page size is 100 in most cases", "Treat the free edition's API key as full access. It can void invoices and terminate subscriptions, so keep it out of prompts and ask a person before financial changes", "Before giving an assistant the MCP server, note that it includes `delete_invoice`, `void_invoice`, `delete_plan` and `create_payment` and sets no read-only annotations" ], "metrics": { "kind": "local", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 65.7 } ], "editorialScores": { "ergonomics": 71, "maintenance": 91, "payments": 50, "reliability": 86, "schema": 87, "security": 37, "transparency": 77 }, "provenanceScore": 41 }, "connect": { "install": "docker run -d --name lago -p 80:80 -p 3000:3000 getlago/lago:latest", "http": "curl --location --request GET \"$LAGO_URL/api/v1/coupons?page=1\u0026per_page=10\" \\\n --header \"Authorization: Bearer $API_KEY\"", "config": { "mcpServers": { "lago": { "args": [ "run", "--rm", "-i", "--pull=always", "--name", "lago-mcp-server", "-e", "LAGO_API_KEY=your_lago_api_key", "-e", "LAGO_API_URL=your_lago_api_url", "getlago/lago-mcp-server:latest" ], "command": "docker" } } } }, "letme": { "capability": "https://letme.dev/payments.metering", "tool": "https://letme.dev/lago" }, "area": "payments", "provenance": { "legalEntity": "Get Lago Corp.", "domain": "getlago.com", "domainRegistered": "2020-11-27", "endpointOnVendorDomain": false, "terms": "", "privacy": "", "statusPage": "", "changelog": "https://getlago.com/docs/changelog/product", "securityTxt": "none", "checked": "2026-10-09", "notes": [ "The privacy policy and the Lago Cloud terms name Get Lago Corp., 1111B S Governors Ave #7455, Dover, DE 19904, United States, company number 86-3963083.", "No terms link is given because the edition graded is AGPL-3.0 software the owner runs. The Lago Self-Hosted Terms and Conditions (updated 9 March 2024) say they apply to self-hosted Premium plans, and the Lago Cloud terms apply through an order form.", "No privacy link is given. The privacy policy (updated 18 September 2026) covers customers' representatives, suppliers, candidates and site visitors, and does not address data held in a self-hosted instance or the Segment analytics it sends.", "The API answers on the owner's own host. Lago Cloud answers at api.getlago.com and api.eu.getlago.com.", "status.getlago.com, on incident.io, covers the US and EU Lago Cloud clusters only, so no status page is recorded for the graded edition.", "getlago.com/.well-known/security.txt returned 404. The security page gives security@getlago.com.", "RDAP for getlago.com gives a registration date of 2020-11-27 and Gandi SAS as registrar." ], "score": 41 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/lago.json", "live": { "slug": "lago", "versions": [ { "registry": "github", "name": "getlago/lago", "version": "v1.55.0", "released": "2026-10-07", "seenAt": "2026-10-09T17:01:07.029964093Z" }, { "registry": "npm", "name": "lago-javascript-client", "version": "1.55.0", "seenAt": "2026-10-09T17:01:06.180706665Z" }, { "registry": "pypi", "name": "lago-python-client", "version": "1.55.0", "released": "2026-10-07", "seenAt": "2026-10-09T17:01:05.951391418Z" } ], "githubStars": 10667, "npmWeekly": 48093, "pypiWeekly": 4510, "pages": [ { "url": "https://getlago.com/docs/changelog/product", "kind": "changelog", "status": 200, "checkedAt": "2026-10-09T18:39:49.512530703Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "37091c8d6eb7" }, { "url": "https://getlago.com/pricing.md", "kind": "pricing", "status": 200, "checkedAt": "2026-10-09T18:39:51.811950235Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "b4af57318431" } ], "updatedAt": "2026-10-09T18:39:51.811950235Z" } }, "facts": [ { "a": "MCP server", "b": "HTTP API", "name": "Kind" }, { "a": "Adyen N.V.", "b": "Get Lago Corp.", "name": "Vendor" }, { "a": "no (local only)", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "stdio", "b": "HTTP", "name": "Transports" }, { "a": "API key", "b": "API key", "name": "Auth" }, { "a": "Pay per use", "b": "Freemium", "name": "Pricing" }, { "a": "no", "b": "no", "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": "AGPL-3.0 (platform). The MCP server and agent SDKs are MIT. Premium capabilities and Lago Cloud are commercial", "name": "Licence" }, { "a": "38", "b": "none", "name": "Tools exposed" }, { "a": "yes", "b": "yes", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-08-24", "b": "2026-10-07", "name": "Last release" }, { "a": "2023-11-01", "b": "no document linked", "name": "Terms last updated" }, { "a": "2025-08-04", "b": "no document linked", "name": "Privacy policy last updated" }, { "a": "yes", "b": "", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "", "name": "Terms or service can change without notice" }, { "a": "yes", "b": "", "name": "Arbitration or class-action waiver" }, { "a": "27 stars, 168 npm/wk", "b": "11k stars, 48k npm/wk", "name": "Popularity" } ], "faq": [ { "answer": "Lago scores 65.7 (B) on agent readiness against Adyen MCP server's 60.3 (C), and leads in 5 of 7 scored categories. Adyen MCP server leads on security \u0026 auth and transparency \u0026 trust.", "question": "Which is better for AI agents, Adyen MCP server or Lago?" }, { "answer": "Both need an API key.", "question": "Do Adyen MCP server and Lago need an API key?" }, { "answer": "Adyen MCP server runs on your own machine, with no hosted endpoint listed. No hosted endpoint is listed for Lago.", "question": "Can an agent call Adyen MCP server and Lago 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). Lago is open source (AGPL-3.0 (platform). The MCP server and agent SDKs are MIT. Premium capabilities and Lago Cloud are commercial).", "question": "Are Adyen MCP server and Lago open source?" } ], "goodFor": [ { "aheadOn": [ "Security \u0026 auth, 63 against 37", "Transparency \u0026 trust, 83 against 59" ], "also": [ "Runs on your own machine", "No incidents deducted, where Lago loses 3 points for them" ], "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": [ "Reliability, 86 against 65", "Schema \u0026 documentation, 87 against 73", "Agent ergonomics, 71 against 56", "Payments \u0026 pricing, 50 against 35", "Maintenance \u0026 community, 91 against 42" ], "also": null, "goodFor": "A team that wants usage metering, plans, wallets and invoicing under its own control and can run PostgreSQL and Redis.", "slug": "lago", "watchFor": "The free edition has one organisation API key with full access. Creating more keys needs a Premium licence and per-resource permissions need an enterprise add-on" } ], "job": { "capability": "payments.card", "name": "Card payments" }, "others": [ { "json": "https://www.anchorterminal.com/compare/atxp-vs-lago.json", "title": "ATXP vs Lago", "url": "https://www.anchorterminal.com/compare/atxp-vs-lago" }, { "json": "https://www.anchorterminal.com/compare/lago-vs-metronome.json", "title": "Lago vs Metronome", "url": "https://www.anchorterminal.com/compare/lago-vs-metronome" }, { "json": "https://www.anchorterminal.com/compare/lago-vs-nevermined.json", "title": "Lago vs Nevermined API + MCP", "url": "https://www.anchorterminal.com/compare/lago-vs-nevermined" }, { "json": "https://www.anchorterminal.com/compare/lago-vs-orb.json", "title": "Lago vs Orb", "url": "https://www.anchorterminal.com/compare/lago-vs-orb" }, { "json": "https://www.anchorterminal.com/compare/lago-vs-paid.json", "title": "Lago vs Paid", "url": "https://www.anchorterminal.com/compare/lago-vs-paid" }, { "json": "https://www.anchorterminal.com/compare/lago-vs-stripe-mcp.json", "title": "Lago vs Stripe API + MCP", "url": "https://www.anchorterminal.com/compare/lago-vs-stripe-mcp" }, { "json": "https://www.anchorterminal.com/compare/lago-vs-tempo.json", "title": "Lago vs Tempo", "url": "https://www.anchorterminal.com/compare/lago-vs-tempo" }, { "json": "https://www.anchorterminal.com/compare/adyen-mcp-server-vs-atxp.json", "title": "Adyen MCP server vs ATXP", "url": "https://www.anchorterminal.com/compare/adyen-mcp-server-vs-atxp" }, { "json": "https://www.anchorterminal.com/compare/adyen-mcp-server-vs-orb.json", "title": "Adyen MCP server vs Orb", "url": "https://www.anchorterminal.com/compare/adyen-mcp-server-vs-orb" }, { "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-lago.json", "title": "Crossmint API + Docs MCP vs Lago", "url": "https://www.anchorterminal.com/compare/crossmint-vs-lago" }, { "json": "https://www.anchorterminal.com/compare/lago-vs-payman.json", "title": "Lago vs Payman Genie MCP", "url": "https://www.anchorterminal.com/compare/lago-vs-payman" }, { "json": "https://www.anchorterminal.com/compare/lago-vs-skyfire.json", "title": "Lago vs Skyfire API + MCP", "url": "https://www.anchorterminal.com/compare/lago-vs-skyfire" }, { "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-paid.json", "title": "Adyen MCP server vs Paid", "url": "https://www.anchorterminal.com/compare/adyen-mcp-server-vs-paid" }, { "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/adyen-mcp-server-vs-stripe-mcp.json", "title": "Adyen MCP server vs Stripe API + MCP", "url": "https://www.anchorterminal.com/compare/adyen-mcp-server-vs-stripe-mcp" } ], "scores": [ { "adyen-mcp-server": 65, "by": 21, "edge": "lago", "key": "reliability", "lago": 86, "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "adyen-mcp-server": 73, "by": 14, "edge": "lago", "key": "schema", "lago": 87, "name": "Schema \u0026 documentation", "weight": 13 }, { "adyen-mcp-server": 56, "by": 15, "edge": "lago", "key": "ergonomics", "lago": 71, "name": "Agent ergonomics", "weight": 13 }, { "adyen-mcp-server": 63, "by": 26, "edge": "adyen-mcp-server", "key": "security", "lago": 37, "name": "Security \u0026 auth", "weight": 14 }, { "adyen-mcp-server": 35, "by": 15, "edge": "lago", "key": "payments", "lago": 50, "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "adyen-mcp-server": 42, "by": 49, "edge": "lago", "key": "maintenance", "lago": 91, "name": "Maintenance \u0026 community", "weight": 7 }, { "adyen-mcp-server": 83, "by": 24, "edge": "adyen-mcp-server", "key": "transparency", "lago": 59, "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Lago scores 65.7 (B) on agent readiness against Adyen MCP server's 60.3 (C), and leads in 5 of 7 scored categories. Adyen MCP server leads on security \u0026 auth and transparency \u0026 trust. Both do card payments.", "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.", "lago": "Lago's open-source edition runs usage metering, plans, wallets and invoicing on the owner's servers at no charge, with an OpenAPI 3.1 file of 217 operations and releases about every two weeks. The free edition has one unscoped API key and no audit logs, and Lago's llms.txt understates what its MCP server can change." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/adyen-mcp-server-vs-lago", "json": "https://www.anchorterminal.com/compare/adyen-mcp-server-vs-lago.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/adyen-mcp-server-vs-lago.md", "slim": "https://www.anchorterminal.com/compare/adyen-mcp-server-vs-lago.min.md" }, "markdown": "Lago scores 65.7 (B) on agent readiness against Adyen MCP server's 60.3 (C), and leads in 5 of 7 scored categories. Adyen MCP server leads on security \u0026 auth and transparency \u0026 trust. Both do card payments.\n\n- Adyen MCP server: grade C, 60.3/100, rank #520 of 950. Markdown https://www.anchorterminal.com/tools/adyen-mcp-server.md · JSON https://www.anchorterminal.com/api/v1/tools/adyen-mcp-server.json\n- Lago: grade B, 65.7/100, rank #311 of 950. Markdown https://www.anchorterminal.com/tools/lago.md · JSON https://www.anchorterminal.com/api/v1/tools/lago.json\n- Best payment and monetisation platforms for AI agents: https://www.anchorterminal.com/best/payment-platforms/index.md\n- All 76 platforms comparisons: https://www.anchorterminal.com/compare/payment-platforms/index.md\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\nAhead on:\n- Security \u0026 auth, 63 against 37\n- Transparency \u0026 trust, 83 against 59\n\nAlso in its favour:\n- Runs on your own machine\n- No incidents deducted, where Lago loses 3 points for them\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### Lago (B)\n\nGood for: A team that wants usage metering, plans, wallets and invoicing under its own control and can run PostgreSQL and Redis.\n\nAhead on:\n- Reliability, 86 against 65\n- Schema \u0026 documentation, 87 against 73\n- Agent ergonomics, 71 against 56\n- Payments \u0026 pricing, 50 against 35\n- Maintenance \u0026 community, 91 against 42\n\nWatch for: The free edition has one organisation API key with full access. Creating more keys needs a Premium licence and per-resource permissions need an enterprise add-on\n\n\n## Score by category\n\n| Category | Weight | Adyen MCP server | Lago | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 65 | 86 | Lago +21 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 73 | 87 | Lago +14 |\n| Agent ergonomics | 13% (16.2 this run) | 56 | 71 | Lago +15 |\n| Security \u0026 auth | 14% (17.5 this run) | 63 | 37 | Adyen MCP server +26 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 35 | 50 | Lago +15 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 42 | 91 | Lago +49 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 83 | 59 | Adyen MCP server +24 |\n| Negative events | ≤15 | 0 | -3 | |\n| **Total** | | **60.3 · C** | **65.7 · B** | |\n\n## Facts side by side\n\n| Fact | Adyen MCP server | Lago |\n| --- | --- | --- |\n| Kind | MCP server | HTTP API |\n| Vendor | Adyen N.V. | Get Lago Corp. |\n| Hosted endpoint | no (local only) | no (local only) |\n| Transports | stdio | HTTP |\n| Auth | API key | API key |\n| Pricing | Pay per use | Freemium |\n| x402 | no | no |\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 | AGPL-3.0 (platform). The MCP server and agent SDKs are MIT. Premium capabilities and Lago Cloud are commercial |\n| Tools exposed | 38 | none |\n| Read-only variant documented | yes | yes |\n| llms.txt | yes | yes |\n| Last release | 2026-08-24 | 2026-10-07 |\n| Terms last updated | 2023-11-01 | no document linked |\n| Privacy policy last updated | 2025-08-04 | no document linked |\n| Customer content may train models | yes | |\n| Terms restrict automated access | not found in the text | |\n| Terms restrict benchmarking | not found in the text | |\n| Terms or service can change without notice | not found in the text | |\n| Arbitration or class-action waiver | yes | |\n| Popularity | 27 stars, 168 npm/wk | 11k stars, 48k npm/wk |\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**Lago.** Lago's open-source edition runs usage metering, plans, wallets and invoicing on the owner's servers at no charge, with an OpenAPI 3.1 file of 217 operations and releases about every two weeks. The free edition has one unscoped API key and no audit logs, and Lago's llms.txt understates what its MCP server can change.\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### Lago\n\n1. Call `\u003cyour Lago API origin\u003e/api/v1` with `Authorization: Bearer \u003ckey\u003e`. On Lago Cloud the hosts are `api.getlago.com` and `api.eu.getlago.com`\n2. Send every usage event with a deterministic `transaction_id` and an explicit `timestamp`, and resend the same payload on retry. On the ClickHouse event store a changed timestamp is billed again\n3. Expect 422 `value_already_exist` for a repeated event on the Postgres event store. Treat it as success for a retry\n4. Page with `page` and `per_page` and read `meta.next_page` and `meta.total_count`. The default page size is 100 in most cases\n5. Treat the free edition's API key as full access. It can void invoices and terminate subscriptions, so keep it out of prompts and ask a person before financial changes\n6. Before giving an assistant the MCP server, note that it includes `delete_invoice`, `void_invoice`, `delete_plan` and `create_payment` and sets no read-only annotations\n\n## Questions\n\n### Which is better for AI agents, Adyen MCP server or Lago?\n\nLago scores 65.7 (B) on agent readiness against Adyen MCP server's 60.3 (C), and leads in 5 of 7 scored categories. Adyen MCP server leads on security \u0026 auth and transparency \u0026 trust.\n\n### Do Adyen MCP server and Lago need an API key?\n\nBoth need an API key.\n\n### Can an agent call Adyen MCP server and Lago without installing anything?\n\nAdyen MCP server runs on your own machine, with no hosted endpoint listed. No hosted endpoint is listed for Lago.\n\n### Are Adyen MCP server and Lago 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). Lago is open source (AGPL-3.0 (platform). The MCP server and agent SDKs are MIT. Premium capabilities and Lago Cloud are commercial).\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/adyen-mcp-server-vs-lago.json, and with the fewest tokens: https://www.anchorterminal.com/compare/adyen-mcp-server-vs-lago.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"adyen-mcp-server\", \"b\": \"lago\"}`. From a terminal: `anchor compare adyen-mcp-server lago`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/adyen-mcp-server.json and https://www.anchorterminal.com/api/v1/tools/lago.json\n\n## Other comparisons with Adyen MCP server or Lago\n\n- [ATXP vs Lago](https://www.anchorterminal.com/compare/atxp-vs-lago.md)\n- [Lago vs Metronome](https://www.anchorterminal.com/compare/lago-vs-metronome.md)\n- [Lago vs Nevermined API + MCP](https://www.anchorterminal.com/compare/lago-vs-nevermined.md)\n- [Lago vs Orb](https://www.anchorterminal.com/compare/lago-vs-orb.md)\n- [Lago vs Paid](https://www.anchorterminal.com/compare/lago-vs-paid.md)\n- [Lago vs Stripe API + MCP](https://www.anchorterminal.com/compare/lago-vs-stripe-mcp.md)\n- [Lago vs Tempo](https://www.anchorterminal.com/compare/lago-vs-tempo.md)\n- [Adyen MCP server vs ATXP](https://www.anchorterminal.com/compare/adyen-mcp-server-vs-atxp.md)\n- [Adyen MCP server vs Orb](https://www.anchorterminal.com/compare/adyen-mcp-server-vs-orb.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 Lago](https://www.anchorterminal.com/compare/crossmint-vs-lago.md)\n- [Lago vs Payman Genie MCP](https://www.anchorterminal.com/compare/lago-vs-payman.md)\n- [Lago vs Skyfire API + MCP](https://www.anchorterminal.com/compare/lago-vs-skyfire.md)\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 Paid](https://www.anchorterminal.com/compare/adyen-mcp-server-vs-paid.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- [Adyen MCP server vs Stripe API + MCP](https://www.anchorterminal.com/compare/adyen-mcp-server-vs-stripe-mcp.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-10", "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 Lago", "url": "" } ], "description": "Lago scores 65.7 (B) to Adyen's 60.3 (C) for card payments. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Adyen MCP server C 60.3", "Lago B 65.7", "scores" ], "h1": "Adyen MCP server vs Lago", "image": "https://www.anchorterminal.com/assets/og/compare-adyen-mcp-server-vs-lago.png", "path": "/compare/adyen-mcp-server-vs-lago", "published": "2026-10-01", "section": "tools", "title": "Adyen vs Lago for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-10-09", "url": "https://www.anchorterminal.com/compare/adyen-mcp-server-vs-lago" }, "tokens": { "markdown": 2600, "slim": 730 }, "version": 1 }