# CityAlert (remote · cityalert.live)

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

- Trust score: 69/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-28

## Components

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

## Channel facts

- Endpoint: `https://cityalert.live/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.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-09-28.

- **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 8 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**: 72/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 635 tokens (~79/item across 8 items; 8 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 88/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 64% of tool parameters carry a description.
- **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 8 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).

## Install

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

CityAlert is a hosted endpoint at https://cityalert.live/api/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/api/mcp'
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "live-cityalert-cityalert": {
      "type": "http",
      "url": "https://cityalert.live/api/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-09-28 (score 69, 0)

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

### 2026-09-27 (score 69, +3)

- [security improvement] HSTS header: unverified → pass
- [security] Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
- [cosmetic] “get_news” reworded the description of “refresh”

### 2026-09-26 (score 66, −2)

- [security regression] HSTS header: pass → unverified
- [security] Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.

### 2026-09-25 (score 68, 0)

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

### 2026-09-24 (score 68, +1)

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

### 2026-09-22 (score 67, +1)

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

### 2026-09-21 (score 66, 0)

- [security] Tool “get_incidents” rewrote its description, which is the text the model reads

### 2026-09-20 (score 66, 0)

- [functional improvement] Stability: unverified → 0.03

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

### `get_incidents` (~268 tokens)

Get live incidents

Merged live incidents from all feeds plus manual reports. Filter by region key, category, group, severity, source, or bbox. Anonymous and free-key calls get a shared ~1-minute snapshot; a pro/business x-api-key header (from cityalert.live/account) unlocks real-time refresh and higher limits.

Input parameters:

- `bbox` (array): [minLon, minLat, maxLon, maxLat]
- `category` (string): Incident category
- `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 250)
- `minSeverity` (string): Minimum severity (low < medium < high < critical)
- `q` (string): Case-insensitive substring match on type/title/neighbourhood
- `refresh` (boolean): Bypass the feed cache and re-fetch sources
- `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'

### `get_trends` (~50 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.

### `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

### `get_news` (~61 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 (pro/business keys only)

### `submit_report` (~67 tokens)

Submit incident report

File a manual geolocated incident report (same as POST /api/reports).

Input parameters:

- `category` (string)
- `description` (string)
- `lat` (number, required)
- `lon` (number, required)
- `severity` (string)
- `title` (string, required)

### `get_dashboard` (~28 tokens)

Get dashboard

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

Input parameters:

- `id` (string, required)

### `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)

## Diagnostics

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

## Score history

- 2026-09-28: 69
- 2026-09-27: 69
- 2026-09-26: 66
- 2026-09-25: 68
- 2026-09-24: 68
- 2026-09-23: 67
- 2026-09-22: 67
- 2026-09-21: 66
- 2026-09-20: 66
- 2026-09-19: 66

## 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/api/mcp).

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

CityAlert scores 69 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 635 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 28 September 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/api/mcp
- Repository: https://github.com/homezloco/cityalert
- Website: https://cityalert.live/
- Changelog RSS feed: https://verifymcp.io/servers/live-cityalert-cityalert/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/live-cityalert-cityalert/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/live-cityalert-cityalert/api-mcp