Denmark Payments (Stripe — MobilePay)

app.wishpoolPublished by wishpool.appOfficial publisherv0.1.0Updated Oct 24, 2026

Denmark payments for AI agents — MobilePay via Stripe. Never holds funds.

The publisher's own server: Algeria Payments (Chargily Pay — EDAHABIA / CIB)

VerifiedStreamable HTTPWeb executableFinanceBusiness & Commerce

Overview

AI-generated overview

A remote MCP endpoint that lets an assistant handle Denmark payments through MobilePay via Stripe.

What you can do
The registry describes it as Denmark payments for AI agents, offering MobilePay payments through Stripe. It is a remote streamable HTTP endpoint at mcp-dk.wishpool.app, and the description states it never holds funds. No tools, packages, environment variables, or headers are listed in the manifest.
When to use it
Consider it when an assistant needs to work with Danish MobilePay payment flows processed through Stripe. The available input does not describe specific tools, so suitability for a given payment task cannot be confirmed from this listing.
Requirements
A remote MCP client that can connect to the streamable HTTP endpoint at mcp-dk.wishpool.app. The manifest declares no authentication, no environment variables, no headers, and no packages.
Before you install
This server concerns payments, so any action it exposes could move or commit money; the description says it never holds funds, but that does not by itself limit what an assistant can trigger. The manifest declares no authentication, so verify how access is actually controlled before connecting. No tool list is provided, so review the tools before allowing any write or payment action.

Installation

In SourceWeft

  1. Open Denmark Payments (Stripe — MobilePay) in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/app.wishpool%2Fdenmark-payments-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "denmark-payments-stripe-mobilepay": {
      "type": "http",
      "url": "https://mcp-dk.wishpool.app/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Wishpool integrations