Remote MCP · Endpoint
Remap MCP server
No. Remap answered an MCP handshake 5 hours ago.
UpLast checked 5 hours ago
Server URL
https://go.remap.earth/mcp
The last check completed an MCP handshake.
- Registry name
- earth.remap/routes
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 164 ms
- Tools exposed
- 2 tools
- Uptime, last 30 days
- 100% from 13 checks
- Described by its publisher as
- Remap generates routes for cycling, running and walking anywhere on Earth.
- Website
- https://remap.earth/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 5 hours ago | Handshake completed | 164 ms |
| 3 days ago | Handshake completed | 130 ms |
| 12 days ago | Handshake completed | 274 ms |
| 12 days ago | Handshake completed | 128 ms |
| 14 days ago | Handshake completed | 205 ms |
| 15 days ago | Handshake completed | 166 ms |
| 16 days ago | Handshake completed | 188 ms |
| 17 days ago | Handshake completed | 196 ms |
| 18 days ago | Handshake completed | 157 ms |
| 19 days ago | Handshake completed | 158 ms |
| 22 days ago | Handshake completed | 156 ms |
| 25 days ago | Handshake completed | 253 ms |
| 27 days ago | Handshake completed | 202 ms |
The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 13 responding of 13.
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 Remap and makes no claim about it beyond what these checks measured.