Yondry: Day Out Planner
REMOTE · YONDRY.APP · SCANNED SEP 20
Plan your perfect day out anywhere: itineraries and neighbourhood guides, tuned to mood and weather.
Available components
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability57
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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
How do I install the Yondry: Day Out Planner MCP server?
Yondry: Day Out Planner is a hosted endpoint at https://yondry.app/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 · yondry.app
claude mcp add --transport http yondry-ltd-day-planner 'https://yondry.app/mcp'
{
"mcpServers": {
"yondry-ltd-day-planner": {
"url": "https://yondry.app/mcp"
}
}
} {
"servers": {
"yondry-ltd-day-planner": {
"type": "http",
"url": "https://yondry.app/mcp"
}
}
} [mcp_servers.yondry-ltd-day-planner] url = "https://yondry.app/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"yondry-ltd-day-planner": {
"type": "remote",
"url": "https://yondry.app/mcp",
"enabled": true
}
}
} openclaw mcp add yondry-ltd-day-planner --url 'https://yondry.app/mcp' --transport streamable-http
mcp_servers:
yondry-ltd-day-planner:
url: "https://yondry.app/mcp" {
"McpServers": {
"yondry-ltd-day-planner": {
"Transport": "http",
"Url": "https://yondry.app/mcp"
}
}
} assistant mcp add yondry-ltd-day-planner -t streamable-http -u 'https://yondry.app/mcp'
{
"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.
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.
- 9 Sept 26 0
- Server version: 3.4.7 → 3.4.2 functional
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
- Stability: 0.97 → pass security
- 23 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Aug 26 0
- Server version: 3.4.6 → 3.4.7 functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 7 Aug 26 0
- The server no longer declares the “experimental” capability functional
- Server version: 3.4.5 → 3.4.6 functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 20 Sept 2026 · Probed https://yondry.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=yondry.app | CN=YE2,O=Let's Encrypt,C=US | 13 Aug 2026 | 11 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 6dc0cf60fb4ec6e431f4de5b96003945af8 |
| SANs: *.yondry.app, yondry.app | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of yondry.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| yondry.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://yondry.app/mcp | Verified | 200 | |
| http (plaintext) | http://yondry.app/mcp | HTTPS enforced | 301 | https://yondry.app/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 →
get_neighbourhood_guide Get a neighbourhood guide ~239
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.
| Name | Type | Req | Description |
|---|---|---|---|
| neighbourhood | string | yes | – |
No output schema declared.
No examples provided.
plan_day Plan a day out ~248
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.
| Name | Type | Req | Description |
|---|---|---|---|
| constraints | – | – | – |
| location | string | yes | – |
| vibe | – | – | – |
No output schema declared.
No examples provided.
suggest_swaps Suggest alternative stops for a plan ~190
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.
| Name | Type | Req | Description |
|---|---|---|---|
| plan_id | string | yes | – |
| reason | – | – | – |
| stop_index | integer | yes | – |
No output schema declared.
No examples provided.
What is the Yondry: Day Out Planner MCP server?
Yondry: Day Out Planner is an MCP server listed in the public MCP registry as io.github.yondry-ltd/day-planner. Plan your perfect day out anywhere: itineraries and neighbourhood guides, tuned to mood and weather. This page covers its hosted endpoint (https://yondry.app/mcp).
Is the Yondry: Day Out Planner MCP server safe to use?
Yondry: Day Out Planner scores 72 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 Yondry: Day Out Planner MCP server expose?
Yondry: Day Out Planner exposes 3 tools: plan_day, get_neighbourhood_guide, suggest_swaps. Their descriptions and schemas cost roughly 677 tokens of context every time the server is loaded.
Does the Yondry: Day Out Planner MCP server require authentication?
No. We connected to Yondry: Day Out Planner without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Yondry: Day Out Planner MCP server still maintained?
Yondry: Day Out Planner is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.