CityAlert
REMOTE · CITYALERT.LIVE · SCANNED SEP 28
Free live public-safety incident map: global crime, fire, disaster, weather and news feeds
Available components
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability72
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 635 tokens (~79/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage88
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 64% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
remote · cityalert.live
claude mcp add --transport http live-cityalert-cityalert 'https://cityalert.live/api/mcp'
{
"mcpServers": {
"live-cityalert-cityalert": {
"url": "https://cityalert.live/api/mcp"
}
}
} {
"servers": {
"live-cityalert-cityalert": {
"type": "http",
"url": "https://cityalert.live/api/mcp"
}
}
} [mcp_servers.live-cityalert-cityalert] url = "https://cityalert.live/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"live-cityalert-cityalert": {
"type": "remote",
"url": "https://cityalert.live/api/mcp",
"enabled": true
}
}
} openclaw mcp add live-cityalert-cityalert --url 'https://cityalert.live/api/mcp' --transport streamable-http
mcp_servers:
live-cityalert-cityalert:
url: "https://cityalert.live/api/mcp" {
"McpServers": {
"live-cityalert-cityalert": {
"Transport": "http",
"Url": "https://cityalert.live/api/mcp"
}
}
} assistant mcp add live-cityalert-cityalert -t streamable-http -u 'https://cityalert.live/api/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 +3
- 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. security
- “get_news” reworded the description of “refresh” cosmetic
- 26 Sept 26 −2
- HSTS header: pass → unverified ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +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.
- 22 Sept 26 +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.
- 21 Sept 26 0
- Tool “get_incidents” rewrote its description, which is the text the model reads security
- 20 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 28 Sept 2026 · Probed https://cityalert.live/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=cityalert.live | CN=YE1,O=Let's Encrypt,C=US | 16 Sept 2026 | 15 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 69919c69e9f2b5e5401fe7048e0c3f63507 |
| SANs: *.cityalert.live, cityalert.live | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of cityalert.live. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| live. | present | 36322 | 8 | Verified |
| cityalert.live. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=2592000 |
| content-security-policy | frame-ancestors 'self' |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://cityalert.live/api/mcp | Verified | 200 | |
| http (plaintext) | http://cityalert.live/api/mcp | HTTPS enforced | 301 | https://cityalert.live/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
create_dashboard Create dashboard ~66
Create a shareable dashboard. Returns {id, token} — the token grants write access via PUT /api/dashboards, so save it.
| Name | Type | Req | Description |
|---|---|---|---|
| config | object | yes | Dashboard config object, e.g. {areas, categories, defaultTab} |
| name | string | – | – |
No output schema declared.
No examples provided.
get_crime_year Get Vancouver crime year ~63
Full-year VPD crime data: totals and ranked neighbourhood stats. Vancouver only, 2003-present.
| Name | Type | Req | Description |
|---|---|---|---|
| includeIncidents | boolean | – | Include every incident point (large; default false) |
| year | integer | yes | Year, 2003 to present |
No output schema declared.
No examples provided.
get_dashboard Get dashboard ~28
Read a saved dashboard by id (shareable, read-only).
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
get_incidents Get live incidents ~268
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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' |
No output schema declared.
No examples provided.
get_news Get safety news ~61
Per-region safety news items, or news for an arbitrary place name.
| Name | Type | Req | Description |
|---|---|---|---|
| place | string | – | Place name for ad-hoc news, e.g. 'Kelowna' |
| refresh | boolean | – | Bypass the news cache (pro/business keys only) |
No output schema declared.
No examples provided.
get_trends Get historical trends ~50
Historical aggregates: VPD crime by year/month/type (6y), USGS M4+ quakes per region (10y), GDACS global events (3y), report and live snapshot stats.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_regions List focus regions ~32
List CityAlert focus regions (key, label, center, zoom, bbox). Use region keys with get_incidents.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
submit_report Submit incident report ~67
File a manual geolocated incident report (same as POST /api/reports).
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| description | string | – | – |
| lat | number | yes | – |
| lon | number | yes | – |
| severity | string | – | – |
| title | string | yes | – |
No output schema declared.
No examples provided.
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.