Remote MCP · Endpoint

7Maps MCP server

No. 7Maps answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://7it.co.il/7maps/mcp?via=registry

The last check completed an MCP handshake.

Registry name
io.github.XLSV777/7maps
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
236 ms
Tools exposed
15 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
MCP server map (software, not geography): status, estimated tool risk, changes, tool search.
Listing
From the official MCP registry (active).
Recent checks of 7Maps
CheckedResultHandshake
1 hour agoHandshake completed236 ms
2 days agoHandshake completed205 ms
5 days agoHandshake completed261 ms
7 days agoHandshake completed253 ms
9 days agoHandshake completed178 ms
11 days agoHandshake completed303 ms
13 days agoHandshake completed262 ms
15 days agoHandshake completed254 ms
17 days agoHandshake completed429 ms
18 days agoHandshake completed387 ms
20 days agoHandshake completed176 ms
21 days agoHandshake completed308 ms
23 days agoHandshake completed184 ms
25 days agoHandshake completed473 ms

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

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 7Maps and makes no claim about it beyond what these checks measured.