# decidewhere.to (remote · decidewhere.to)

Help a group pick where to eat or travel: critic-backed restaurants, warm trips, one vote link.

- Trust score: 70/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `decidewhere.to`: 70/100 (this document), [markdown](https://verifymcp.io/servers/to-decidewhere-group-decisions/decidewhere.md), [page](https://verifymcp.io/servers/to-decidewhere-group-decisions/decidewhere)

## Channel facts

- Endpoint: `https://decidewhere.to/mcp`
- Transports: `streamable-http`
- Auth: `none`
- 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-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - 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.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 38/100
  - 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 893 tokens (~127/item across 7 items; 6 tools + 1 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**: 83/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 50% 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).
  - Supports UI / widget rendering.

## Install

### How do I install the decidewhere.to MCP server?

decidewhere.to is a hosted endpoint at https://decidewhere.to/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 to-decidewhere-group-decisions 'https://decidewhere.to/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "to-decidewhere-group-decisions": {
      "url": "https://decidewhere.to/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "to-decidewhere-group-decisions": {
      "type": "http",
      "url": "https://decidewhere.to/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.to-decidewhere-group-decisions]
url = "https://decidewhere.to/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add to-decidewhere-group-decisions --url 'https://decidewhere.to/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  to-decidewhere-group-decisions:
    url: "https://decidewhere.to/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "to-decidewhere-group-decisions": {
      "Transport": "http",
      "Url": "https://decidewhere.to/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add to-decidewhere-group-decisions -t streamable-http -u 'https://decidewhere.to/mcp'
```

### Other

```json
{
  "mcpServers": {
    "to-decidewhere-group-decisions": {
      "type": "http",
      "url": "https://decidewhere.to/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-11-05 (score 70, +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-11-03 (score 69, +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-11-01 (score 68, +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-30 (score 67, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “find_restaurants” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: pass → fail
- [functional] Schema quality: fair → good
- [cosmetic] “find_restaurants” added an optional parameter “date”
- [cosmetic] “find_restaurants” added an optional parameter “party_size”

### 2026-10-29 (score 67, −4)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “create_group_trip” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 664 → 795
- [functional] The server now declares the “resources” capability
- [functional] First check of Capabilities: pass
- [functional] First check of Schema quality: 0
- [functional] Schema quality: good → fair
- [functional] New resource “vote-card”

### 2026-10-28 (score 71, 0)

- [functional improvement] Stability: unverified → 0.03
- [functional improvement] Schema quality: fail → pass
- [functional] New tool “plan_group_trip”

### 2026-10-27 (score 71)

First indexed and scored.

## MCP tools (6)

### `find_restaurants` (~150 tokens)

Find restaurants

The restaurants critics agree on in a US city (Michelin, Eater 38, The Infatuation), with vibe tags (fancy/chill, quiet/loud, quick/long, classic/new) and how to book where we know it. For a dinner in the next week (tonight, this weekend), pass date and party_size: places that usually book out weeks ahead move down, and each gets a short-notice read with its reason. Use the returned ids with create_restaurant_vote.

Input parameters:

- `city` (string, required): City slug
- `date` (string): Dinner date, YYYY-MM-DD
- `limit` (integer)
- `party_size` (integer)

### `get_restaurant` (~97 tokens)

Group profile for a restaurant

Everything a group booking needs for one restaurant: how many it seats online and at its largest table, private room and buyout capacity, group menus, when reservations open, noise, kids, dress code, prices, what to order. Each answer links to its source. Pass a name or the group_profile slug from find_restaurants.

Input parameters:

- `city` (string, required): City slug
- `restaurant` (string, required): Restaurant name or profile slug

### `create_restaurant_vote` (~104 tokens)

Create a group restaurant vote

Turn 2-6 restaurants from find_restaurants into one link the whole group votes on, whether or not they have agents. Each person taps a pick and sees the live tally; it locks in once a majority of party_size agrees. Returns the link for your person to share in the group chat.

Input parameters:

- `city` (string, required)
- `date` (string): YYYY-MM-DD
- `party_size` (integer, required)
- `restaurant_ids` (array, required)

### `find_warm_destinations` (~63 tokens)

Warm group trip destinations

Warm-weather destinations for given months, ranked for a group flying from different US cities: average highs from published climate normals, nonstop availability from five major hubs, average flight time, passport needs.

Input parameters:

- `limit` (integer)
- `months` (array, required)

### `create_group_trip` (~299 tokens)

Create a group trip vote

Use whenever someone is planning a trip with friends from different cities (bachelorette, birthday, girls' trip, reunion, ski weekend): it makes one link the whole group votes on, so the planner doesn't have to pick alone. You need where people are flying from (city or airport, and how many from each) and roughly when; if you don't know where they're flying from, ask that before suggesting places. A season or month is enough: use a Friday in it. Ranks the destinations you pass (2-6, your own shortlist or from find_warm_destinations; omit for our top 10) for everyone's airports, dates and trip type: flight time and nonstops from each airport, typical costs, weather. Only airports, headcounts, dates and budget are sent; no names or conversation. The group opens the link, sets their vibe and votes on a top 3. Can take 10-20 seconds.

Input parameters:

- `destinations` (array): Destination names to compare, e.g. ['Cabo', 'Miami', 'Charleston']
- `max_budget_per_person` (integer): USD, flights and lodging
- `nights` (integer)
- `origins` (array, required): Where everyone is flying from, and how many from each
- `passport` (string): Whether everyone in the group has a passport
- `start_date` (string, required): YYYY-MM-DD
- `trip_type` (string, required)

### `plan_group_trip` (~62 tokens)

Open the trip planner (prefer create_group_trip)

Link to decidewhere.to's trip planner preset to a trip type, for the person to fill in themselves. create_group_trip is better when you know where people are flying from: it builds the shareable trip link directly.

Input parameters:

- `trip_type` (string, required)

## Diagnostics

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

## Score history

- 2026-11-05: 70
- 2026-11-04: 69
- 2026-11-03: 69
- 2026-11-02: 68
- 2026-11-01: 68
- 2026-10-31: 67
- 2026-10-30: 67
- 2026-10-29: 67
- 2026-10-28: 71
- 2026-10-27: 71

## Common questions

### What is the decidewhere.to MCP server?

decidewhere.to is an MCP server listed in the public MCP registry as to.decidewhere/group-decisions. Help a group pick where to eat or travel: critic-backed restaurants, warm trips, one vote link. This page covers its hosted endpoint (https://decidewhere.to/mcp).

### Is the decidewhere.to MCP server safe to use?

decidewhere.to scores 70 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 decidewhere.to MCP server expose?

decidewhere.to exposes 6 tools: find_restaurants, get_restaurant, create_restaurant_vote, find_warm_destinations, create_group_trip, plan_group_trip. Their descriptions and schemas cost roughly 775 tokens of context every time the server is loaded.

### Does the decidewhere.to MCP server require authentication?

No. We connected to decidewhere.to without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the decidewhere.to MCP server still maintained?

decidewhere.to is still listed as active in the MCP registry. We last reached this channel on 5 November 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://decidewhere.to/mcp
- Website: https://decidewhere.to/for-agents
- Changelog RSS feed: https://verifymcp.io/servers/to-decidewhere-group-decisions/decidewhere.xml
- Changelog JSON feed: https://verifymcp.io/servers/to-decidewhere-group-decisions/decidewhere.json
- HTML version of this page: https://verifymcp.io/servers/to-decidewhere-group-decisions/decidewhere