The Adyen Model Context Protocol server allows you to integrate with Adyen APIs through LLMs function calling utilizing various Clients. It
from $19/mo
Nothing to run from here
Deonpay is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
Open Installation—
p95 latency
—
call success
local
runs on your machine
—
calls last 7d
What it does
Model Context Protocol server for DeonPay - lets AI assistants like Claude Desktop interact with your payments, links, subscriptions and customers.
Quickstart
# 1 — run it from where its publisher ships it
npx -y @deonpay/mcp-server
# 2 — ask your agent something
> Model Context Protocol server for DeonPay - lets AI assistants like Claude Desktop interact with your payments, links, subscriptions and
Deonpay is free: there is no plan to choose, no cap to set and nothing that can bill you.
Publishernot claimed
DEAll 1 server
@deonpay1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Deonpay as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. It is scanned, signed and pinned to the version you choose — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. Claude Code registers it in one command.
claude mcp add deonpay-mcp -- npx -y @deonpay/mcp-serverReconnect, or start a new session, and the tools appear in the model’s tool list.
Free to install, and it runs from its publisher’s own package: no account, no key, no card.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
20 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Create an ephemeral checkout session (Stripe-style). Use this when integrating an e-commerce flow: the user wants a one-time payment URL tied to a specific cart and a success_url to land on after payment. The response contains
Takes no parameters.
Example callreturns →
List individual customer subscriptions (the per-customer rows, NOT the plans). Use this to answer
Takes no parameters.
Example callreturns →
Takes no parameters.
Example callreturns →
List the merchant
Takes no parameters.
Example callreturns →
Fetch a customer
Takes no parameters.
Example callreturns →
List payment links for the authenticated merchant. Use this when the user asks
Takes no parameters.
Example callreturns →
Takes no parameters.
Example callreturns →
List all transactions associated with a specific payment link. Use this when the user asks
Takes no parameters.
Example callreturns →
Create a new payment link. Use this when the user says
Takes no parameters.
Example callreturns →
Update an existing payment link by UUID or short_code. Only send the fields you want to change — others are preserved. Common uses: pause a link (status=
Takes no parameters.
Example callreturns →
Fetch a curated set of business metrics for the merchant. Use this as the FIRST tool for high-level questions:
Takes no parameters.
Example callreturns →
List products in the merchant catalog. Use this when the user asks
Takes no parameters.
Example callreturns →
Fetch a single product by UUID OR by SKU (if you pass a non-UUID string the API resolves it as a SKU). Returns name, description, unit_amount in centavos, currency, image_url, sku, is_active, stock_tracking, stock_quantity and metadata.
Takes no parameters.
Example callreturns →
Create a new product in the catalog. Use this when the user says
Takes no parameters.
Example callreturns →
Update an existing product (resolved by UUID or SKU). Only fields you send are changed. Use this for price adjustments, renaming, toggling is_active, updating stock_quantity, or swapping the image_url. Note: under the hood the API uses HTTP PATCH (not PUT).
Takes no parameters.
Example callreturns →
List subscription PLANS (the recurring templates, not individual subscribers). Use this when the user asks
Takes no parameters.
Example callreturns →
Fetch a single subscription plan by UUID, including aggregated stats (active_subscribers, total_subscribers) and the most recent 10 recurring charges across all subscribers. Use this when the user wants a quick health view of a specific plan (
Takes no parameters.
Example callreturns →
Create a new subscription PLAN (template). Use this when the user wants to set up a recurring charge:
Takes no parameters.
Example callreturns →
List transactions for the merchant with rich filtering. Use this for queries like
Takes no parameters.
Example callreturns →
Takes no parameters.
Example callreturns →
Freeyour plan
$0 forever
- Every tool, no call limit
- No card, no account needed
- Source published under a licence you can read
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because nothing bills
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable. Deonpay costs nothing to install and nothing to call, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: $8.42
$16.58 left
ATrust score 96 / 100
Release 0.1.0 · scanned 26 Aug 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score96
Findings0 threat · 0 capability
Capabilitymoderate
Coveragesource
Verificationrepo
Surface digest5a79c06d90a0827a58a40c3ff725a7c93608c2242b2b1f7e406c180606c4ce68
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (20 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| deonpay_list_links | no tags | |
| deonpay_get_link | untrusted-input | |
| deonpay_list_link_transactions | no tags | |
| deonpay_create_link | no tags | |
| deonpay_update_link | no tags | |
| deonpay_create_checkout_session | no tags | |
| deonpay_list_transactions | no tags | |
| deonpay_get_transaction | untrusted-input | |
| deonpay_list_products | no tags | |
| deonpay_get_product | untrusted-input | |
| deonpay_create_product | no tags | |
| deonpay_update_product | no tags | |
| deonpay_list_subscriptions | no tags | |
| deonpay_get_subscription | untrusted-input | |
| deonpay_create_subscription | no tags | |
| deonpay_list_customer_subscriptions | no tags | |
| deonpay_get_customer_subscription | untrusted-input | |
| deonpay_list_customers | no tags | |
| deonpay_get_customer | untrusted-input | |
| deonpay_get_merchant_metrics | untrusted-input |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest5a79c06d90a0827a
Scanned2026-08-26
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Pinned to 0.1.0 — the install command below asks for that release. A pin is part of an install, so it is kept for this visit and written down when you install.
0.1.0
undated
installedNo release note was published with this version.
—
no reviews yet
Reviews are earned
Only accounts with at least 50 real tool calls against this server in the last 90 days can post. Ratings are weighted by how much the reviewer actually uses it, and publishers can reply once per review.
Reviews are earned
Writing one takes an account with at least 50 real tool calls against Deonpay in the last 90 days. That is the whole gate — there is no other way to post, which is why the counts beside each review are worth reading.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes an account with 50 real tool calls against it.