Remote MCP · Endpoint

WavePay Payments MCP server

No. WavePay Payments answered an MCP handshake 6 hours ago.

UpLast checked 6 hours ago

Server URL

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

The last check completed an MCP handshake.

Registry name
io.github.t3ratech/wavepay
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
86 ms
Tools exposed
11 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Payments MCP: self-serve merchant key, PayNow + PayPal checkouts.
Listing
From the official MCP registry (active).
Recent checks of WavePay Payments
CheckedResultHandshake
6 hours agoHandshake completed86 ms
9 days agoHandshake completed196 ms
10 days agoHandshake completed128 ms
11 days agoHandshake completed104 ms
12 days agoHandshake completed95 ms
14 days agoHandshake completed99 ms
15 days agoHandshake completed107 ms
15 days agoHandshake completed96 ms
17 days agoHandshake completed130 ms
19 days agoHandshake completed117 ms
22 days agoHandshake completed110 ms
24 days agoHandshake completed113 ms
26 days agoHandshake completed117 ms
28 days agoHandshake completed123 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 26 responding of 26.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with WavePay Payments and makes no claim about it beyond what these checks measured.