PublicSafetyAPI
PYPI · PUBLICSAFETYAPI-MCP · SCANNED AUG 20
US police, fire, EMS and hospital locations near any address, from federal HIFLD data
Available components
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 →
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 native-build step with no shell scripting around it. View diagnostics → Pass
- 1 of 30 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- 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 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
pypi · publicsafetyapi-mcp
claude mcp add dev-publicsafetyapi-publicsafetyapi-mcp -- uvx publicsafetyapi-mcp
codex mcp add dev-publicsafetyapi-publicsafetyapi-mcp -- uvx publicsafetyapi-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-publicsafetyapi-publicsafetyapi-mcp": {
"type": "local",
"command": [
"uvx",
"publicsafetyapi-mcp"
],
"enabled": true
}
}
} openclaw mcp add dev-publicsafetyapi-publicsafetyapi-mcp --command uvx --arg publicsafetyapi-mcp
mcp_servers:
dev-publicsafetyapi-publicsafetyapi-mcp:
command: "uvx"
args: ["publicsafetyapi-mcp"] {
"mcpServers": {
"dev-publicsafetyapi-publicsafetyapi-mcp": {
"command": "uvx",
"args": [
"publicsafetyapi-mcp"
]
}
}
} 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.
- 16 Aug 26 65
First indexed and scored.
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 20 Aug 2026 · Analysed pypi/publicsafetyapi-mcp@0.1.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Dependencies 30 packages
| Packages resolved | 30 |
|---|---|
| Stale | 1 |
| Tree resolution | Complete |
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.
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.