All servers · Maps, location & weather · Crypto & blockchain · Research & knowledge

Yondry: Day Out Planner

io.github.yondry-ltd/day-planner · v1.0.1

No registry update 90+ days

Measured by MCP Station

Last check	Reachable
Checked at	—
Check success 7 / 30 days	—
First-try success 30 days	—
Median response	—
Lookups 30 days	—
Authentication	No auth
MCP version	2025-06-18
Rank score	—
Declared risk	Read-only (all tools declare readOnlyHint)
Capabilities declared	experimental, extensions, logging, prompts, resources, tools
Tool definitions	3 tools · with description 100% · input schema is an object 100% · read/destructive hints 100%

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

streamable-http · https://yondry.app/mcp

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

{
  "mcpServers": {
    "day-planner": {
      "url": "https://yondry.app/mcp"
    }
  }
}

plan_day
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
get_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
suggest_swaps
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

Website · JSON · Text for agents · Registry updated 2026-06-25