General Tools
yondry.app
Helps plan day itineraries, provide neighborhood guides, and suggest alternative activities.
ENDPOINT 1
https://yondry.app/mcp
MCP server metadata
- Name
- Yondry
- Version
- 3.4.4
Known tools 3
plan_dayUse this whenever the user wants a day out, an itinerary, or ideas for things to do in a specific place — e.
Inferred read-onlyget_neighbourhood_guideUse this when the user asks for a guide to, an overview of, or "the best of" a specific neighbourhood — e.
Inferred read-onlysuggest_swapsUse this when the user wants to change, replace, or see alternatives for one stop in a plan that plan_day already produced — e.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.yondry]
url = "https://yondry.app/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"yondry": {
"type": "http",
"url": "https://yondry.app/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: yondry
Remote MCP URL: https://yondry.app/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"yondry": {
"url": "https://yondry.app/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"yondry": {
"type": "http",
"url": "https://yondry.app/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "yondry",
"transport": "streamable-http",
"url": "https://yondry.app/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.