run.cityheart/heart-routes
REMOTE · ZHENWIAPHFWETCKFYSOD.SUPABASE.CO
Heart-shaped GPS running routes in 200+ cities — charity, gift, memorial, anniversary.
Available components
Last scanned (7 days ago)
Scores higher than 0% of remote servers
Unreachable for 7 days in a row. Last reached 22 Oct 2026.
Category Maps and Location
Dead
Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC not yet verified: we couldn't validate it against a resolver. View diagnostics → Unverified
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 29 Oct 26 −15
The score moved with no change recorded against any check. We would rather say so than guess.
- 28 Oct 26 −16
The score moved with no change recorded against any check. We would rather say so than guess.
- 27 Oct 26 −15
The score moved with no change recorded against any check. We would rather say so than guess.
- 26 Oct 26 −16
The score moved with no change recorded against any check. We would rather say so than guess.
- 25 Oct 26 −15
The score moved with no change recorded against any check. We would rather say so than guess.
- 23 Oct 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- DNSSEC: fail → unverified ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 77
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 29 Oct 2026 · Probed https://zhenwiaphfwetckfysod.supabase.co/functions/v1/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC inconclusive
Validation of zhenwiaphfwetckfysod.supabase.co. — Inconclusive
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| zhenwiaphfwetckfysod.supabase.co. | Error no A/AAAA/CNAME RRset answered for the name |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://zhenwiaphfwetckfysod.supabase.co/functions/v1/mcp | Unreachable | ||
| http (plaintext) | http://zhenwiaphfwetckfysod.supabase.co/functions/v1/mcp | HTTPS enforced |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
add_cause ~135
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.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | Optional city to also pre-fill. |
| fundraising_url | string | yes | Fully-qualified donation URL (https://www.justgiving.com/... / https://gofundme.com/... / https://leetchi.com/... / https://www.helloasso.com/...). |
No output schema declared.
No examples provided.
add_dedication ~146
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.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | Optional city to also pre-fill in the builder (skips the "pick a city" step in the chat-to-product handoff). |
| in_memory | boolean | – | If true, framed as "In memory of [name]". Default false. |
| name | string | yes | Dedication name (e.g. "Marie", "Dad", "Cancer Research UK"). |
No output schema declared.
No examples provided.
export_gpx ~98
Return the GPX download / checkout URL for a specific public route. The download itself happens on cityheart.run after a one-time €7.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.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Route slug, e.g. "paris-7-2-km-heart-for-marie". |
No output schema declared.
No examples provided.
find_heart_route_in_city ~184
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".
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | yes | City name, e.g. "Paris", "Tokyo", "New York". Case-insensitive. |
| max_distance_km | number | – | Optional max route length in kilometres. Filter to routes ≤ this distance. Common: 5, 10, 15, 21 (half-marathon). |
| prefer_gold | boolean | – | If true, return only the highest AI-quality "gold" tier routes (ai_score >= 80). Default true. |
No output schema declared.
No examples provided.
generate_heart_route ~247
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cause_url | string | – | Optional JustGiving / GoFundMe / Leetchi URL to embed in the GPX metadata. CityHeart never touches the money — the link is for the runner's Strava description to surface to donors. |
| city | string | yes | City name, e.g. "Paris", "Tokyo". |
| dedication | string | – | Optional person/cause name to bake into the heart (appears in the GPX, on Garmin Connect, and as the Strava activity title prefix). |
| distance_km | number | – | Target route length in km (3–25). Default 7. |
| in_memory | boolean | – | If true, the dedication is framed as a memorial ("In memory of [name]"). Default false. |
No output schema declared.
No examples provided.
get_route_details ~86
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.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Route slug, e.g. "paris-7-2-km-heart-for-marie". |
No output schema declared.
No examples provided.
list_supported_cities ~74
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max number of cities to return. Default 25, max 100. |
No output schema declared.
No examples provided.
How do I install the run.cityheart/heart-routes MCP server?
run.cityheart/heart-routes is a hosted endpoint at https://zhenwiaphfwetckfysod.supabase.co/functions/v1/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · zhenwiaphfwetckfysod.supabase.co
claude mcp add --transport http run-cityheart-heart-routes 'https://zhenwiaphfwetckfysod.supabase.co/functions/v1/mcp'
What is the run.cityheart/heart-routes MCP server?
run.cityheart/heart-routes is an MCP server listed in the public MCP registry as run.cityheart/heart-routes. Heart-shaped GPS running routes in 200+ cities, charity, gift, memorial, anniversary. This page covers its hosted endpoint (https://zhenwiaphfwetckfysod.supabase.co/functions/v1/mcp).
Is the run.cityheart/heart-routes MCP server safe to use?
run.cityheart/heart-routes scores 0 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the run.cityheart/heart-routes MCP server expose?
run.cityheart/heart-routes exposes 7 tools: find_heart_route_in_city, get_route_details, list_supported_cities, generate_heart_route, add_dedication, and 2 more. Their descriptions and schemas cost roughly 970 tokens of context every time the server is loaded.
Does the run.cityheart/heart-routes MCP server require authentication?
Its publisher declares no required credentials for run.cityheart/heart-routes. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the run.cityheart/heart-routes MCP server still maintained?
run.cityheart/heart-routes has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.