Remote MCP · Endpoint

WavePay Payments MCP server

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

UpLast checked 2 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
113 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 15 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
2 hours agoHandshake completed113 ms
2 days agoHandshake completed117 ms
4 days agoHandshake completed123 ms
6 days agoHandshake completed401 ms
8 days agoHandshake completed108 ms
10 days agoHandshake completed79 ms
12 days agoHandshake completed103 ms
13 days agoHandshake completed127 ms
14 days agoHandshake completed408 ms
16 days agoHandshake completed66 ms
18 days agoHandshake completed81 ms
20 days agoHandshake completed67 ms
21 days agoHandshake completed64 ms
23 days agoHandshake completed95 ms
24 days agoHandshake completed73 ms

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

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.