Skip to content

heart-routes MCP server

run.cityheart/heart-routescityheart.runstreamable-httpv1.0.0Scanned

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

7 tools: 3 change things and 4 only read.

Tools: 0 delete, 0 irreversible, 3 write, 4 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

3 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the heart-routes MCP server can do

The heart-routes MCP server is published by cityheart.run, a domain the MCP Registry verified. It has 7 tools. It can create or change data (3 tools: generate_heart_route, add_dedication and add_cause), but cannot delete data. 4 tools only read.

1 tool brings in text other people can write (export_gpx).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 18, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

7 tools

Changes things 3Claude Code: ask
  • add_causeCompose 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 th…No findings

    Why it is in this group

    • The name "add_cause" says "add": a word for a change.
    Description, as the server wrote it
    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.
  • add_dedicationCompose a builder URL with a dedication pre-filled — the name shows on the runner's GPS watch and in the Strava activity title.No findings

    Why it is in this group

    • The name "add_dedication" says "add": a word for a change.
    Description, as the server wrote it
    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.
  • generate_heart_routeStart a new heart-shaped route for a given city.No findings

    Why it is in this group

    • The name "generate_heart_route" says "generate": a word for a change.
    Description, as the server wrote it
    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.
Only reads 4Show 4 read-only tools
  • export_gpxReturn the GPX download / checkout URL for a specific public route.Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "return": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "return" and "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    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.
  • find_heart_route_in_cityFind an existing heart-shaped running route in a given city.No findings

    Why it is in this group

    • The name "find_heart_route_in_city" says "find": a word for reading.
    Description, as the server wrote it
    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".
  • get_route_detailsGet full details for a specific heart route by its slug.No findings

    Why it is in this group

    • The name "get_route_details" says "get": a word for reading.
    Description, as the server wrote it
    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.
  • list_supported_citiesList cities that have at least one heart route available.No findings

    Why it is in this group

    • The name "list_supported_cities" says "list": a word for reading.
    Description, as the server wrote it
    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.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:18 UTC, unchanged since Nov 6, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
3
Protocol version
2024-11-05
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://zhenwiaphfwetckfysod.supabase.co/functions/v1/mcp: tools/list returned 7 tools to an anonymous client, including generate_heart_route (write), add_dedication (write), add_cause (write)

    What this check looks for

Posture changes

  1. Nov 6, 2026
    • Reachable: no to yes
    • HTTP status of an anonymous initialize: none to 200
    • tools/list served without credentials: no to yes
    • Tools that change things, listed without credentials: 0 to 3
    • Protocol version: none to 2024-11-05

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools1 changed.~1 changedView diff
  2. PostureRemote posture changed. Reachable: no -> yes; HTTP status of an anonymous initialize: none -> 200; tools/list served without credentials: no -> yes (and 2 more).View diff
    • Reachable: no to yes
    • HTTP status of an anonymous initialize: none to 200
    • tools/list served without credentials: no to yes
    • Tools that change things, listed without credentials: 0 to 3
    • Protocol version: none to 2024-11-05

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__heart-routes__find_heart_route_in_city",
      "mcp__heart-routes__get_route_details",
      "mcp__heart-routes__list_supported_cities",
      "mcp__heart-routes__export_gpx"
    ],
    "ask": [
      "mcp__heart-routes__generate_heart_route",
      "mcp__heart-routes__add_dedication",
      "mcp__heart-routes__add_cause"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as heart-routes. Review it before you use it.

Capability tags behind 1 rule
  • mcp__heart-routes__export_gpx untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/run.cityheart/heart-routes/verify?hash=a2b3c56f7e35461511b9c1abdc5dbd106ebd9d5d0175a4ae389b57442d0e8fae" | jq -e '.changed == false'

Pinned hash a2b3c56f7e35, from Nov 18, 2026, 06:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/run.cityheart/heart-routes/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for run.cityheart/heart-routes
[![Anlyon Radar](https://radar.anlyon.com/badge/run.cityheart/heart-routes.svg)](https://radar.anlyon.com/servers/run.cityheart/heart-routes)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:54 UTC.

heart-routes MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the heart-routes MCP server safe?

No scan can promise that. What its definitions show: 7 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the heart-routes MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the heart-routes MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the heart-routes MCP server have?

7 tools: 3 write, 4 read. generate_heart_route, add_dedication, add_cause, find_heart_route_in_city, get_route_details, list_supported_cities and export_gpx.

Does the heart-routes MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the heart-routes MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the heart-routes MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 18, 2026. Every change is on this page and in its Atom feed.