Search / io.github.yondry-ltd/day-planner
protogridR0· no sign-inPlan your perfect day out anywhere: itineraries and neighbourhood guides, tuned to mood and weather.
v1.0.1 · active · website · descriptor JSON · versions
{
"mcpServers": {
"day-planner": {
"type": "http",
"url": "https://yondry.app/mcp"
}
}
}claude mcp add --transport http day-planner https://yondry.app/mcp[mcp_servers.day-planner]
url = "https://yondry.app/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"day-planner": {
"type": "remote",
"url": "https://yondry.app/mcp",
"enabled": true
}
}
}{
"mcpServers": {
"day-planner": {
"type": "http",
"url": "https://yondry.app/mcp"
}
},
"deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=day-planner&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8veW9uZHJ5LmFwcC9tY3AifQ%3D%3D"
}{
"servers": {
"day-planner": {
"type": "http",
"url": "https://yondry.app/mcp"
}
}
}{
"mcpServers": {
"day-planner": {
"httpUrl": "https://yondry.app/mcp"
}
}
}extensions:
"day-planner":
enabled: true
name: "day-planner"
type: streamable_http
uri: "https://yondry.app/mcp"
timeout: 300
protocol.modernnewest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28protocol.statelessonly applies to 2026-07-28 serversprotocol.transportstreamable HTTPprotocol.list_ttlonly applies to 2026-07-28 serversauth.prm, auth.as_metadata, auth.cimdno remote uses OAuthauth.secret_in_urlno templated URLtools.descriptionsevery tool has a descriptiontools.description_lengthdescriptions are concisetools.schemasevery tool has an object input schematools.annotations3 of 3 tools declare readOnlyHint or destructiveHinttools.directory_hintsno tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: plan_day (destructiveHint, idempotentHint, openWorldHint); get_neighbourhood_guide (destructiveHint, idempotentHint, openWorldHint); suggest_swaps (destructiveHint, idempotentHint, openWorldHint)tools.token_costabout 846 tokens to load every tooltools.api_dumptools are not a one-to-one API dumpstability.changesno tool changes in 30 daysstability.rug_pullno tool changed its meaning under the same namedeps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI packageNo tool definition changes recorded. A server's first observation is its baseline; later probes record what changes.
Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.
+website +reachable +uptime-92% ~updated-117d-ago -no-repository
Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.
| remote | auth | reachable | uptime 30d | p50 | protocol | last ok |
|---|---|---|---|---|---|---|
https://yondry.app/mcp streamable-http | none | yes | 92% | 391 ms | 2025-11-25 | 2026-10-20 |
get_neighbourhood_guideread-only | 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. |
plan_dayread-only | 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. |
suggest_swapsread-only | 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. |
Schemas: list_tools.
{
"name": "io.github.yondry-ltd/day-planner",
"title": "Yondry: Day Out Planner",
"$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
"remotes": [
{
"url": "https://yondry.app/mcp",
"type": "streamable-http"
}
],
"version": "1.0.1",
"websiteUrl": "https://yondry.app",
"description": "Plan your perfect day out anywhere: itineraries and neighbourhood guides, tuned to mood and weather."
}