# run.cityheart/heart-routes (remote · zhenwiaphfwetckfysod.supabase.co)

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

- Trust score: 64/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `zhenwiaphfwetckfysod.supabase.co`: 64/100 (this document), [markdown](https://verifymcp.io/servers/run-cityheart-heart-routes/functions-v1-mcp.md), [page](https://verifymcp.io/servers/run-cityheart-heart-routes/functions-v1-mcp)

## Channel facts

- Endpoint: `https://zhenwiaphfwetckfysod.supabase.co/functions/v1/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http run-cityheart-heart-routes https://zhenwiaphfwetckfysod.supabase.co/functions/v1/mcp
```

### Codex

```toml
[mcp_servers.run-cityheart-heart-routes]
url = "https://zhenwiaphfwetckfysod.supabase.co/functions/v1/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "run-cityheart-heart-routes": {
      "type": "remote",
      "url": "https://zhenwiaphfwetckfysod.supabase.co/functions/v1/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add run-cityheart-heart-routes --url https://zhenwiaphfwetckfysod.supabase.co/functions/v1/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  run-cityheart-heart-routes:
    url: "https://zhenwiaphfwetckfysod.supabase.co/functions/v1/mcp"
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 63, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 62, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-28 (score 61, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 60, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 59)

First indexed and scored.

## MCP tools (7)

### `find_heart_route_in_city` (~184 tokens)

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".

Input parameters:

- `city` (string, required): 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.

### `get_route_details` (~86 tokens)

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.

Input parameters:

- `slug` (string, required): Route slug, e.g. "paris-7-2-km-heart-for-marie".

### `list_supported_cities` (~74 tokens)

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.

Input parameters:

- `limit` (number): Max number of cities to return. Default 25, max 100.

### `generate_heart_route` (~247 tokens)

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.

Input parameters:

- `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, required): 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.

### `add_dedication` (~146 tokens)

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.

Input parameters:

- `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, required): Dedication name (e.g. "Marie", "Dad", "Cancer Research UK").

### `add_cause` (~135 tokens)

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.

Input parameters:

- `city` (string): Optional city to also pre-fill.
- `fundraising_url` (string, required): Fully-qualified donation URL (https://www.justgiving.com/... / https://gofundme.com/... / https://leetchi.com/... / https://www.helloasso.com/...).

### `export_gpx` (~98 tokens)

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.

Input parameters:

- `slug` (string, required): Route slug, e.g. "paris-7-2-km-heart-for-marie".

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/run-cityheart-heart-routes/functions-v1-mcp#diagnostics

## Score history

- 2026-08-03: 64
- 2026-08-02: 63
- 2026-08-01: 63
- 2026-07-31: 63
- 2026-07-30: 62
- 2026-07-29: 61
- 2026-07-28: 61
- 2026-07-27: 60
- 2026-07-26: 59

## Links

- Remote endpoint: https://zhenwiaphfwetckfysod.supabase.co/functions/v1/mcp
- Repository: https://github.com/secupunk/scenic-pathfinder-ai
- Website: https://cityheart.run/mcp
- Changelog RSS feed: https://verifymcp.io/servers/run-cityheart-heart-routes/functions-v1-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/run-cityheart-heart-routes/functions-v1-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/run-cityheart-heart-routes/functions-v1-mcp