Skip to content

WavePay Payments MCP server

io.github.t3ratech/wavepayt3ratechstreamable-httpv1.0.0Scanned

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

11 tools: 1 do something that can't be undone, 9 change things and 1 only read.

Tools: 0 delete, 1 irreversible, 9 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 2
  • No findings

Tools listed without sign-in. Remote posture

Anlyon alternative

10 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the WavePay Payments MCP server can do

The WavePay Payments MCP server is published by the GitHub account t3ratech. It has 11 tools. It can do things that cannot be undone, such as sending, paying or publishing (wavepay_refund) and create or change data (9 tools: wavepay_register, wavepay_pricing, wavepay_checkout, wavepay_checkout_status and 5 more), but cannot delete data. 1 tool only reads.

2 tools can send data out of your system (wavepay_checkout and wavepay_subscribe).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 21, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

11 tools

Can't be undone 1Claude Code: ask
  • wavepay_refundRefund a settled payment through its provider (PayPal; test payments with a test key).No findings

    Why it is in this group

    • The name "wavepay_refund" says "refund": a word that usually means money moves, which cannot be taken back.
    Description, as the server wrote it
    Refund a settled payment through its provider (PayPal; test payments with a test key). PayNow documents no refund API, so a PayNow payment is refused with REFUND_UNSUPPORTED rather than recorded as refunded. Needs a merchant key.
Changes things 9Claude Code: ask
  • wavepay_bnplBuy now, pay later: take a deposit now and collect the rest from the buyer's card on a schedule until the total is paid.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Buy now, pay later: take a deposit now and collect the rest from the buyer's card on a schedule until the total is paid. Cards only (provider paynow or paypal); prepaid and virtual cards are refused. Needs a merchant key; mk_test_ previews it.
  • wavepay_catalogMerchant self-service catalog — the sites, plans, prices and coupons your merchant key can see.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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_checkoutStart a checkout for a product/plan on a rail; returns the hosted checkoutUrl to hand the buyer.Can send data outNo findings

    Why it is in this group

    • The name "wavepay_checkout" says "checkout": a word for a change.

    What it can reach

    • outboundThe input takes a destination (input.phone): what the tool writes goes there.
    Description, as the server wrote it
    Start a checkout for a product/plan on a rail; returns the hosted checkoutUrl to hand the buyer.
  • wavepay_checkout_statusPoll a payment by reference: pending | collected | expired.No findings

    Why it is in this group

    • The name "wavepay_checkout_status" says "checkout": a word for a change.
    Description, as the server wrote it
    Poll a payment by reference: pending | collected | expired.
  • wavepay_featuresWhich flagged capabilities (refunds, recurring, bnpl, card_tokens, paypal_billing, disputes) this deployment has switched on for live money.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Which flagged capabilities (refunds, recurring, bnpl, card_tokens, paypal_billing, disputes) this deployment has switched on for live money. Test-mode keys can use every one.
  • wavepay_pricingLive plans and prices for a product, per rail, with the active promotion.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Live plans and prices for a product, per rail, with the active promotion.
  • wavepay_registerRegister a WavePay merchant account.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Register a WavePay merchant account. Returns a live merchant key (key) and a test-mode key (testKey) once — save both; only their hashes are stored. Free tier: 25 payments per 30 days; test mode is uncapped and never reaches a provider.
  • wavepay_subscribeOpen a subscription for a customer (needs a merchant key; a mk_test_ key previews it with fake money).Can send data outNo findings

    Why it is in this group

    • The name "wavepay_subscribe" says "subscribe": a word for a change.

    What it can reach

    • outboundThe input takes a destination (input.phone): what the tool writes goes there.
    Description, as the server wrote it
    Open a subscription for a customer (needs a merchant key; a mk_test_ key previews it with fake money). collection=automatic charges a saved card or PayPal subscription; invoice_and_remind (default, and the only mode for mobile wallets) sends a payment request each period. Returns the first checkout to hand the buyer.
  • wavepay_test_billing_runTest mode only (mk_test_ key): run the billing engine as if advanceDays had passed, so renewals, instalments and dunning can be exercised without waiting.No findings

    Why it is in this group

    • The name "wavepay_test_billing_run" says "run": a word for a change.
    Description, as the server wrote it
    Test mode only (mk_test_ key): run the billing engine as if advanceDays had passed, so renewals, instalments and dunning can be exercised without waiting.
Only reads 1Show 1 read-only tool
  • wavepay_providersList the payment rails this deployment can take — PayNow (EcoCash, OneMoney, InnBucks, Telecash, O'mari, ZimSwitch, cards) and PayPal.No findings

    Why it is in this group

    • The description's first verb is "list": a word for reading.
    Description, as the server wrote it
    List the payment rails this deployment can take — PayNow (EcoCash, OneMoney, InnBucks, Telecash, O'mari, ZimSwitch, cards) and PayPal.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out2
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:11 UTC, unchanged since Nov 6, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
10
Protocol version
2025-03-26
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://t3rnel-wavepay-production.t3ratech.workers.dev/.well-known/oauth-protected-resource
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 10 tools that change things (1 irreversible, 9 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://t3rnel-wavepay-production.t3ratech.workers.dev/mcp: tools/list returned 11 tools to an anonymous client, including wavepay_refund (irreversible), wavepay_register (write), wavepay_pricing (write), wavepay_checkout (write), wavepay_checkout_status (write) and 5 more

    What this check looks for

Posture changes

  1. Nov 6, 2026
    • Tools that change things, listed without credentials: 5 to 10
    • RFC 9728 protected resource metadata: none to https://t3rnel-wavepay-production.t3ratech.workers.dev/.well-known/oauth-protected-resource

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools5 added, 2 changed.+5 added~2 changedView diff
  2. PostureRemote posture changed. Tools that change things, listed without credentials: 5 -> 10; RFC 9728 protected resource metadata: none -> https://t3rnel-wavepay-production.t3ratech.workers.dev/.well-known/oauth-protected-resource.View diff
    • Tools that change things, listed without credentials: 5 to 10
    • RFC 9728 protected resource metadata: none to https://t3rnel-wavepay-production.t3ratech.workers.dev/.well-known/oauth-protected-resource

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__wavepay__wavepay_providers"
    ],
    "ask": [
      "mcp__wavepay__wavepay_register",
      "mcp__wavepay__wavepay_pricing",
      "mcp__wavepay__wavepay_checkout",
      "mcp__wavepay__wavepay_checkout_status",
      "mcp__wavepay__wavepay_features",
      "mcp__wavepay__wavepay_subscribe",
      "mcp__wavepay__wavepay_bnpl",
      "mcp__wavepay__wavepay_refund",
      "mcp__wavepay__wavepay_test_billing_run",
      "mcp__wavepay__wavepay_catalog"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as wavepay. Review it before you use it.

Capability tags behind 2 rules
  • mcp__wavepay__wavepay_checkout outbound
  • mcp__wavepay__wavepay_subscribe outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.t3ratech/wavepay/verify?hash=1f20d96f63ab925dc9d5799d998224358b2163fc97a82a350b8ee055d0aa718c" | jq -e '.changed == false'

Pinned hash 1f20d96f63ab, from Nov 21, 2026, 04:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.t3ratech/wavepay/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.t3ratech/wavepay
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.t3ratech/wavepay.svg)](https://radar.anlyon.com/servers/io.github.t3ratech/wavepay)

Source: MCP Registry. Synced Oct 21, 2026, 18:50 UTC.

WavePay Payments MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the WavePay Payments MCP server safe?

No scan can promise that. What its definitions show: 11 tools, 10 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the WavePay Payments MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the WavePay Payments MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: wavepay_refund.

What tools does the WavePay Payments MCP server have?

11 tools: 1 irreversible, 9 write, 1 read. wavepay_refund, wavepay_register, wavepay_pricing, wavepay_checkout, wavepay_checkout_status, wavepay_features, wavepay_subscribe, wavepay_bnpl and 3 more.

Does the WavePay Payments MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the WavePay Payments MCP server send data to outside services?

2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): wavepay_checkout and wavepay_subscribe.

Has the WavePay Payments MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 7, 2026. Every change is on this page and in its Atom feed.