Usa Payments MCP Server

@junter1989k-ai

代码仓库主页

基本信息

许可证

MIT

传输方式

stdio

作者

junter1989k-ai

提交者

junter1989k-ai

关于 Usa Payments MCP Server

暂无概览

Usa Payments MCP Server 配置

使用下面的配置,将此服务器添加到你的 MCP 客户端。

{
  "mcpServers": {
    "usa-payments": {
      "type": "http",
      "url": "https://mcp-us.wishpool.app/mcp"
    }
  }
}

Usa Payments MCP Server 工具

工具列表暂未提供

当前收录暂时没有可展示的工具列表，不代表服务没有工具。请查阅项目文档了解支持的能力。

点击上方按钮,直接连接服务器端点实时获取工具列表。

概览

What is Usa Payments Mcp?

Usa Payments Mcp is a remote Model Context Protocol server that lets any AI agent accept payments in the United States via Stripe’s hosted checkout. It supports cards, Apple Pay, and Google Pay and acts as a stateless translation layer – funds flow directly from buyer to Stripe to merchant, and no credentials or funds are stored.

How to use Usa Payments Mcp?

Point your MCP client to the endpoint https://mcp-us.wishpool.app/mcp with the header x-stripe-secret-key set to your Stripe secret key (starting with sk_test_ for test mode or sk_live_ for production). The server exposes two tools: create_payment_link (creates a USD hosted-checkout link) and query_payment_status (pull-based status check, returns paid=true when complete). For local development, run node test/serve.js after cloning the repository.

Key features of Usa Payments Mcp

Stateless, zero‑database design – no funds or credentials stored.
Accepts cards, Apple Pay, and Google Pay via Stripe.
Two simple tools: create payment link and check payment status.
Streamable HTTP transport for real‑time agent communication.
Part of a 20‑country payments family with a shared hub.
No runtime dependencies; requires Node.js ≥ 18.

Use cases of Usa Payments Mcp

AI assistants generating collect‑on‑delivery payment links during conversations.
E‑commerce bots creating checkout pages for customer orders.
Automated payment status polling to confirm purchase completion.
Multi‑country payment orchestration with other servers in the same family.

常见问题

What payment methods are supported?

Cards, Apple Pay, and Google Pay, plus any other methods enabled on the connected Stripe account.

Does the server store any payment data?

No – it is a stateless translation layer. Funds flow directly buyer → Stripe → merchant, and the server has no database.

How do I switch between test and production mode?

Use a Stripe secret key beginning with `sk_test_` for testing or `sk_live_` for live payments. The server behavior is identical; the key determines which Stripe environment is used.

What runtime is required to run the server locally?

Node.js version 18 or higher. The repository has zero runtime dependencies and is MIT licensed.

Is authentication required other than the Stripe key?

Only the `x-stripe-secret-key` header is needed. No additional tokens or bearer authentication are specified.