run.cityheart/heart-routes
REMOTE · ZHENWIAPHFWETCKFYSOD.SUPABASE.CO · SCANNED SEP 20
Heart-shaped GPS running routes in 200+ cities — charity, gift, memorial, anniversary.
Available components
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1134 tokens (~162/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
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'
{
"mcpServers": {
"run-cityheart-heart-routes": {
"url": "https://zhenwiaphfwetckfysod.supabase.co/functions/v1/mcp"
}
}
} {
"servers": {
"run-cityheart-heart-routes": {
"type": "http",
"url": "https://zhenwiaphfwetckfysod.supabase.co/functions/v1/mcp"
}
}
} [mcp_servers.run-cityheart-heart-routes] url = "https://zhenwiaphfwetckfysod.supabase.co/functions/v1/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"run-cityheart-heart-routes": {
"type": "remote",
"url": "https://zhenwiaphfwetckfysod.supabase.co/functions/v1/mcp",
"enabled": true
}
}
} openclaw mcp add run-cityheart-heart-routes --url 'https://zhenwiaphfwetckfysod.supabase.co/functions/v1/mcp' --transport streamable-http
mcp_servers:
run-cityheart-heart-routes:
url: "https://zhenwiaphfwetckfysod.supabase.co/functions/v1/mcp" {
"McpServers": {
"run-cityheart-heart-routes": {
"Transport": "http",
"Url": "https://zhenwiaphfwetckfysod.supabase.co/functions/v1/mcp"
}
}
} assistant mcp add run-cityheart-heart-routes -t streamable-http -u 'https://zhenwiaphfwetckfysod.supabase.co/functions/v1/mcp'
{
"mcpServers": {
"run-cityheart-heart-routes": {
"type": "http",
"url": "https://zhenwiaphfwetckfysod.supabase.co/functions/v1/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 7 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “export_gpx” rewrote its description, which is the text the model reads security
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
- Stability: 0.97 → pass security
- 23 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 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
- 31 Jul 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
- 30 Jul 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
- 27 Jul 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
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 20 Sept 2026 · Probed https://zhenwiaphfwetckfysod.supabase.co/functions/v1/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=supabase.co | CN=WE1,O=Google Trust Services,C=US | 26 Aug 2026 | 24 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 7c35296a896c0a6f13f8495266045d45 |
| SANs: supabase.co, *.supabase.co | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of zhenwiaphfwetckfysod.supabase.co. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| co. | present | 7786 | 8 | Verified |
| supabase.co. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
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 | Verified | 200 | |
| http (plaintext) | http://zhenwiaphfwetckfysod.supabase.co/functions/v1/mcp | HTTPS enforced | 301 | https://zhenwiaphfwetckfysod.supabase.co/functions/v1/mcp |
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.
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 77 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?
No. We connected to run.cityheart/heart-routes without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the run.cityheart/heart-routes MCP server still maintained?
run.cityheart/heart-routes is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.