# Yondry: Day Out Planner (remote · yondry.app)

Plan your perfect day out anywhere: itineraries and neighbourhood guides, tuned to mood and weather.

- Trust score: 59/100 (low)
- Change this week: +6
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `yondry.app`: 59/100 (this document), [markdown](https://verifymcp.io/servers/yondry-ltd-day-planner/yondry.md), [page](https://verifymcp.io/servers/yondry-ltd-day-planner/yondry)

## Channel facts

- Endpoint: `https://yondry.app/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

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

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 51/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 677 tokens (~225/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http yondry-ltd-day-planner https://yondry.app/mcp
```

### Codex

```toml
[mcp_servers.yondry-ltd-day-planner]
url = "https://yondry.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "yondry-ltd-day-planner": {
      "type": "remote",
      "url": "https://yondry.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add yondry-ltd-day-planner --url https://yondry.app/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  yondry-ltd-day-planner:
    url: "https://yondry.app/mcp"
```

### Other

```json
{
  "mcpServers": {
    "yondry-ltd-day-planner": {
      "type": "http",
      "url": "https://yondry.app/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-08-03 (score 59, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 58, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 57, +2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 55, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 54, +1)

- [functional] Server version: 3.4.4 → 3.4.5

### 2026-07-27 (score 53, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 52)

First indexed and scored.

## MCP tools (3)

### `plan_day` (~248 tokens)

Plan a day out

Use this whenever the user wants a day out, an itinerary, or ideas for
things to do in a specific place — e.g. "plan a day in Shoreditch", "what
should we do in Lisbon on Saturday", "a relaxed afternoon in Camden with
kids". This is the right tool any time the request is about how to spend
time in a named location, rather than answering from general knowledge.

Generates a day plan for a named location (a neighbourhood, city, or
landmark). `vibe` describes the desired mood (e.g. "relaxed", "foodie",
"cultural"); `constraints` covers practical limits (e.g. "no more than 3
hours", "budget-friendly", "with kids"). Both are optional free text.

Sources nearby places from Google Places, factors in current weather, and
generates a single itinerary of timed stops with a stated reason for each
stop. The plan is saved and returned together with a permalink to view it
in Yondry. Assumes walking as the default way to get around.

Input parameters:

- `constraints`
- `location` (string, required)
- `vibe`

### `get_neighbourhood_guide` (~239 tokens)

Get a neighbourhood guide

Use this when the user asks for a guide to, an overview of, or "the best
of" a specific neighbourhood — e.g. "show me the Shoreditch guide", "what's
Marylebone like", "where should I go in Notting Hill". Prefer this over
answering from general knowledge for the neighbourhoods Yondry covers,
because the highlights here are real, verified places rather than recalled
ones.

Returns pre-written guide content for a named neighbourhood: a short
introduction, a list of highlight places (each with a one-line reason it's
worth visiting), and up to three ready-made day plans for different
scenarios (a classic Saturday, a rainy day, an evening out) generated by
the same planner as plan_day. Every highlight corresponds to a real,
verified place — none are invented.

Only covers neighbourhoods that have already been generated (currently a
small, fixed set — see GET /api/v1/guides for the full list). Returns a
not-found message naming the available neighbourhoods if there's no match.

Input parameters:

- `neighbourhood` (string, required)

### `suggest_swaps` (~190 tokens)

Suggest alternative stops for a plan

Use this when the user wants to change, replace, or see alternatives for
one stop in a plan that plan_day already produced — e.g. "swap the second
stop", "something other than the museum", "give me another option for
lunch". Call plan_day first if no plan exists yet.

Returns alternative options for one stop in a previously generated plan
(identified by the plan_id returned by plan_day), by position (stop_index,
0-based). Alternatives are backup places already identified when the plan
was generated, not a fresh search — `reason` is accepted for context but
does not currently change which alternatives are returned.

Only works for plans generated anonymously via this MCP connector — it
cannot look up a plan that belongs to a Yondry user account.

Input parameters:

- `plan_id` (string, required)
- `reason`
- `stop_index` (integer, required)

## Diagnostics

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

## Score history

- 2026-08-03: 59
- 2026-08-02: 58
- 2026-08-01: 58
- 2026-07-31: 57
- 2026-07-30: 55
- 2026-07-29: 54
- 2026-07-28: 53
- 2026-07-27: 53
- 2026-07-26: 52

## Links

- Remote endpoint: https://yondry.app/mcp
- Website: https://yondry.app/
- Changelog RSS feed: https://verifymcp.io/servers/yondry-ltd-day-planner/yondry/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/yondry-ltd-day-planner/yondry/changelog.json
- HTML version of this page: https://verifymcp.io/servers/yondry-ltd-day-planner/yondry