Remote MCP · Endpoint

RewindMap MCP server

No. RewindMap answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://rewindmap.com/mcp

The last check completed an MCP handshake.

Registry name
com.rewindmap/rewindmap
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
171 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Historical borders and dated map events with source attribution and coverage limits.
Listing
From the official MCP registry (active).
Recent checks of RewindMap
CheckedResultHandshake
1 hour agoHandshake completed171 ms
2 days agoHandshake completed168 ms
4 days agoHandshake completed203 ms
6 days agoHandshake completed55 ms
8 days agoHandshake completed32 ms
9 days agoHandshake completed35 ms
11 days agoHandshake completed45 ms
12 days agoHandshake completed296 ms
13 days agoHandshake completed32 ms
16 days agoHandshake completed31 ms
17 days agoHandshake completed69 ms
19 days agoHandshake completed30 ms
20 days agoHandshake completed184 ms
22 days agoHandshake completed151 ms
23 days agoHandshake completed110 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 RewindMap and makes no claim about it beyond what these checks measured.