Skip to content

How Mollie’s scores are calculated

The full audit trail, recomputed from the verdict data at build time through the same code that produced the leaderboard: verdict × quality × story weight per cell, cells sum to dimension scores, dimensions blend into the PA Score. Every number on the product page is reproducible from this page alone; for why the formula looks like this, see the methodology.

verdict factors: full ×1.0 · partial ×0.6 · disputed ×0.3 · none ×0.0 · n/a excluded from both sides · cell points = weight × quality × factor · cell max = weight × 10

PA Score30/100

Agent-ready 59.0 × 0.30 = 17.70

API quality 11.4 × 0.20 = 2.28

Openness 16.8 × 0.20 = 3.36

Built-in AI 23.6 × 0.15 = 3.54

Automation 20.6 × 0.15 = 3.09

(17.70 + 2.28 + 3.36 + 3.54 + 3.09) ÷ (0.30 + 0.20 + 0.20 + 0.15 + 0.15) = 29.97 ÷ 1.00 = 30.0

Scores are stored to 1 decimal; the product page’s pills round to whole numbers for display. Each dimension below shows the stories, verdicts, and cited evidence behind its number.

Agent-ready59.0/100×0.30 of the PA blend

Outside-in: can YOUR agent reach and drive this product — API, MCP, CLI, headless runs, agent docs.

Point an agent at llms.txt or agent-oriented docsweight 2

2 (weight) × 9 (quality) × 1.0 (full) = 18.0 of 20 max

  • [claimed-docs] https://docs.mollie.com/llms.txtdocs.mollie.com publishes a full llms.txt page index and documents the markdown mirror convention on every page: "Fetch the complete documentation index at: https://docs.mollie.com/llms.txt. Use this file to discover all available pages before exploring further. Append .md to any documentation page URL to get its markdown version."
  • [probe] https://docs.mollie.com/llms.txtPROBE llms.txt: HTTP 200 at https://docs.mollie.com/llms.txt # Mollie Documentation Documentation > Easily integrate online and point-of-sale payments into your platform with our r

Run the product headlessly / in CI for automationweight 2

2 (weight) × 7 (quality) × 1.0 (full) = 14.0 of 20 max

  • [claimed-docs] https://docs.mollie.com/reference/testing.mdTest mode is a first-class switch: "You can access the `test` mode of the Mollie API in two ways: by using the Test API key, or... by providing the `testmode` parameter in your API request. Any payments or other resources you create in test mode are completely isolated from your live mode data." Test-mode checkout replaces the hosted pages so "you can walk through the payment process without spending actual money", and paid test payments expose a `changePaymentState` URL to simulate refunds and chargebacks.
  • [claimed-docs] https://docs.mollie.com/reference/api-idempotency.mdIdempotent retries via a documented header: "you can send a unique value with every API request via the `Idempotency-Key` header. If two requests come in with the same value, the second request is considered a duplicate that can be ignored." The docs spell out exactly where retries are dangerous without it: recurring payments ("can lead to double charges"), subscriptions ("double charges during the entire duration of both subscriptions"), and partial refunds ("executing the refund twice may lead to two separate partial refunds").
  • [claimed-docs] https://docs.mollie.com/reference/authentication.mdFour documented authentication methods — API keys ("default API access for a specific payment profile"), Advanced access tokens ("advanced API access for organization-level data... can be scoped to a specific mode or profile"), App access tokens (OAuth, "on behalf of your connected customers"), and Basic Auth for token management. Keys are shown once at creation, and "Permissions are now grouped by business area and API... all keys now clearly show which permissions are included with your API key."
  • [claimed-docs] https://docs.mollie.com/reference/payments-api.mdThe Payments API is at the heart of the Mollie API. It allows you to create and manage payments.
  • [claimed-docs] https://docs.mollie.com/reference/webhooks.mdWebhooks are used to process real-time status updates, for example when a payment is paid.

Plug MCP servers into this product so it can use their toolsweight 3

n/a — not applicable to this product: excluded from numerator and denominator

no evidence cited — the verdict rests on absence of evidence, re-checked on refresh

Connect an agent via an official MCP serverweight 3

3 (weight) × 9 (quality) × 1.0 (full) = 27.0 of 30 max

  • [claimed-docs] https://docs.mollie.com/docs/mollie-mcp-server.mdThe Mollie MCP server enables merchants to use various AI tools like Claude Desktop and Cursor AI to utilize natural language for creating different resources in their Mollie account.
  • [claimed-docs] https://docs.mollie.com/docs/mollie-mcp-server.mdThe Mollie MCP server is hosted at a documented endpoint: "You can find Mollie MCP server at `https://mcp.mollie.com/mcp`, which acts as a proxy for the public API." Coverage: "Currently, the following APIs are available: Balances API, Captures API, Customers API, Invoices API, Mandates API, Methods API, Payments API, Payment Links API, Settlements API, Subscriptions API, Terminals API, Webhooks API, Webhook Events API." Access is scoped: an Advanced access token in `MOLLIE_API_OAUTH_ORG_TOKEN` where "profile.read is a required scope" and optional scopes per API enable each tool; documented client configs cover Claude Desktop, Cursor, and VS Code via mcp-remote.
  • [probe] https://docs.mollie.com/docs/mollie-mcp-serverofficial MCP server documented at https://docs.mollie.com/docs/mollie-mcp-server

Use an official CLIweight 2

2 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 20 max

no evidence cited — the verdict rests on absence of evidence, re-checked on refresh

Drive the product through a documented public APIweight 3

3 (weight) × 8 (quality) × 1.0 (full) = 24.0 of 30 max

  • [claimed-docs] https://docs.mollie.com/reference/payments-api.mdThe Payments API is at the heart of the Mollie API. It allows you to create and manage payments.
  • [claimed-docs] https://docs.mollie.com/reference/api-idempotency.mdIdempotent retries via a documented header: "you can send a unique value with every API request via the `Idempotency-Key` header. If two requests come in with the same value, the second request is considered a duplicate that can be ignored." The docs spell out exactly where retries are dangerous without it: recurring payments ("can lead to double charges"), subscriptions ("double charges during the entire duration of both subscriptions"), and partial refunds ("executing the refund twice may lead to two separate partial refunds").
  • [claimed-docs] https://docs.mollie.com/reference/testing.mdTest mode is a first-class switch: "You can access the `test` mode of the Mollie API in two ways: by using the Test API key, or... by providing the `testmode` parameter in your API request. Any payments or other resources you create in test mode are completely isolated from your live mode data." Test-mode checkout replaces the hosted pages so "you can walk through the payment process without spending actual money", and paid test payments expose a `changePaymentState` URL to simulate refunds and chargebacks.
  • [claimed-docs] https://docs.mollie.com/reference/authentication.mdFour documented authentication methods — API keys ("default API access for a specific payment profile"), Advanced access tokens ("advanced API access for organization-level data... can be scoped to a specific mode or profile"), App access tokens (OAuth, "on behalf of your connected customers"), and Basic Auth for token management. Keys are shown once at creation, and "Permissions are now grouped by business area and API... all keys now clearly show which permissions are included with your API key."
  • [claimed-docs] https://docs.mollie.com/llms.txtdocs.mollie.com publishes a full llms.txt page index and documents the markdown mirror convention on every page: "Fetch the complete documentation index at: https://docs.mollie.com/llms.txt. Use this file to discover all available pages before exploring further. Append .md to any documentation page URL to get its markdown version."
  • [claimed-docs] https://docs.mollie.com/docs/mollie-mcp-server.mdThe Mollie MCP server is hosted at a documented endpoint: "You can find Mollie MCP server at `https://mcp.mollie.com/mcp`, which acts as a proxy for the public API." Coverage: "Currently, the following APIs are available: Balances API, Captures API, Customers API, Invoices API, Mandates API, Methods API, Payments API, Payment Links API, Settlements API, Subscriptions API, Terminals API, Webhooks API, Webhook Events API." Access is scoped: an Advanced access token in `MOLLIE_API_OAUTH_ORG_TOKEN` where "profile.read is a required scope" and optional scopes per API enable each tool; documented client configs cover Claude Desktop, Cursor, and VS Code via mcp-remote.
  • [probe] https://docs.mollie.com/llms.txtPROBE llms.txt: HTTP 200 at https://docs.mollie.com/llms.txt # Mollie Documentation Documentation > Easily integrate online and point-of-sale payments into your platform with our r
  • [probe] https://docs.mollie.com/openapi.jsonPROBE openapi: all candidate paths 404 (https://docs.mollie.com/openapi.json, https://docs.mollie.com/swagger.json, https://docs.mollie.com/api/openapi.json, https://docs.mollie.com/.well-known/openapi.json)
  • [probe] https://docs.mollie.com/docs/mollie-mcp-serverofficial MCP server documented at https://docs.mollie.com/docs/mollie-mcp-server

Issue scoped/least-privilege API credentials for an agentweight 2

2 (weight) × 6 (quality) × 0.6 (partial) = 7.2 of 20 max

  • [claimed-docs] https://docs.mollie.com/reference/authentication.mdFour documented authentication methods — API keys ("default API access for a specific payment profile"), Advanced access tokens ("advanced API access for organization-level data... can be scoped to a specific mode or profile"), App access tokens (OAuth, "on behalf of your connected customers"), and Basic Auth for token management. Keys are shown once at creation, and "Permissions are now grouped by business area and API... all keys now clearly show which permissions are included with your API key."
  • [claimed-docs] https://docs.mollie.com/docs/mollie-mcp-server.mdThe Mollie MCP server is hosted at a documented endpoint: "You can find Mollie MCP server at `https://mcp.mollie.com/mcp`, which acts as a proxy for the public API." Coverage: "Currently, the following APIs are available: Balances API, Captures API, Customers API, Invoices API, Mandates API, Methods API, Payments API, Payment Links API, Settlements API, Subscriptions API, Terminals API, Webhooks API, Webhook Events API." Access is scoped: an Advanced access token in `MOLLIE_API_OAUTH_ORG_TOKEN` where "profile.read is a required scope" and optional scopes per API enable each tool; documented client configs cover Claude Desktop, Cursor, and VS Code via mcp-remote.
  • [claimed-docs] https://docs.mollie.com/docs/mollie-mcp-server.mdThe Mollie MCP server enables merchants to use various AI tools like Claude Desktop and Cursor AI to utilize natural language for creating different resources in their Mollie account.

Build against official SDKsweight 2

2 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 20 max

no evidence cited — the verdict rests on absence of evidence, re-checked on refresh

Subscribe to events via webhooksweight 2

2 (weight) × 8 (quality) × 1.0 (full) = 16.0 of 20 max

  • [claimed-docs] https://docs.mollie.com/reference/webhooks-new.mdNext-gen webhooks add a subscription model and an audit API: "Updated Webhooks API allowing you to permanently subscribe to specific event types, compared to 'one-off' webhooks fired by each payment" and a "Webhook Events API allowing you to retroactively inspect past events sent to you via webhooks and enable retrieving detailed information about each individual triggered event", with a choice of full-snapshot or simple payloads.
  • [claimed-docs] https://docs.mollie.com/reference/webhooks.mdWebhooks are used to process real-time status updates, for example when a payment is paid.
  • [claimed-docs] https://docs.mollie.com/reference/webhooks-best-practices.mdTo verify HMAC signature for a webhook, follow these steps: 1. Retrieve the signature from the request header (X-Mollie-Signature)...
  • [claimed-docs] https://docs.mollie.com/reference/webhooks-new.mdNew event types to offer a broader context for your business processes (e.g. payment creation, invoice creation, onboarding status changes etc).
  • [claimed-docs] https://docs.mollie.com/reference/webhooks-best-practices.mdTo verify HMAC signature for a webhook, follow these steps: Retrieve the signature from the request header (X-Mollie-Signature) and obtain the shared secret key.

Agent-ready = 106.2 ÷ 180 × 100 = 59.0

API quality11.4/100×0.20 of the PA blend

The programmable surface once an agent is there — machine-readable spec, interactive docs, sandbox, versioning discipline.

Explore an interactive API reference with runnable examplesweight 2

2 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 20 max

  • [probe] https://docs.mollie.com/openapi.jsonPROBE openapi: all candidate paths 404 (https://docs.mollie.com/openapi.json, https://docs.mollie.com/swagger.json, https://docs.mollie.com/api/openapi.json, https://docs.mollie.com/.well-known/openapi.json)
  • [claimed-docs] https://docs.mollie.com/llms.txtdocs.mollie.com publishes a full llms.txt page index and documents the markdown mirror convention on every page: "Fetch the complete documentation index at: https://docs.mollie.com/llms.txt. Use this file to discover all available pages before exploring further. Append .md to any documentation page URL to get its markdown version."
  • [probe] https://docs.mollie.com/llms.txtPROBE llms.txt: HTTP 200 at https://docs.mollie.com/llms.txt # Mollie Documentation Documentation > Easily integrate online and point-of-sale payments into your platform with our r

Download a machine-readable API spec (OpenAPI or equivalent)weight 2

2 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 20 max

  • [probe] https://docs.mollie.com/openapi.jsonPROBE openapi: all candidate paths 404 (https://docs.mollie.com/openapi.json, https://docs.mollie.com/swagger.json, https://docs.mollie.com/api/openapi.json, https://docs.mollie.com/.well-known/openapi.json)
  • [claimed-docs] https://docs.mollie.com/llms.txtdocs.mollie.com publishes a full llms.txt page index and documents the markdown mirror convention on every page: "Fetch the complete documentation index at: https://docs.mollie.com/llms.txt. Use this file to discover all available pages before exploring further. Append .md to any documentation page URL to get its markdown version."
  • [probe] https://docs.mollie.com/llms.txtPROBE llms.txt: HTTP 200 at https://docs.mollie.com/llms.txt # Mollie Documentation Documentation > Easily integrate online and point-of-sale payments into your platform with our r

Test against a sandbox environment without touching production dataweight 1

1 (weight) × 8 (quality) × 1.0 (full) = 8.0 of 10 max

  • [claimed-docs] https://docs.mollie.com/reference/testing.mdAny payments or other resources you create in test mode are completely isolated from your live mode data.
  • [claimed-docs] https://docs.mollie.com/reference/testing.mdTest mode is a first-class switch: "You can access the `test` mode of the Mollie API in two ways: by using the Test API key, or... by providing the `testmode` parameter in your API request. Any payments or other resources you create in test mode are completely isolated from your live mode data." Test-mode checkout replaces the hosted pages so "you can walk through the payment process without spending actual money", and paid test payments expose a `changePaymentState` URL to simulate refunds and chargebacks.

Rely on versioned APIs with a documented deprecation policyweight 2

2 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 20 max

  • [claimed-docs] https://docs.mollie.com/docs/multicurrency.mdMollie enables you to accept payments in currencies beyond EUR through its v2 APIs, allowing international customers to transact in their preferred currency.

API quality = 8.0 ÷ 70 × 100 = 11.4

Openness16.8/100×0.20 of the PA blend

Can you leave, inspect, or self-host — data export, open source, portability.

Do everything through the API that I can do in the UIweight 2

2 (weight) × 7 (quality) × 0.6 (partial) = 8.4 of 20 max

  • [claimed-docs] https://docs.mollie.com/docs/refunds.mdyou can also create refunds manually via the Mollie Web app.
  • [claimed-docs] https://docs.mollie.com/docs/refunds.mdNext to the API endpoint, you can also create refunds manually via the Mollie Web app.
  • [claimed-docs] https://docs.mollie.com/reference/balances-api.mdThe Balances API allows you to retrieve real-time as well as historical information about your Mollie balance.
  • [claimed-docs] https://docs.mollie.com/reference/balances-api.mdThe Balances API allows you to retrieve real-time as well as historical information about your Mollie balance. This may be useful to for example integrate Mollie into your bookkeeping.
  • [claimed-docs] https://docs.mollie.com/docs/settlement-report.mdSettlement Report gives you a complete breakdown of the data included in a specific payout... helping you reconcile your transactions.
  • [claimed-docs] https://docs.mollie.com/docs/settlement-report.mdSettlement Report gives you a complete breakdown of the data included in a specific payout. It shows all transactions, fees and deductions that are part of a single settlement.
  • [claimed-docs] https://docs.mollie.com/reference/chargebacks-api.mdThe Chargebacks API then allows you to retrieve details of the chargebacks that took place on your account.
  • [claimed-docs] https://docs.mollie.com/docs/connect-route-and-split-payments.mdMarketplace money movement is documented under Mollie Connect: "Split payments let marketplaces distribute funds across multiple sellers in a single transaction. When a buyer pays, Mollie holds the incoming funds in an escrow-like account (your marketplace's holding balance) before distributing specified amounts to each connected seller's balance, while letting you retain a portion of the funds as a commission" — alongside application fees, merchant onboarding, and Connect reporting pages.
  • [claimed-docs] https://docs.mollie.com/reference/testing.mdTest mode is a first-class switch: "You can access the `test` mode of the Mollie API in two ways: by using the Test API key, or... by providing the `testmode` parameter in your API request. Any payments or other resources you create in test mode are completely isolated from your live mode data." Test-mode checkout replaces the hosted pages so "you can walk through the payment process without spending actual money", and paid test payments expose a `changePaymentState` URL to simulate refunds and chargebacks.
  • [claimed-docs] https://docs.mollie.com/reference/authentication.mdFour documented authentication methods — API keys ("default API access for a specific payment profile"), Advanced access tokens ("advanced API access for organization-level data... can be scoped to a specific mode or profile"), App access tokens (OAuth, "on behalf of your connected customers"), and Basic Auth for token management. Keys are shown once at creation, and "Permissions are now grouped by business area and API... all keys now clearly show which permissions are included with your API key."

Export all of my data in open formats and leaveweight 3

3 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 30 max

  • [claimed-docs] https://docs.mollie.com/docs/settlement-report.mdSettlement Report gives you a complete breakdown of the data included in a specific payout... helping you reconcile your transactions.
  • [claimed-docs] https://docs.mollie.com/reference/balances-api.mdThe Balances API allows you to retrieve real-time as well as historical information about your Mollie balance.
  • [claimed-docs] https://docs.mollie.com/docs/settlement-report.mdSettlement Report gives you a complete breakdown of the data included in a specific payout. It shows all transactions, fees and deductions that are part of a single settlement.
  • [claimed-docs] https://docs.mollie.com/reference/balances-api.mdThe Balances API allows you to retrieve real-time as well as historical information about your Mollie balance. This may be useful to for example integrate Mollie into your bookkeeping.

Read the product's source under an open licenseweight 2

n/a — not applicable to this product: excluded from numerator and denominator

no evidence cited — the verdict rests on absence of evidence, re-checked on refresh

Self-host the core productweight 3

n/a — not applicable to this product: excluded from numerator and denominator

no evidence cited — the verdict rests on absence of evidence, re-checked on refresh

Openness = 8.4 ÷ 50 × 100 = 16.8

Built-in AI23.6/100×0.15 of the PA blend

Inside-out: how agentic the product itself is for its users — built-in assistants, autonomous features.

Get AI-generated insights and suggestions from my data inside the productweight 2

2 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 20 max

  • [claimed-docs] https://docs.mollie.com/docs/mollie-mcp-server.mdThe Mollie MCP server enables merchants to use various AI tools like Claude Desktop and Cursor AI to utilize natural language for creating different resources in their Mollie account.
  • [claimed-docs] https://docs.mollie.com/docs/mollie-mcp-server.mdThe Mollie MCP server is hosted at a documented endpoint: "You can find Mollie MCP server at `https://mcp.mollie.com/mcp`, which acts as a proxy for the public API." Coverage: "Currently, the following APIs are available: Balances API, Captures API, Customers API, Invoices API, Mandates API, Methods API, Payments API, Payment Links API, Settlements API, Subscriptions API, Terminals API, Webhooks API, Webhook Events API." Access is scoped: an Advanced access token in `MOLLIE_API_OAUTH_ORG_TOKEN` where "profile.read is a required scope" and optional scopes per API enable each tool; documented client configs cover Claude Desktop, Cursor, and VS Code via mcp-remote.

Set up automations that run autonomously in the backgroundweight 2

2 (weight) × 6 (quality) × 0.6 (partial) = 7.2 of 20 max

  • [claimed-docs] https://docs.mollie.com/docs/recurring-payments.mdRecurring payments happen in the background. The customer goes through the payment steps only once, for the first payment.
  • [claimed-docs] https://docs.mollie.com/reference/subscriptions-api.mdThe Subscriptions API provides an easy way to schedule recurring payments at regular intervals. When using this API, we automatically create recurring payments for you at the interval you specified.
  • [claimed-docs] https://docs.mollie.com/reference/subscriptions-api.mdWhen using this API, we automatically create recurring payments for you at the interval you specified.
  • [claimed-docs] https://docs.mollie.com/reference/webhooks.mdWebhooks are used to process real-time status updates, for example when a payment is paid.
  • [claimed-docs] https://docs.mollie.com/docs/mollie-mcp-server.mdThe Mollie MCP server enables merchants to use various AI tools like Claude Desktop and Cursor AI to utilize natural language for creating different resources in their Mollie account.
  • [claimed-docs] https://docs.mollie.com/docs/mollie-mcp-server.mdThe Mollie MCP server is hosted at a documented endpoint: "You can find Mollie MCP server at `https://mcp.mollie.com/mcp`, which acts as a proxy for the public API." Coverage: "Currently, the following APIs are available: Balances API, Captures API, Customers API, Invoices API, Mandates API, Methods API, Payments API, Payment Links API, Settlements API, Subscriptions API, Terminals API, Webhooks API, Webhook Events API." Access is scoped: an Advanced access token in `MOLLIE_API_OAUTH_ORG_TOKEN` where "profile.read is a required scope" and optional scopes per API enable each tool; documented client configs cover Claude Desktop, Cursor, and VS Code via mcp-remote.
  • [claimed-docs] https://docs.mollie.com/reference/webhooks-new.mdNext-gen webhooks add a subscription model and an audit API: "Updated Webhooks API allowing you to permanently subscribe to specific event types, compared to 'one-off' webhooks fired by each payment" and a "Webhook Events API allowing you to retroactively inspect past events sent to you via webhooks and enable retrieving detailed information about each individual triggered event", with a choice of full-snapshot or simple payloads.

Delegate tasks to a built-in AI assistant inside the productweight 3

3 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 30 max

  • [claimed-docs] https://docs.mollie.com/docs/mollie-mcp-server.mdThe Mollie MCP server enables merchants to use various AI tools like Claude Desktop and Cursor AI to utilize natural language for creating different resources in their Mollie account.
  • [claimed-docs] https://docs.mollie.com/docs/mollie-mcp-server.mdThe Mollie MCP server is hosted at a documented endpoint: "You can find Mollie MCP server at `https://mcp.mollie.com/mcp`, which acts as a proxy for the public API." Coverage: "Currently, the following APIs are available: Balances API, Captures API, Customers API, Invoices API, Mandates API, Methods API, Payments API, Payment Links API, Settlements API, Subscriptions API, Terminals API, Webhooks API, Webhook Events API." Access is scoped: an Advanced access token in `MOLLIE_API_OAUTH_ORG_TOKEN` where "profile.read is a required scope" and optional scopes per API enable each tool; documented client configs cover Claude Desktop, Cursor, and VS Code via mcp-remote.
  • [probe] https://docs.mollie.com/docs/mollie-mcp-serverofficial MCP server documented at https://docs.mollie.com/docs/mollie-mcp-server

Operate the product with natural-language commandsweight 2

2 (weight) × 7 (quality) × 1.0 (full) = 14.0 of 20 max

  • [claimed-docs] https://docs.mollie.com/docs/mollie-mcp-server.mdThe Mollie MCP server enables merchants to use various AI tools like Claude Desktop and Cursor AI to utilize natural language for creating different resources in their Mollie account.
  • [claimed-docs] https://docs.mollie.com/docs/mollie-mcp-server.mdThe Mollie MCP server is hosted at a documented endpoint: "You can find Mollie MCP server at `https://mcp.mollie.com/mcp`, which acts as a proxy for the public API." Coverage: "Currently, the following APIs are available: Balances API, Captures API, Customers API, Invoices API, Mandates API, Methods API, Payments API, Payment Links API, Settlements API, Subscriptions API, Terminals API, Webhooks API, Webhook Events API." Access is scoped: an Advanced access token in `MOLLIE_API_OAUTH_ORG_TOKEN` where "profile.read is a required scope" and optional scopes per API enable each tool; documented client configs cover Claude Desktop, Cursor, and VS Code via mcp-remote.
  • [probe] https://docs.mollie.com/docs/mollie-mcp-serverofficial MCP server documented at https://docs.mollie.com/docs/mollie-mcp-server

Built-in AI = 21.2 ÷ 90 × 100 = 23.6

Automation20.6/100×0.15 of the PA blend

Depth of automation primitives — rules, scheduling, bulk operations, webhooks.

Perform bulk operations across many items at onceweight 2

2 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 20 max

  • [claimed-docs] https://docs.mollie.com/docs/mollie-mcp-server.mdThe Mollie MCP server enables merchants to use various AI tools like Claude Desktop and Cursor AI to utilize natural language for creating different resources in their Mollie account.
  • [claimed-docs] https://docs.mollie.com/docs/mollie-mcp-server.mdThe Mollie MCP server is hosted at a documented endpoint: "You can find Mollie MCP server at `https://mcp.mollie.com/mcp`, which acts as a proxy for the public API." Coverage: "Currently, the following APIs are available: Balances API, Captures API, Customers API, Invoices API, Mandates API, Methods API, Payments API, Payment Links API, Settlements API, Subscriptions API, Terminals API, Webhooks API, Webhook Events API." Access is scoped: an Advanced access token in `MOLLIE_API_OAUTH_ORG_TOKEN` where "profile.read is a required scope" and optional scopes per API enable each tool; documented client configs cover Claude Desktop, Cursor, and VS Code via mcp-remote.
  • [claimed-docs] https://docs.mollie.com/reference/payments-api.mdThe Payments API is at the heart of the Mollie API. It allows you to create and manage payments.
  • [claimed-docs] https://docs.mollie.com/docs/refunds.mdNext to the API endpoint, you can also create refunds manually via the Mollie Web app.

Define rules that trigger actions automatically on eventsweight 3

3 (weight) × 4 (quality) × 0.6 (partial) = 7.2 of 30 max

  • [claimed-docs] https://docs.mollie.com/reference/webhooks.mdWebhooks are used to process real-time status updates, for example when a payment is paid.
  • [claimed-docs] https://docs.mollie.com/reference/webhooks-new.mdNext-gen webhooks add a subscription model and an audit API: "Updated Webhooks API allowing you to permanently subscribe to specific event types, compared to 'one-off' webhooks fired by each payment" and a "Webhook Events API allowing you to retroactively inspect past events sent to you via webhooks and enable retrieving detailed information about each individual triggered event", with a choice of full-snapshot or simple payloads.
  • [claimed-docs] https://docs.mollie.com/reference/subscriptions-api.mdThe Subscriptions API provides an easy way to schedule recurring payments at regular intervals. When using this API, we automatically create recurring payments for you at the interval you specified.
  • [claimed-docs] https://docs.mollie.com/docs/application-fees.mdApplication Fees allow your platform to collect a fee on every payment you process on behalf of a connected account. You define the amount, flat, percentage (or a combination of those) and Mollie moves it to your balance automatically when the payment succeeds.
  • [claimed-docs] https://docs.mollie.com/reference/api-idempotency.mdIdempotent retries via a documented header: "you can send a unique value with every API request via the `Idempotency-Key` header. If two requests come in with the same value, the second request is considered a duplicate that can be ignored." The docs spell out exactly where retries are dangerous without it: recurring payments ("can lead to double charges"), subscriptions ("double charges during the entire duration of both subscriptions"), and partial refunds ("executing the refund twice may lead to two separate partial refunds").

Schedule recurring jobs or workflowsweight 2

2 (weight) × 6 (quality) × 0.6 (partial) = 7.2 of 20 max

  • [claimed-docs] https://docs.mollie.com/reference/subscriptions-api.mdWhen using this API, we automatically create recurring payments for you at the interval you specified.
  • [claimed-docs] https://docs.mollie.com/reference/subscriptions-api.mdThe Subscriptions API provides an easy way to schedule recurring payments at regular intervals. When using this API, we automatically create recurring payments for you at the interval you specified.
  • [claimed-docs] https://docs.mollie.com/docs/recurring-payments.mdRecurring payments can be used to charge customers on a regular basis or to offer automatic top-ups with credits-based services.
  • [claimed-docs] https://docs.mollie.com/docs/recurring-payments.mdRecurring payments happen in the background. The customer goes through the payment steps only once, for the first payment.

Version, review, and roll back my automationsweight 1

n/a — not applicable to this product: excluded from numerator and denominator

no evidence cited — the verdict rests on absence of evidence, re-checked on refresh

Automation = 14.4 ÷ 70 × 100 = 20.6