# CityAlert (remote · cityalert.live)

Free live public-safety incident map: global crime, fire, disaster, weather and news feeds

- Trust score: 86/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `cityalert.live`: 86/100 (this document), [markdown](https://verifymcp.io/servers/live-cityalert-cityalert/well-known-mcp.md), [page](https://verifymcp.io/servers/live-cityalert-cityalert/well-known-mcp)

## Channel facts

- Endpoint: `https://cityalert.live/.well-known/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.2`

## 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-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - 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**: 85/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 982 tokens (~109/item across 9 items; 8 tools + 1 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 80/100
  - Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 98/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 91% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).
  - Supports UI / widget rendering.

## Install

### How do I install the CityAlert MCP server?

CityAlert is a hosted endpoint at https://cityalert.live/.well-known/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.

### Claude

```bash
claude mcp add --transport http live-cityalert-cityalert 'https://cityalert.live/.well-known/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "live-cityalert-cityalert": {
      "url": "https://cityalert.live/.well-known/mcp"
    }
  }
}
```

### VS Code

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

### Codex

```toml
[mcp_servers.live-cityalert-cityalert]
url = "https://cityalert.live/.well-known/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "live-cityalert-cityalert": {
      "type": "remote",
      "url": "https://cityalert.live/.well-known/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add live-cityalert-cityalert --url 'https://cityalert.live/.well-known/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  live-cityalert-cityalert:
    url: "https://cityalert.live/.well-known/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "live-cityalert-cityalert": {
      "Transport": "http",
      "Url": "https://cityalert.live/.well-known/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add live-cityalert-cityalert -t streamable-http -u 'https://cityalert.live/.well-known/mcp'
```

### Other

```json
{
  "mcpServers": {
    "live-cityalert-cityalert": {
      "type": "http",
      "url": "https://cityalert.live/.well-known/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-11-04 (score 86, +1)

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

### 2026-11-01 (score 85, +1)

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

### 2026-10-30 (score 84, +1)

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

### 2026-10-28 (score 83, +1)

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

### 2026-10-26 (score 82, +1)

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

### 2026-10-24 (score 81, +1)

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

### 2026-10-22 (score 80, +1)

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

### 2026-10-20 (score 79, +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.

## MCP tools (8)

### `list_regions` (~32 tokens)

List focus regions

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

Output parameters:

- `regions` (array)

### `get_incidents` (~331 tokens)

Get live 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 (details: cityalert.live/developers).

Input parameters:

- `bbox` (array): [minLon, minLat, maxLon, maxLat]
- `category` (string): Incident category
- `detail` (string): Response detail. 'full' (default): every field incl. description, neighbourhood and reporter/vote metadata. 'compact': id/type/title/coords/time/severity/url only — about half the tokens, for list-st…
- `groups` (array): Normalized subtypes to include, e.g. ['violent','property','collision','wildfire']. See group keys in the /api/incidents OpenAPI doc.
- `limit` (integer): Max incidents to return (default 50)
- `minSeverity` (string): Minimum severity (low < medium < high < critical)
- `q` (string): Case-insensitive substring match on type/title/neighbourhood
- `refresh` (boolean): Re-fetch upstream feeds instead of returning the shared ~15-minute snapshot. Only honored for API keys with real-time entitlement; ignored otherwise.
- `region` (string): Focus-region key, e.g. 'vancouver' (see list_regions)
- `source` (string): Feed source, e.g. 'usgs', 'gdacs', 'eccc', 'vpd', 'bcws', 'vernon-media', 'manual'

Output parameters:

- `delayMinutes` (number)
- `delayed` (boolean)
- `feeds` (object)
- `incidents` (array)
- `region` (string)
- `returned` (number)
- `textTruncated` (string)
- `total` (number)

### `get_trends` (~78 tokens)

Get historical 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 cadence. For what's happening right now, use get_incidents.

Output parameters:

- `crime`
- `errors` (array)
- `gdacs` (array)
- `generatedAt` (string)
- `history` (object)
- `quakes` (array)
- `reports` (object)
- `snapshot` (object)
- `statcan`

### `get_crime_year` (~63 tokens)

Get Vancouver crime year

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

Input parameters:

- `includeIncidents` (boolean): Include every incident point (large; default false)
- `year` (integer, required): Year, 2003 to present

Output parameters:

- `byNeighbourhood` (array)
- `byType` (object)
- `incidents` (array)
- `total` (number)
- `year` (number)

### `get_news` (~64 tokens)

Get safety news

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

Input parameters:

- `place` (string): Place name for ad-hoc news, e.g. 'Kelowna'
- `refresh` (boolean): Bypass the news cache (API keys with real-time entitlement only)

Output parameters:

- `fetchedAt` (string)
- `items` (array)
- `place` (string)

### `submit_report` (~147 tokens)

Submit incident 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.

Input parameters:

- `category` (string): Incident category (default 'report')
- `description` (string): Details, up to 2000 chars
- `lat` (number, required): Latitude, -90 to 90
- `lon` (number, required): Longitude, -180 to 180
- `severity` (string): low | medium | high | critical (default 'medium')
- `title` (string, required): Short headline, 1–200 chars

Output parameters:

- `report` (object)

### `get_dashboard` (~28 tokens)

Get dashboard

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

Input parameters:

- `id` (string, required)

Output parameters:

- `id` (string)
- `name` (string)

### `create_dashboard` (~66 tokens)

Create dashboard

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

Input parameters:

- `config` (object, required): Dashboard config object, e.g. {areas, categories, defaultTab}
- `name` (string)

Output parameters:

- `id` (string)
- `token` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/live-cityalert-cityalert/well-known-mcp#diagnostics

## Score history

- 2026-11-05: 86
- 2026-11-04: 86
- 2026-11-03: 85
- 2026-11-02: 85
- 2026-11-01: 85
- 2026-10-31: 84
- 2026-10-30: 84
- 2026-10-29: 83
- 2026-10-28: 83
- 2026-10-27: 82
- 2026-10-26: 82
- 2026-10-25: 81
- 2026-10-24: 81
- 2026-10-23: 80
- 2026-10-22: 80
- 2026-10-21: 79
- 2026-10-20: 79
- 2026-10-19: 78
- 2026-10-18: 78
- 2026-10-17: 78
- 2026-10-16: 77
- 2026-10-15: 77
- 2026-10-14: 76
- 2026-10-13: 76
- 2026-10-12: 75
- 2026-10-11: 25

## Common questions

### What is the CityAlert MCP server?

CityAlert is an MCP server listed in the public MCP registry as live.cityalert/cityalert. Free live public-safety incident map: global crime, fire, disaster, weather and news feeds. This page covers its hosted endpoint (https://cityalert.live/.well-known/mcp).

### Is the CityAlert MCP server safe to use?

CityAlert scores 86 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 CityAlert MCP server expose?

CityAlert exposes 8 tools: list_regions, get_incidents, get_trends, get_crime_year, get_news, and 3 more. Their descriptions and schemas cost roughly 809 tokens of context every time the server is loaded.

### Does the CityAlert MCP server require authentication?

No. We connected to CityAlert without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the CityAlert MCP server still maintained?

CityAlert is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://cityalert.live/.well-known/mcp
- Repository: https://github.com/homezloco/cityalert
- Website: https://cityalert.live/
- Changelog RSS feed: https://verifymcp.io/servers/live-cityalert-cityalert/well-known-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/live-cityalert-cityalert/well-known-mcp.json
- HTML version of this page: https://verifymcp.io/servers/live-cityalert-cityalert/well-known-mcp