United States Payments (Stripe — Stripe checkout)

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

United States payments for AI agents — Stripe checkout via Stripe. Never holds funds.

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

VerifiedStreamable HTTPWeb executableFinanceBusiness & Commerce

Overview

AI-generated overview

Remote MCP endpoint that lets an AI assistant create Stripe checkout payments for United States transactions, without holding funds itself.

What you can do
  • Set up Stripe checkout payments for US transactions on behalf of an assistant.
  • The server is a hosted remote endpoint; no tool list, instructions or README is published, so the exact operations available are not documented here.
  • It states that it never holds funds, acting as a pass-through to Stripe checkout.
When to use it
Consider it when you want an assistant to initiate Stripe checkout payments in a US context and you are comfortable relying on a third-party hosted endpoint with little published documentation.
Requirements
A remote MCP client connecting to the hosted endpoint over streamable HTTP. No packages, environment variables, headers or authentication are declared in the manifest, so any account or key requirements are unstated.
Before you install
This server handles payments: using it can move real money, and the manifest declares no authentication, so anyone reaching the endpoint may be able to trigger checkout flows. No tool list, instructions or README is available to confirm what it does with data or how it is secured; verify ownership and terms before connecting.

Installation

In SourceWeft

  1. Open United States Payments (Stripe — Stripe checkout) 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%2Fusa-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": {
    "united-states-payments-stripe-stripe-che": {
      "type": "http",
      "url": "https://mcp-us.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