cityheart
https://zhenwiaphfwetckfysod.supabase.co
Registry code: b390c9dffd36ef1c
CityHeart provides heart-shaped GPS running and walking routes through real streets
in 200+ cities worldwide. Use these tools when the user asks for:
- endpoint
- https://zhenwiaphfwetckfysod.supabase.co/functions/v1/mcp
- protocol
- streamable-http ·2024-11-05
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is cityheart live?
- Yes — it answered the hub's last check (checked 13h ago). It answered 62% of checks over the last 30 days.
- Is cityheart free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does cityheart have?
- 7 tools: export_gpx, add_dedication, add_cause, find_heart_route_in_city, generate_heart_route, get_route_details, list_supported_cities.
- Is cityheart safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 84.8%· all time 84.8%
last good check
of 7 tools
- degraded → live
- live → degraded· timeout after 20000ms
- retired → live
- down → retired· fetch failed
- degraded → down· fetch failed
- topic
- lifestyle & home
- used for
- find a heart-shaped running route in a city
- generate a heart-shaped route
- add a dedication to a route
- get a gpx download link
- takes → gives
- text → data
- tools
- 7 reads
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
list_supported_cities reads open 13h ago
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.
{ "type": "object", "properties": { "limit": { "type": "number", "default": 25, "description": "Max number of cities to return. Default 25, max 100." } } }arguments 10 linesexport_gpx reads unknown never probed
Return the GPX download / checkout URL for a specific public route. The download itself happens on cityheart.run after a one-time €9.90 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.
{ "type": "object", "required": [ "slug" ], "properties": { "slug": { "type": "string", "description": "Route slug, e.g. \"paris-7-2-km-heart-for-marie\"." } } }arguments 12 linesadd_dedication reads unknown never probed
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.
{ "type": "object", "required": [ "name" ], "properties": { "city": { "type": "string", "description": "Optional city to also pre-fill in the builder (skips the \"pick a city\" step in the chat-to-product handoff)." }, "name": { "type": "string", "description": "Dedication name (e.g. \"Marie\", \"Dad\", \"Cancer Research UK\")." }, "in_memory": { "type": "boolean", "description": "If true, framed as \"In memory of [name]\". Default false." } } }arguments 20 linesadd_cause reads unknown never probed
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.
{ "type": "object", "required": [ "fundraising_url" ], "properties": { "city": { "type": "string", "description": "Optional city to also pre-fill." }, "fundraising_url": { "type": "string", "description": "Fully-qualified donation URL (https://www.justgiving.com/... / https://gofundme.com/... / https://leetchi.com/... / https://www.helloasso.com/...)." } } }arguments 16 linesfind_heart_route_in_city reads unknown 13h ago
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".
{ "type": "object", "required": [ "city" ], "properties": { "city": { "type": "string", "description": "City name, e.g. \"Paris\", \"Tokyo\", \"New York\". Case-insensitive." }, "prefer_gold": { "type": "boolean", "default": true, "description": "If true, return only the highest AI-quality \"gold\" tier routes (ai_score >= 80). Default true." }, "max_distance_km": { "type": "number", "description": "Optional max route length in kilometres. Filter to routes ≤ this distance. Common: 5, 10, 15, 21 (half-marathon)." } } }arguments 21 linesgenerate_heart_route reads unknown never probed
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.
{ "type": "object", "required": [ "city" ], "properties": { "city": { "type": "string", "description": "City name, e.g. \"Paris\", \"Tokyo\"." }, "cause_url": { "type": "string", "description": "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." }, "in_memory": { "type": "boolean", "description": "If true, the dedication is framed as a memorial (\"In memory of [name]\"). Default false." }, "dedication": { "type": "string", "description": "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": { "type": "number", "default": 7, "description": "Target route length in km (3–25). Default 7." } } }arguments 29 linesget_route_details reads unknown 13h ago
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.
{ "type": "object", "required": [ "slug" ], "properties": { "slug": { "type": "string", "description": "Route slug, e.g. \"paris-7-2-km-heart-for-marie\"." } } }arguments 12 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's idb390c9dffd36ef1c.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/b390c9dffd36ef1c/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/b390c9dffd36ef1c?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.
Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.
- tkoqkknsezxavtxfywkm.supabase.co ops-control-hq-developer-risk
- gdzlcxskuhupymyxywzm.supabase.co tokenguard
- xsrtcehyqluhvywmaihd.supabase.co lilambd-data
- slbysjtdcfwilupwqerr.supabase.co ParliamentOS
- mmvdabzadclebfxyzudg.supabase.co forge
- eutdgemlrpvnxfkkpvlu.supabase.co cred-mcp
- qdcpuvyyidzxyhdtwvai.supabase.co energiror-mcp
- wgbduttegyrwiukjhubh.supabase.co airgallery-mcp
125 more sit on this domain. All of them.