WavePay Payments
REMOTE · T3RNEL-WAVEPAY-PRODUCTION.T3RATECH.WORKERS.DEV · SCANNED SEP 29
Payments MCP: self-serve merchant key, PayNow + PayPal checkouts.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 338 tokens (~56/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage74
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 22% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
How do I install the WavePay Payments MCP server?
WavePay Payments is a hosted endpoint at https://t3rnel-wavepay-production.t3ratech.workers.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · t3rnel-wavepay-production.t3ratech.workers.dev
claude mcp add --transport http t3ratech-wavepay 'https://t3rnel-wavepay-production.t3ratech.workers.dev/mcp'
{
"mcpServers": {
"t3ratech-wavepay": {
"url": "https://t3rnel-wavepay-production.t3ratech.workers.dev/mcp"
}
}
} {
"servers": {
"t3ratech-wavepay": {
"type": "http",
"url": "https://t3rnel-wavepay-production.t3ratech.workers.dev/mcp"
}
}
} [mcp_servers.t3ratech-wavepay] url = "https://t3rnel-wavepay-production.t3ratech.workers.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"t3ratech-wavepay": {
"type": "remote",
"url": "https://t3rnel-wavepay-production.t3ratech.workers.dev/mcp",
"enabled": true
}
}
} openclaw mcp add t3ratech-wavepay --url 'https://t3rnel-wavepay-production.t3ratech.workers.dev/mcp' --transport streamable-http
mcp_servers:
t3ratech-wavepay:
url: "https://t3rnel-wavepay-production.t3ratech.workers.dev/mcp" {
"McpServers": {
"t3ratech-wavepay": {
"Transport": "http",
"Url": "https://t3rnel-wavepay-production.t3ratech.workers.dev/mcp"
}
}
} assistant mcp add t3ratech-wavepay -t streamable-http -u 'https://t3rnel-wavepay-production.t3ratech.workers.dev/mcp'
{
"mcpServers": {
"t3ratech-wavepay": {
"type": "http",
"url": "https://t3rnel-wavepay-production.t3ratech.workers.dev/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 61
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 29 Sept 2026 · Probed https://t3rnel-wavepay-production.t3ratech.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=t3ratech.workers.dev | CN=WE1,O=Google Trust Services,C=US | 13 Aug 2026 | 11 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 1bc813ff8fe100710ed7be55f0f59b03 |
| SANs: t3ratech.workers.dev, *.t3ratech.workers.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of t3rnel-wavepay-production.t3ratech.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://t3rnel-wavepay-production.t3ratech.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://t3rnel-wavepay-production.t3ratech.workers.dev/mcp | HTTPS enforced | 308 | https://t3rnel-wavepay-production.t3ratech.workers.dev/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
wavepay_catalog ~49
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
wavepay_checkout ~68
Start a checkout for a product/plan on a rail; returns the hosted checkoutUrl to hand the buyer.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | – | |
| phone | string | – | – |
| planId | string | yes | – |
| productId | string | yes | – |
| provider | string | yes | – |
No output schema declared.
No examples provided.
wavepay_checkout_status ~29
Poll a payment by reference: pending | collected | expired.
| Name | Type | Req | Description |
|---|---|---|---|
| reference | string | yes | – |
No output schema declared.
No examples provided.
wavepay_pricing ~34
Live plans and prices for a product, per rail, with the active promotion.
| Name | Type | Req | Description |
|---|---|---|---|
| productId | string | yes | – |
No output schema declared.
No examples provided.
wavepay_providers ~49
List the payment rails this deployment can take — PayNow (EcoCash, OneMoney, InnBucks, Telecash, O'mari, ZimSwitch, cards) and PayPal.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
wavepay_register ~65
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.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Merchant or product name |
| ownerEmail | string | yes | Owner contact address |
No output schema declared.
No examples provided.
What is the WavePay Payments MCP server?
WavePay Payments is an MCP server listed in the public MCP registry as io.github.t3ratech/wavepay. Payments MCP: self-serve merchant key, PayNow + PayPal checkouts. This page covers its hosted endpoint (https://t3rnel-wavepay-production.t3ratech.workers.dev/mcp).
Is the WavePay Payments MCP server safe to use?
WavePay Payments scores 62 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the WavePay Payments MCP server expose?
WavePay Payments exposes 6 tools: wavepay_register, wavepay_providers, wavepay_pricing, wavepay_checkout, wavepay_checkout_status, wavepay_catalog. Their descriptions and schemas cost roughly 294 tokens of context every time the server is loaded.
Does the WavePay Payments MCP server require authentication?
No. We connected to WavePay Payments without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the WavePay Payments MCP server still maintained?
WavePay Payments is still listed as active in the MCP registry. We last reached this channel on 29 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.