Remote MCP · Endpoint

RewindMap MCP server

No. RewindMap answered an MCP handshake 20 minutes ago.

UpLast checked 20 minutes 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
236 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 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
20 minutes agoHandshake completed236 ms
9 days agoHandshake completed166 ms
9 days agoHandshake completed82 ms
11 days agoHandshake completed168 ms
12 days agoHandshake completed234 ms
13 days agoHandshake completed502 ms
14 days agoHandshake completed144 ms
15 days agoHandshake completed144 ms
16 days agoHandshake completed72 ms
19 days agoHandshake completed161 ms
21 days agoHandshake completed121 ms
24 days agoHandshake completed92 ms
26 days agoHandshake completed171 ms
28 days agoHandshake completed168 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 27 responding of 27.

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.