Remote MCP · Endpoint
app.netlify.micropay-test-suite/micropay-test-suite MCP server
No. app.netlify.micropay-test-suite/micropay-test-suite answered an MCP handshake 11 hours ago.
UpLast checked 11 hours ago
Server URL
https://micropay-test-suite.netlify.app/api/mcp
The last check completed an MCP handshake.
- Registry name
- app.netlify.micropay-test-suite/micropay-test-suite
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 2.54 s
- Tools exposed
- 1 tool
- Uptime, last 30 days
- 70.6% from 17 checks
- Described by its publisher as
- Verify your agent's x402 payment flow for free on Base Sepolia testnet before real money moves.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 11 hours ago | Handshake completed | 2.54 s |
| 2 days ago | Handshake completed | 176 ms |
| 4 days ago | Handshake completed | 292 ms |
| 6 days ago | Handshake completed | 153 ms |
| 7 days ago | Handshake completed | 205 ms |
| 8 days ago | Handshake completed | 143 ms |
| 9 days ago | Handshake completed | 227 ms |
| 12 days ago | Handshake completed | 151 ms |
| 14 days ago | Handshake completed | 200 ms |
| 15 days ago | Handshake completed | 247 ms |
| 16 days ago | Handshake completed | 2.26 s |
| 18 days ago | Handshake completed | 324 ms |
| 19 days ago | Failed - the server returned an HTTP error | — |
| 19 days ago | Failed - the server returned an HTTP error | — |
| 20 days ago | Failed - the server returned an HTTP error | — |
| 21 days ago | Failed - the server returned an HTTP error | — |
| 23 days ago | Failed - the server returned an HTTP error | — |
The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 12 responding of 17.
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 app.netlify.micropay-test-suite/micropay-test-suite and makes no claim about it beyond what these checks measured.