Remote MCP · Endpoint
gate402 merchant checkout MCP server
Yes, as of 1 hour ago: the response was not JSON-RPC.
DownLast checked 1 hour ago
Server URL
https://api.ogenalabs.com/api/gate402/mcp
The last check failed: the response was not JSON-RPC.
- Registry name
- com.ogenalabs/gate402-x402
- Transport
- Streamable HTTP
- Protocol negotiated
- Not measured yet
- Handshake latency
- —
- Tools exposed
- 2 tools
- Uptime, last 30 days
- 78.9% from 19 checks
- Described by its publisher as
- Drop-in x402 checkout for merchants: issue terms, verify payment. $0.01 each.
- Repository
- https://github.com/OgenaLabs/gate402-mcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Failed - the response was not JSON-RPC | — |
| 18 hours ago | Failed - the response was not JSON-RPC | — |
| 2 days ago | Failed - the response was not JSON-RPC | — |
| 3 days ago | Failed - the response was not JSON-RPC | — |
| 4 days ago | Handshake completed | 196 ms |
| 5 days ago | Handshake completed | 69 ms |
| 6 days ago | Handshake completed | 138 ms |
| 7 days ago | Handshake completed | 174 ms |
| 10 days ago | Handshake completed | 92 ms |
| 13 days ago | Handshake completed | 122 ms |
| 15 days ago | Handshake completed | 86 ms |
| 17 days ago | Handshake completed | 96 ms |
| 19 days ago | Handshake completed | 72 ms |
| 21 days ago | Handshake completed | 83 ms |
| 23 days ago | Handshake completed | 68 ms |
| 25 days ago | Handshake completed | 59 ms |
| 27 days ago | Handshake completed | 81 ms |
| 28 days ago | Handshake completed | 63 ms |
| 29 days ago | Handshake completed | 310 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 26 responding of 30.
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 gate402 merchant checkout and makes no claim about it beyond what these checks measured.