Remote MCP · Endpoint

Wheremind MCP server

No. Wheremind answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://wheremind.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.wheremind/wheremind
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
2.71 s
Tools exposed
5 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Hosted MCP for live place search, geocoding & turn-by-turn routes. No Maps API key to manage.
Website
https://wheremind.ai/
Listing
From the official MCP registry (active).
Recent checks of Wheremind
CheckedResultHandshake
1 hour agoHandshake completed2.71 s
2 days agoHandshake completed123 ms
5 days agoHandshake completed74 ms
7 days agoHandshake completed124 ms
9 days agoHandshake completed94 ms
11 days agoHandshake completed115 ms
13 days agoHandshake completed146 ms
15 days agoHandshake completed202 ms
17 days agoHandshake completed68 ms
19 days agoHandshake completed62 ms
20 days agoHandshake completed130 ms
21 days agoCredentials required—
23 days agoCredentials required—

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with Wheremind and makes no claim about it beyond what these checks measured.