概要
What is Denmark Payments Mcp?
An MCP (Model Context Protocol) server that lets any AI agent (Claude, ChatGPT, Cursor, etc.) accept payments in Denmark via MobilePay, cards, and Klarna. It acts as a stateless translation layer over Stripe’s hosted checkout—funds flow directly from buyer to merchant without the server holding funds or storing credentials.
How to use Denmark Payments Mcp?
Add the endpoint https://mcp-dk.wishpool.app/mcp to your MCP client and pass your Stripe secret key as the header x-stripe-secret-key. Use the tools create_payment_link to generate a DKK checkout link and query_payment_status to check payment status. For local testing run node test/serve.js and for protocol validation node test/e2e.js.
Key features of Denmark Payments Mcp
- Stateless: no database, never holds funds or credentials
- Supports MobilePay, cards, and Klarna via Stripe
- Remote Streamable HTTP endpoint, no local installation needed
- Two tools: create payment link and query payment status
- Part of a 50-country family of payment MCP servers
- MIT licensed, zero runtime dependencies (Node ≥ 18)
Use cases of Denmark Payments Mcp
- Allow an AI assistant to generate a checkout link in Danish kroner for a user
- Let a chatbot accept payments for digital goods or services inside Denmark
- Build a multi-country agent that switches between country‑specific payment rails
- Enable automated payment status verification without manual polling
FAQ from Denmark Payments Mcp
How is Denmark Payments Mcp different from a direct Stripe integration?
It is a stateless translation layer that converts MCP tool calls into Stripe hosted‑checkout requests. No Stripe credentials are stored on the server—they are passed per‑request via the x-stripe-secret-key header. There is no database and no fund holding.
What are the runtime requirements?
Node.js version 18 or later. The server has zero runtime dependencies. For production use, only an HTTPS endpoint is needed; no local software is required for clients.
Where does payment data live?
All payment data resides in Stripe. The server never stores any data—it only forwards requests and responses. Funds move directly from the buyer to the merchant’s Stripe account.
What transports and auth does this server support?
It uses Streamable HTTP (stateless JSON‑RPC) over HTTPS. Authentication is done via the x-stripe-secret-key header containing the user’s Stripe secret key (test or live). No other auth mechanism is documented.
Are there known limits?
The README does not mention specific rate limits or transaction caps. It is built to be stateless and lightweight, but any Stripe‑imposed limits would apply. The server is part of a 50‑country family, suggesting it is designed for multi‑region use.
