Remote MCP · Endpoint
app.vercel.ora-x402-gateway/sensations-mergulho MCP server
No. app.vercel.ora-x402-gateway/sensations-mergulho answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://ywabnlhkmhbyewqhbsjm.supabase.co/functions/v1/sensations-mergulho
The last check completed an MCP handshake.
- Registry name
- app.vercel.ora-x402-gateway/sensations-mergulho
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-03-26
- Handshake latency
- 182 ms
- Tools exposed
- 7 tools
- Uptime, last 30 days
- 61.1% from 18 checks
- Described by its publisher as
- MCP server for 0001SENSATIONS: 107-level textual descent, append-only trace logging
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 182 ms |
| 1 day ago | Handshake completed | 265 ms |
| 3 days ago | Handshake completed | 121 ms |
| 3 days ago | Handshake completed | 143 ms |
| 4 days ago | Handshake completed | 211 ms |
| 5 days ago | Handshake completed | 247 ms |
| 7 days ago | Handshake completed | 195 ms |
| 10 days ago | Handshake completed | 231 ms |
| 12 days ago | Handshake completed | 150 ms |
| 14 days ago | Handshake completed | 234 ms |
| 17 days ago | Handshake completed | 460 ms |
| 19 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 | — |
| 25 days ago | Failed - the server returned an HTTP error | — |
| 26 days ago | Failed - the server returned an HTTP error | — |
| 28 days ago | Failed - the server returned an HTTP error | — |
| 29 days ago | Failed - the server returned an HTTP error | — |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 16 responding of 29.
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.vercel.ora-x402-gateway/sensations-mergulho and makes no claim about it beyond what these checks measured.