Wheremind
REMOTE · WHEREMIND.AI
Hosted MCP for live place search, geocoding & turn-by-turn routes. No Maps API key to manage.
Available components
Last scanned (4 hours ago)
Scores higher than 87% of remote servers
Reachable. Last reached 17 Oct 2026.
Category Maps and Location
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability67
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1028 tokens (~205/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage85
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 55% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Oct 26 +39
- Transport: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Authorization: Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. security
- MCP protocol: unverified → pass ▲ functional
- Stability: unverified → 0.07 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 55 functional
- First check of Schema quality: excellent functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: fail functional
- 6 Oct 26 38
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 17 Oct 2026 · Probed https://wheremind.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=wheremind.ai | CN=WE1,O=Google Trust Services,C=US | 20 Sept 2026 | 19 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d58ff4238e24077e0e09720a22af73ad |
| SANs: wheremind.ai, www.wheremind.ai, *.www.wheremind.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of wheremind.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| wheremind.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer error="invalid_token", resource_metadata="https://wheremind.ai/.well-known/oauth-protected-resource/mcp", scope="mcp"
Bearer error="invalid_token", resource_metadata="https://wheremind.ai/.well-known/oauth-protected-resource/mcp", scope="mcp"| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
Protected resource metadata
| Document | https://wheremind.ai/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://wheremind.ai/mcp |
| Authorisation server | https://wheremind.ai |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://wheremind.ai/mcp | Verified | 200 | |
| http (plaintext) | http://wheremind.ai/mcp | HTTPS enforced | 301 | https://invite.wheremind.ai/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
directions Directions / routes ~237
Compute a route from origin to destination by DRIVE, WALK, BICYCLE, TRANSIT, or TWO_WHEELER. Use when the user asks how to get somewhere, how far it is, or how long it takes. Origin and destination may be an address string, "lat,lng", or an object with place_id. Returns total duration and distance, an encoded polyline, and per-leg turn-by-turn steps (maneuver, instruction text, distance, duration, start/end lat/lng).
| Name | Type | Req | Description |
|---|---|---|---|
| alternatives | boolean | – | – |
| destination | – | yes | Address string, 'lat,lng', or {address|place_id|latitude,longitude} |
| field_mask | string | – | Optional Routes X-Goog-FieldMask override. Default includes turn-by-turn navigationInstruction without Pro fields (localizedValues, travelAdvisory). |
| intermediates | array | – | – |
| language_code | string | – | – |
| origin | – | yes | Address string, 'lat,lng', or {address|place_id|latitude,longitude} |
| travel_mode | string | – | DRIVE, WALK, BICYCLE, TRANSIT, TWO_WHEELER |
No output schema declared.
No examples provided.
geocode Geocode ~145
Convert an address to lat/lng (forward: pass address), or lat/lng to an address (reverse: pass latitude and longitude). Use when the user needs coordinates or a normalized address, or before places_nearby. To find businesses use places_search_text; directions accepts addresses directly, so geocoding first is not required. Returns formatted address, lat/lng, place_id, types, and plus code.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Address to forward-geocode |
| field_mask | string | – | – |
| language_code | string | – | – |
| latitude | number | – | Latitude for reverse geocode |
| longitude | number | – | Longitude for reverse geocode |
No output schema declared.
No examples provided.
places_details Place details ~106
Get details for one known place by place_id (from places_search_text or places_nearby). Use when the user asks for a specific place's phone number, website, opening hours, or rating. Returns name, formatted address, lat/lng, rating, opening hours, phone, website, and attributions.
| Name | Type | Req | Description |
|---|---|---|---|
| field_mask | string | – | – |
| language_code | string | – | – |
| place_id | string | yes | Place id, with or without the places/ prefix |
No output schema declared.
No examples provided.
places_nearby Places nearby search ~180
List places within a radius (meters) of a lat/lng you already have, such as the user's location or a geocode result, optionally filtered by Places types (e.g. ["restaurant"]) and ranked by DISTANCE or POPULARITY. For free-text, name, or city queries use places_search_text instead. Returns place_id, name, formatted address, lat/lng, types, rating, opening hours, and attributions.
| Name | Type | Req | Description |
|---|---|---|---|
| field_mask | string | – | – |
| included_types | array | – | Places types, e.g. ["restaurant"] |
| language_code | string | – | – |
| latitude | number | yes | – |
| longitude | number | yes | – |
| max_result_count | integer | – | – |
| radius | number | yes | Circle radius in meters |
| rank_preference | string | – | DISTANCE or POPULARITY |
No output schema declared.
No examples provided.
places_search_text Places text search ~210
Find places by free text: a business name, a category, or "X in/near Y" (e.g. "coffee in Porto", "pharmacies near Lisbon Oriente"). Default choice for finding places. Use places_nearby only when you already have exact coordinates. Returns up to 20 places, each with place_id, name, formatted address, lat/lng, types, rating, opening hours (open_now and weekly hours), and attributions. Pass a place_id to places_details for phone or website.
| Name | Type | Req | Description |
|---|---|---|---|
| field_mask | string | – | – |
| included_type | string | – | Optional Places type filter |
| language_code | string | – | – |
| latitude | number | – | Optional location bias latitude |
| longitude | number | – | Optional location bias longitude |
| max_result_count | integer | – | 1-20 |
| query | string | yes | Free-text query, e.g. 'coffee in Austin' |
| radius | number | – | Optional location bias radius in meters |
No output schema declared.
No examples provided.
How do I install the Wheremind MCP server?
Wheremind is a hosted endpoint at https://wheremind.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · wheremind.ai
claude mcp add --transport http ai-wheremind-wheremind 'https://wheremind.ai/mcp'
What is the Wheremind MCP server?
Wheremind is an MCP server listed in the public MCP registry as ai.wheremind/wheremind. Hosted MCP for live place search, geocoding & turn-by-turn routes. No Maps API key to manage. This page covers its hosted endpoint (https://wheremind.ai/mcp).
Is the Wheremind MCP server safe to use?
Wheremind scores 81 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Wheremind MCP server expose?
Wheremind exposes 5 tools: places_search_text, places_nearby, places_details, geocode, directions. Their descriptions and schemas cost roughly 878 tokens of context every time the server is loaded.
Does the Wheremind MCP server require authentication?
Yes. Wheremind asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Wheremind MCP server still maintained?
Wheremind is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.