# Wheremind (remote · wheremind.ai)

Hosted MCP for live place search, geocoding & turn-by-turn routes. No Maps API key to manage.

- Trust score: 81/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-17

## Components

- remote · `wheremind.ai`: 81/100 (this document), [markdown](https://verifymcp.io/servers/ai-wheremind-wheremind/wheremind.md), [page](https://verifymcp.io/servers/ai-wheremind-wheremind/wheremind)

## Channel facts

- Endpoint: `https://wheremind.ai/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-17.

- **Endpoint Security**: 94/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 85/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 55% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http ai-wheremind-wheremind 'https://wheremind.ai/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ai-wheremind-wheremind": {
      "url": "https://wheremind.ai/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ai-wheremind-wheremind": {
      "type": "http",
      "url": "https://wheremind.ai/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ai-wheremind-wheremind]
url = "https://wheremind.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-wheremind-wheremind": {
      "type": "remote",
      "url": "https://wheremind.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-wheremind-wheremind --url 'https://wheremind.ai/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-wheremind-wheremind:
    url: "https://wheremind.ai/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ai-wheremind-wheremind": {
      "Transport": "http",
      "Url": "https://wheremind.ai/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-wheremind-wheremind -t streamable-http -u 'https://wheremind.ai/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ai-wheremind-wheremind": {
      "type": "http",
      "url": "https://wheremind.ai/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-17 (score 81, +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.

### 2026-10-15 (score 80, +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.

### 2026-10-13 (score 79, +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.

### 2026-10-11 (score 78, +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.

### 2026-10-10 (score 77, +39)

- [security improvement] Transport: unverified → pass
- [security improvement] 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.
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Stability: unverified → 0.07
- [functional improvement] 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

### 2026-10-06 (score 38)

First indexed and scored.

## MCP tools (5)

### `places_search_text` (~210 tokens)

Places text search

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.

Input parameters:

- `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, required): Free-text query, e.g. 'coffee in Austin'
- `radius` (number): Optional location bias radius in meters

### `places_nearby` (~180 tokens)

Places nearby search

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.

Input parameters:

- `field_mask` (string)
- `included_types` (array): Places types, e.g. ["restaurant"]
- `language_code` (string)
- `latitude` (number, required)
- `longitude` (number, required)
- `max_result_count` (integer)
- `radius` (number, required): Circle radius in meters
- `rank_preference` (string): DISTANCE or POPULARITY

### `places_details` (~106 tokens)

Place details

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.

Input parameters:

- `field_mask` (string)
- `language_code` (string)
- `place_id` (string, required): Place id, with or without the places/ prefix

### `geocode` (~145 tokens)

Geocode

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.

Input parameters:

- `address` (string): Address to forward-geocode
- `field_mask` (string)
- `language_code` (string)
- `latitude` (number): Latitude for reverse geocode
- `longitude` (number): Longitude for reverse geocode

### `directions` (~237 tokens)

Directions / routes

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).

Input parameters:

- `alternatives` (boolean)
- `destination` (required): 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` (required): Address string, 'lat,lng', or {address|place_id|latitude,longitude}
- `travel_mode` (string): DRIVE, WALK, BICYCLE, TRANSIT, TWO_WHEELER

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-wheremind-wheremind/wheremind#diagnostics

## Score history

- 2026-10-17: 81
- 2026-10-16: 80
- 2026-10-15: 80
- 2026-10-14: 79
- 2026-10-13: 79
- 2026-10-12: 78
- 2026-10-11: 78
- 2026-10-10: 77
- 2026-10-07: 38
- 2026-10-06: 38

## Common questions

### 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.

## Links

- Remote endpoint: https://wheremind.ai/mcp
- Website: https://wheremind.ai/
- Changelog RSS feed: https://verifymcp.io/servers/ai-wheremind-wheremind/wheremind.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-wheremind-wheremind/wheremind.json
- HTML version of this page: https://verifymcp.io/servers/ai-wheremind-wheremind/wheremind