Skip to content
Cityalert logo

Cityalert MCP server

Which servers in the official MCP registry are Cityalert's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-19

← Back to Cityalert

Whose server it is
  • Registry namelive.cityalert/cityalertverified in the MCP registry

The registry name sits under cityalert.live. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-19
  • Stateanswerschecked 2026-10-19
  • Tools8
  • Server calls itselfcityalert
  • Server version0.1.1
  • Protocol version2025-06-18

On 2026-10-19 the server answered initialize and tools/list without a sign-in. First answer in 454 ms.

Measured dailydaily checks: 2, the first on 2026-10-19
  • Answeredmeasuring2 of the 7 daily checks it takes to print a share
  • Median first answer407 ms
  • Space in an agent's context≈ 1,307 tokensthe definitions of all its tools (8), which an agent carries on every turn
  • Tool definitionsA · 96 of 100
  • Parameters without a description: in 2 of 8

Worth a look

  • Tools that change data, on a server that answers without a sign-in: create_dashboard

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The state of vendors' MCP servers: method and numbers →

Tools it offers8 tools · read 2026-10-19
  • list_regions

    List CityAlert focus regions (key, label, center, zoom, bbox). Use region keys with get_incidents.

  • get_incidents

    Merged live incidents from all feeds plus manual reports. Filter by region key, category, group, severity, source, or bbox. Results come from a shared ~15-minute snapshot; real-time refresh requires an API key with that entitlement…

  • get_trends

    Historical aggregates: VPD crime by year/month/type (6y), USGS M4+ quakes per region (10y), GDACS global events (3y), report and live snapshot stats. Use for questions about patterns over time — crime trends, quake frequency, disaster…

  • get_crime_year

    Full-year VPD crime data: totals and ranked neighbourhood stats. Vancouver only, 2003-present.

  • get_news

    Per-region safety news items, or news for an arbitrary place name.

  • submit_report

    File a manual geolocated incident report (same as POST /api/reports). Reports are moderated before they appear publicly. Errors: 'report submission disabled' if the caller is blocked; 'rate limited' past 20 reports/hour via MCP.

  • get_dashboard

    Read a saved dashboard by id (shareable, read-only).

  • create_dashboard

    Create a shareable dashboard. Returns {id, token} — the token grants write access via PUT /api/dashboards, so save it.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "cityalert": {
      "type": "http",
      "url": "https://cityalert.live/.well-known/mcp"
    }
  }
}

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.