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
260 ms
Tools exposed
16 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
7Maps, the live directory of MCP servers, run by 7IT Solutions: which work today, what changed.
Listing
From the official MCP registry (active).
Recent checks of 7Maps
CheckedResultHandshake
1 hour agoHandshake completed260 ms
3 days agoHandshake completed163 ms
13 days agoHandshake completed148 ms
14 days agoHandshake completed440 ms
15 days agoHandshake completed430 ms
16 days agoHandshake completed232 ms
18 days agoHandshake completed242 ms
18 days agoHandshake completed283 ms
19 days agoHandshake completed223 ms
21 days agoHandshake completed243 ms
22 days agoHandshake completed236 ms
25 days agoHandshake completed205 ms
27 days agoHandshake completed261 ms
30 days agoHandshake completed253 ms

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

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.