WavePay Payments MCP Server

by t3ratech Your server? Claim it

answering

WavePay Payments is answering right now. Last checked 7 min ago. It exposes 6 tools.

Payments MCP: self-serve merchant key, PayNow + PayPal checkouts.

Uptime history 29 days of history

29 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

184 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 1

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 28 September 2026. No other catalogue keeps this.

28 Sep a tool changed the parameters it asks for wavepay_checkout

Nothing serious here today

Today is the operative word: we check WavePay Payments every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 7 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add wavepay --transport http https://t3rnel-wavepay-production.t3ratech.workers.dev/mcp

Settings → Connectors → Add custom connector, then paste this address

https://t3rnel-wavepay-production.t3ratech.workers.dev/mcp

~/.codex/config.toml

[mcp_servers.wavepay]
url = "https://t3rnel-wavepay-production.t3ratech.workers.dev/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "wavepay": {
      "url": "https://t3rnel-wavepay-production.t3ratech.workers.dev/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "wavepay": {
      "type": "http",
      "url": "https://t3rnel-wavepay-production.t3ratech.workers.dev/mcp"
    }
  }
}

Available tools 6

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

wavepay

wavepay_catalog

Merchant self-service catalog — the sites, plans, prices and coupons your merchant key can see. Requires the x-wavepay-service-key header carrying an mk_live_… or mk_test_… key.

wavepay_checkout

Start a checkout for a product/plan on a rail; returns the hosted checkoutUrl to hand the buyer.

wavepay_checkout_status

Poll a payment by reference: pending | collected | expired.

wavepay_pricing

Live plans and prices for a product, per rail, with the active promotion.

wavepay_providers

List the payment rails this deployment can take — PayNow (EcoCash, OneMoney, InnBucks, Telecash, O'mari, ZimSwitch, cards) and PayPal.

wavepay_register

Register a WavePay merchant account. Returns a live merchant key once — save it; only its hash is stored. Free tier: 25 payments per 30 days.

Endpoints

URL	Transport	State	Latency	Checked
https://t3rnel-wavepay-production.t3ratech.workers.dev/mcp	streamable-http	answering	108 ms	7 min ago

Alternatives to WavePay Payments

same job, measured the same way

MCP Stripe

by codespar

MCP server for Stripe — global payments API (PaymentIntents, Checkout, Billing, Refunds)

18 installs/wk local only

MCP Coinbase Commerce

by codespar

MCP server for Coinbase Commerce — crypto merchant payments (BTC/ETH/USDC); settle crypto or fiat

17 installs/wk local only

MCP Circle

by codespar

MCP server for Circle — USDC payments, wallets, payouts, transfers

11 installs/wk local only

Clawpay

by up2itnow0822

Non-custodial x402 payment MCP server for AI agents. Wallets, payments, and commerce on 17 chains.

local only

MCP Ebanx

by codespar

MCP server for EBANX — cross-border payments, payouts, exchange rates

13 installs/wk local only

MCP Mercado Pago

by codespar

Mercado Pago — payments, checkout, PIX, refunds for LATAM

21 installs/wk local only

Agentpay

by up2itnow0822

Non-custodial x402 payment MCP server for AI agents. Wallets and payments on 17 chains.

448 installs/wk local only

x402 Merchant Check

by gradientdecisions

Pre-payment merchant trust checks for x402 agents on Base and Solana.

1 tools answering

WavePay Payments — questions

Answers built from our own checks of this server.

What can WavePay Payments do?

It exposes 6 tools, read directly from the server on our last check. Among them: wavepay_catalog, wavepay_checkout, wavepay_checkout_status, wavepay_pricing, wavepay_providers, wavepay_register. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is WavePay Payments working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 184 ms. The bar chart above shows every period we have measured.

How do I connect WavePay Payments?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does WavePay Payments need an API key?

No. WavePay Payments completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 6 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is WavePay Payments?

It answers our handshake in 184 ms on average, which is faster than 82% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.