mcpbeat

Heart Routes MCP Server

run.cityheart/heart-routes
answering

Heart Routes is answering right now. Last checked 9 min ago. It exposes 7 tools.

Heart-shaped GPS running routes in 200+ cities — charity, gift, memorial, anniversary.

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 39 hours of history
39 hours agonow
100.0%
Uptime 24h
91 of 91 checks
7
Tools
read from the server
288 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 9 min ago.

run in your terminal
claude mcp add heart-routes --transport http https://zhenwiaphfwetckfysod.supabase.co/functions/v1/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "heart-routes": {
      "url": "https://zhenwiaphfwetckfysod.supabase.co/functions/v1/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.heart-routes]
url = "https://zhenwiaphfwetckfysod.supabase.co/functions/v1/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "heart-routes": {
      "url": "https://zhenwiaphfwetckfysod.supabase.co/functions/v1/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "heart-routes": {
      "url": "https://zhenwiaphfwetckfysod.supabase.co/functions/v1/mcp"
    }
  }
}

Available tools 7

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

cause
add_cause
Compose a builder URL with a fundraising link pre-filled — the URL is embedded into the GPX metadata (description, filename) so it surfaces in the runner's Strava activity after they sync. CityHeart never collects the donation; the runner's donors click straight through to JustGiving / GoFundMe / Leetchi / etc.
dedication
add_dedication
Compose a builder URL with a dedication pre-filled — the name shows on the runner's GPS watch and in the Strava activity title. Use after the user picks a route (find/generate) and decides who the heart is for. Pure URL builder, no server-side state.
export
export_gpx
Return the GPX download / checkout URL for a specific public route. The download itself happens on cityheart.run after a one-time €4.99 payment (Stripe — CityHeart never charges through the chat). Use after the user has picked a final route (find / get_details) and confirms they want it.
generate
generate_heart_route
Start a new heart-shaped route for a given city. Returns existing AI-validated matches from inventory PLUS a deep-link to the live builder for an on-demand fresh generation with the user's exact dedication and cause. Use when the user explicitly wants a NEW heart, or when an existing match is "close enough but not personal yet". Optional dedication / cause_url pre-fill the builder fields, so the URL deep-link arrives configured.
heart
find_heart_route_in_city
Find an existing heart-shaped running route in a given city. Returns up to 5 AI-validated routes matching the city (and optionally a target distance). Use this when a user mentions a city and wants a heart route — e.g. "find me a heart-shaped route in Paris" or "I want to run a heart in Tokyo for my mum's birthday".
route
get_route_details
Get full details for a specific heart route by its slug. Use after find_heart_route_in_city when the user picks one. Returns: city, distance, image URL, share URL, dedication (if any), and the GPX download deep-link.
supported
list_supported_cities
List cities that have at least one heart route available. Use when the user asks "where can I run a heart?" or hasn't picked a city yet. Returns city names + route counts, sorted by inventory size.

Endpoints

URLTransportStateLatencyChecked
https://zhenwiaphfwetckfysod.supabase.co/functions/v1/mcp streamable-http answering 277 ms 9 min ago

Heart Routes — questions

Answers built from our own checks of this server.

What can Heart Routes do?
It exposes 7 tools, read directly from the server on our last check. Among them: add_cause, add_dedication, export_gpx, find_heart_route_in_city, generate_heart_route, get_route_details and 1 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Heart Routes working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 288 ms. The bar chart above shows every period we have measured.
Is Heart Routes still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
How do I connect Heart Routes?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Heart Routes need an API key?
No. Heart Routes completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 7 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Heart Routes?
It answers our handshake in 288 ms on average, which is faster than 48% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.