PublicSafetyAPI
PYPI · PUBLICSAFETYAPI-MCP
US police, fire, EMS and hospital locations near any address, from federal HIFLD data
Available components
Last scanned (9 minutes ago)
Scores higher than 84% of PyPI servers
Category Maps and Location
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 0 of 28 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 31 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 904 tokens (~150/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.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.
- 5 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 31 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 29 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 28 Oct 26 +1
- Stability: 0.97 → pass security
- 26 Oct 26 −16
- Malware scan: pass → unverified ▼ security
- Stability: pass → 0.93 functional
- 20 Oct 26 +1
- Stability: 0.97 → pass security
- 19 Oct 26 −1
- Stability: pass → 0.97 functional
- 18 Oct 26 +15
- Malware scan: unverified → pass ▲ security
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 · Analysed pypi/publicsafetyapi-mcp@0.1.3
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 28 packages
| Packages resolved | 28 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
find_stations_near_address ~155
Find the public safety facilities nearest to a US street address, sorted by distance. Args: address: Full US street address, e.g. "350 Fifth Ave, New York, NY" type: Optional filter — "fire", "police", "ems", or "hospital". Comma-separate for several; omit to return all types. radius_miles: Search radius in miles (0.1–50, default 10) limit: Maximum facilities to return (1–25, default 5)
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
| limit | integer | – | – |
| radius_miles | number | – | – |
| type | string | – | – |
No output schema declared.
No examples provided.
find_stations_near_coordinates ~171
Find the public safety facilities nearest to a latitude/longitude, sorted by distance. Use this when you already have coordinates; it skips geocoding and is faster than find_stations_near_address. Args: lat: Latitude (WGS84) lng: Longitude (WGS84) type: Optional filter — "fire", "police", "ems", or "hospital" radius_miles: Search radius in miles (0.1–50, default 10) limit: Maximum facilities to return (1–25, default 5)
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number | yes | – |
| limit | integer | – | – |
| lng | number | yes | – |
| radius_miles | number | – | – |
| type | string | – | – |
No output schema declared.
No examples provided.
get_jurisdiction ~168
Determine which Census-defined place (city/town) contains a location, and which agencies most likely respond there. Returns the place name, state, Census GEOID, boundary type, and a `likelyAgencies` list of nearby police, fire, EMS, and hospital facilities. Useful for routing, coverage reporting, or working out which local government and responders serve an address. Provide either an address, or a lat/lng pair. Args: address: Full US street address (geocoded automatically) lat: Latitude (WGS84) — use with lng instead of address lng: Longitude (WGS84) — use with lat instead of address
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | – |
| lat | – | – | – |
| lng | – | – | – |
No output schema declared.
No examples provided.
get_state_summary ~53
Get facility counts by type (fire, police, EMS, hospital) for one state. Args: state_code: Two-letter state abbreviation, e.g. "CA"
| Name | Type | Req | Description |
|---|---|---|---|
| state_code | string | yes | – |
No output schema declared.
No examples provided.
get_station ~67
Get the full record for one facility by its ID, including address, phone, coordinates, and (for hospitals) beds, trauma level, and ownership. Args: station_id: Facility ID, e.g. "fire_CA_12345"
| Name | Type | Req | Description |
|---|---|---|---|
| station_id | string | yes | – |
No output schema declared.
No examples provided.
list_stations ~199
List or search public safety facilities by type, state, name, or ZIP. Use this for questions like "how many fire stations are in Kansas" or to find a facility by name. For "what's nearest to X", use find_stations_near_address instead. Args: type: "fire", "police", "ems", or "hospital" (comma-separate for several) state: Two-letter state code, e.g. "CA" name: Full-text search on the facility name zip: 5-digit ZIP code limit: Results per page (1–100, default 25) offset: Pagination offset (default 0)
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| name | string | – | – |
| offset | integer | – | – |
| state | string | – | – |
| type | string | – | – |
| zip | string | – | – |
No output schema declared.
No examples provided.
How do I install the PublicSafetyAPI MCP server?
PublicSafetyAPI runs locally as a PyPI package, launched with uvx publicsafetyapi-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · publicsafetyapi-mcp
claude mcp add dev-publicsafetyapi-publicsafetyapi-mcp -- uvx publicsafetyapi-mcp
What is the PublicSafetyAPI MCP server?
PublicSafetyAPI is an MCP server listed in the public MCP registry as dev.publicsafetyapi/publicsafetyapi-mcp. US police, fire, EMS and hospital locations near any address, from federal HIFLD data. This page covers its PyPI package (publicsafetyapi-mcp).
Is the PublicSafetyAPI MCP server safe to use?
PublicSafetyAPI scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. 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 PublicSafetyAPI MCP server expose?
PublicSafetyAPI exposes 6 tools: find_stations_near_address, find_stations_near_coordinates, get_station, list_stations, get_jurisdiction, get_state_summary. Their descriptions and schemas cost roughly 813 tokens of context every time the server is loaded.
Is the PublicSafetyAPI MCP server still maintained?
PublicSafetyAPI 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.
What licence is the PublicSafetyAPI MCP server under?
PublicSafetyAPI declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.