Remote MCP · Endpoint
LatLong Maps MCP server
No. LatLong Maps answered an MCP handshake 2 hours ago.
UpLast checked 2 hours ago
Server URL
https://geocp.latlong.ai/mcp/
The last check completed an MCP handshake.
- Registry name
- ai.latlong/map-mcp
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 820 ms
- Tools exposed
- 5 tools
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- Turn CSV or Excel data into styled choropleth and categorical maps of India from plain language.
- Website
- https://latlong.ai/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Handshake completed | 820 ms |
| 1 day ago | Handshake completed | 845 ms |
| 3 days ago | Handshake completed | 891 ms |
| 3 days ago | Handshake completed | 868 ms |
| 4 days ago | Handshake completed | 846 ms |
| 5 days ago | Handshake completed | 837 ms |
| 7 days ago | Handshake completed | 846 ms |
| 10 days ago | Handshake completed | 862 ms |
| 12 days ago | Handshake completed | 868 ms |
| 15 days ago | Handshake completed | 899 ms |
| 17 days ago | Handshake completed | 892 ms |
| 19 days ago | Handshake completed | 882 ms |
| 21 days ago | Handshake completed | 827 ms |
| 23 days ago | Handshake completed | 852 ms |
| 25 days ago | Handshake completed | 850 ms |
| 26 days ago | Handshake completed | 828 ms |
| 28 days ago | Handshake completed | 855 ms |
| 29 days ago | Handshake completed | 881 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 29 responding of 29.
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 LatLong Maps and makes no claim about it beyond what these checks measured.