CityAlert
REMOTE · CITYALERT.LIVE
Free live public-safety incident map: global crime, fire, disaster, weather and news feeds
Available components
Last scanned (3 hours ago)
Scores higher than 93% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Maps and Location
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- 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 Usability85
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 982 tokens (~109/item across 9 items; 8 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 91% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
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 10 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
- Supports UI / widget rendering.Pass
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.
- 4 Nov 26 +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.
- 1 Nov 26 +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.
- 30 Oct 26 +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.
- 28 Oct 26 +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.
- 26 Oct 26 +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.
- 24 Oct 26 +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.
- 22 Oct 26 +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.
- 20 Oct 26 +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.
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 5 Nov 2026 · Probed https://cityalert.live/.well-known/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 | 4724, 36322 | 8, 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/.well-known/mcp | Verified | 200 | |
| http (plaintext) | http://cityalert.live/.well-known/mcp | HTTPS enforced | 301 | https://cityalert.live/.well-known/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 | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| token | string | – | – |
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 |
| Name | Type | Req | Description |
|---|---|---|---|
| byNeighbourhood | array | yes | – |
| byType | object | yes | – |
| incidents | array | – | – |
| total | number | yes | – |
| year | number | yes | – |
No examples provided.
get_dashboard Get dashboard ~28
Read a saved dashboard by id (shareable, read-only).
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| name | string | – | – |
No examples provided.
get_incidents Get live incidents ~331
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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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' |
| Name | Type | Req | Description |
|---|---|---|---|
| delayMinutes | number | – | – |
| delayed | boolean | – | – |
| feeds | object | yes | – |
| incidents | array | yes | – |
| region | string | – | – |
| returned | number | yes | – |
| textTruncated | string | – | – |
| total | number | yes | – |
No examples provided.
get_news Get safety news ~64
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 (API keys with real-time entitlement only) |
| Name | Type | Req | Description |
|---|---|---|---|
| fetchedAt | string | – | – |
| items | array | yes | – |
| place | string | – | – |
No examples provided.
get_trends Get historical trends ~78
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| crime | – | – | – |
| errors | array | – | – |
| gdacs | array | – | – |
| generatedAt | string | – | – |
| history | object | – | – |
| quakes | array | – | – |
| reports | object | – | – |
| snapshot | object | – | – |
| statcan | – | – | – |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| regions | array | yes | – |
No examples provided.
submit_report Submit incident report ~147
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.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Incident category (default 'report') |
| description | string | – | Details, up to 2000 chars |
| lat | number | yes | Latitude, -90 to 90 |
| lon | number | yes | Longitude, -180 to 180 |
| severity | string | – | low | medium | high | critical (default 'medium') |
| title | string | yes | Short headline, 1–200 chars |
| Name | Type | Req | Description |
|---|---|---|---|
| report | object | yes | – |
No examples provided.
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.
remote · cityalert.live
claude mcp add --transport http live-cityalert-cityalert 'https://cityalert.live/.well-known/mcp'
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.