WavePay Payments MCP server
online · 100% uptimePayments MCP: self-serve merchant key, PayNow + PayPal checkouts.
Little public usage data yet
Reviews
Write oneNobody has reviewed WavePay Payments yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
WavePay Payments tools (6)
write = sends, deletes, buys or postswavepay_catalogFreeMerchant 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_checkoutFreeStart a checkout for a product/plan on a rail; returns the hosted checkoutUrl to hand the buyer.
wavepay_checkout_statusFreePoll a payment by reference: pending | collected | expired.
wavepay_pricingFreeLive plans and prices for a product, per rail, with the active promotion.
wavepay_providersFreeList the payment rails this deployment can take — PayNow (EcoCash, OneMoney, InnBucks, Telecash, O'mari, ZimSwitch, cards) and PayPal.
wavepay_registerFreeRegister a WavePay merchant account. Returns a live merchant key once — save it; only its hash is stored. Free tier: 25 payments per 30 days.
Public scan report
scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote reachable in 237ms20/20
- Tool poisoning6 tool descriptions checked15/15
- Auth qualityAPI key sent as a header8/15
- Maintenanceno repository listed3/15
- Maintainer identityno repository or website to verify2/10
Findings (1)
- lowNo source repository listed
maint.no-repo
How WavePay Payments compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 64/100
- higher than 19% of 48,273 servers
- Tools
- 6
- the typical server has 7
- Tools that change things
- 0%
- typical: 0%. Fewer write tools means less an agent can break
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 74 ms
- faster than 87% of 30,037 servers
What its tools let an agent do: 6 read
Install WavePay Payments in Claude Code, Cursor or VS Code
claude mcp add --transport http wavepay https://t3rnel-wavepay-production.t3ratech.workers.dev/mcp
WavePay Payments: common questions
- Is WavePay Payments MCP server safe?
- With care: it is graded C, so read the findings first (64/100). Read the WavePay Payments safety report
- How do I install WavePay Payments?
- It runs remotely at t3rnel-wavepay-production.t3ratech.workers.dev. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does WavePay Payments need an API key?
- Yes. The registry entry asks for
x-wavepay-service-key. - Is WavePay Payments maintained?
- The latest release is v1.0.0.
- Is WavePay Payments up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does WavePay Payments compare with other MCP servers?
- safety score 64/100 (higher than 19% of 48,273 servers); tools 6 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.