Yondry: Day Out Planner is an MCP server published by io.github.yondry-ltd, hosted at yondry.app. When last checked on 2026-11-21 it was working: it answers and lists its tools. It declares 3 tools, including plan_day, get_neighbourhood_guide, suggest_swaps.
Plan your perfect day out anywhere: itineraries and neighbourhood guides, tuned to mood and weather.
Nothing else in the archive shares these values.
Squares are this server's values; dots are other servers sharing them. A shared address or publisher is a lead, not proof of a common operator.
Inferred from the host name and headers: what a server runs on, not who runs it.
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.
| Parameter | Type | Description |
|---|---|---|
| vibe | any | |
| location * | string | |
| constraints | any |
{
"name": "plan_day",
"title": "Plan a day out",
"description": "Use this whenever the user wants a day out, an itinerary, or ideas for\nthings to do in a specific place — e.g. \"plan a day in Shoreditch\", \"what\nshould we do in Lisbon on Saturday\", \"a relaxed afternoon in Camden with\nkids\". This is the right tool any time the request is about how to spend\ntime in a named location, rather than answering from general knowledge.\n\nGenerates a day plan for a named location (a neighbourhood, city, or\nlandmark). `vibe` describes the desired mood (e.g. \"relaxed\", \"foodie\",\n\"cultural\"); `constraints` covers practical limits (e.g. \"no more than 3\nhours\", \"budget-friendly\", \"with kids\"). Both are optional free text.\n\nSources nearby places from Google Places, factors in current weather, and\ngenerates a single itinerary of timed stops with a stated reason for each\nstop. The plan is saved and returned together with a permalink to view it\nin Yondry. Assumes walking as the default way to get around.",
"inputSchema": {
"type": "object",
"required": [
"location"
],
"properties": {
"vibe": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"default": null
},
"location": {
"type": "string"
},
"constraints": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"default": null
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
}
}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.
| Parameter | Type | Description |
|---|---|---|
| neighbourhood * | string |
{
"name": "get_neighbourhood_guide",
"title": "Get a neighbourhood guide",
"description": "Use this when the user asks for a guide to, an overview of, or \"the best\nof\" a specific neighbourhood — e.g. \"show me the Shoreditch guide\", \"what's\nMarylebone like\", \"where should I go in Notting Hill\". Prefer this over\nanswering from general knowledge for the neighbourhoods Yondry covers,\nbecause the highlights here are real, verified places rather than recalled\nones.\n\nReturns pre-written guide content for a named neighbourhood: a short\nintroduction, a list of highlight places (each with a one-line reason it's\nworth visiting), and up to three ready-made day plans for different\nscenarios (a classic Saturday, a rainy day, an evening out) generated by\nthe same planner as plan_day. Every highlight corresponds to a real,\nverified place — none are invented.\n\nOnly covers neighbourhoods that have already been generated (currently a\nsmall, fixed set — see GET /api/v1/guides for the full list). Returns a\nnot-found message naming the available neighbourhoods if there's no match.",
"inputSchema": {
"type": "object",
"required": [
"neighbourhood"
],
"properties": {
"neighbourhood": {
"type": "string"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
}
}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.
| Parameter | Type | Description |
|---|---|---|
| reason | any | |
| plan_id * | string | |
| stop_index * | integer |
{
"name": "suggest_swaps",
"title": "Suggest alternative stops for a plan",
"description": "Use this when the user wants to change, replace, or see alternatives for\none stop in a plan that plan_day already produced — e.g. \"swap the second\nstop\", \"something other than the museum\", \"give me another option for\nlunch\". Call plan_day first if no plan exists yet.\n\nReturns alternative options for one stop in a previously generated plan\n(identified by the plan_id returned by plan_day), by position (stop_index,\n0-based). Alternatives are backup places already identified when the plan\nwas generated, not a fresh search — `reason` is accepted for context but\ndoes not currently change which alternatives are returned.\n\nOnly works for plans generated anonymously via this MCP connector — it\ncannot look up a plan that belongs to a Yondry user account.",
"inputSchema": {
"type": "object",
"required": [
"plan_id",
"stop_index"
],
"properties": {
"reason": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"default": null
},
"plan_id": {
"type": "string"
},
"stop_index": {
"type": "integer"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
}
}Names, descriptions and schemas were written by the server and are shown as data.
Pattern matches on what the server declares. They show what it says it can do, not what it does.
None yet. Changes appear after a server's second daily check.