# PublicSafetyAPI (pypi · publicsafetyapi-mcp)

US police, fire, EMS and hospital locations near any address, from federal HIFLD data

- Trust score: 65/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-20

## Components

- pypi · `publicsafetyapi-mcp`: 65/100 (this document), [markdown](https://verifymcp.io/servers/dev-publicsafetyapi-publicsafetyapi-mcp/publicsafetyapi-mcp.md), [page](https://verifymcp.io/servers/dev-publicsafetyapi-publicsafetyapi-mcp/publicsafetyapi-mcp)

## Channel facts

- Registry: `pypi`
- Package: `publicsafetyapi-mcp`
- Version: `0.1.2`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-20.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it.
  - 1 of 30 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 3 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

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

## Install

### Claude

```bash
claude mcp add dev-publicsafetyapi-publicsafetyapi-mcp -- uvx publicsafetyapi-mcp
```

### Codex

```bash
codex mcp add dev-publicsafetyapi-publicsafetyapi-mcp -- uvx publicsafetyapi-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-publicsafetyapi-publicsafetyapi-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "publicsafetyapi-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-publicsafetyapi-publicsafetyapi-mcp --command uvx --arg publicsafetyapi-mcp
```

### Hermes

```yaml
mcp_servers:
  dev-publicsafetyapi-publicsafetyapi-mcp:
    command: "uvx"
    args: ["publicsafetyapi-mcp"]
```

### Other

```json
{
  "mcpServers": {
    "dev-publicsafetyapi-publicsafetyapi-mcp": {
      "command": "uvx",
      "args": [
        "publicsafetyapi-mcp"
      ]
    }
  }
}
```

## 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-08-16 (score 65)

First indexed and scored.

## MCP tools (6)

### `find_stations_near_address` (~155 tokens)

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)

Input parameters:

- `address` (string, required)
- `limit` (integer)
- `radius_miles` (number)
- `type` (string)

### `find_stations_near_coordinates` (~171 tokens)

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)

Input parameters:

- `lat` (number, required)
- `limit` (integer)
- `lng` (number, required)
- `radius_miles` (number)
- `type` (string)

### `get_station` (~67 tokens)

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"

Input parameters:

- `station_id` (string, required)

### `list_stations` (~199 tokens)

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)

Input parameters:

- `limit` (integer)
- `name` (string)
- `offset` (integer)
- `state` (string)
- `type` (string)
- `zip` (string)

### `get_jurisdiction` (~168 tokens)

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

Input parameters:

- `address` (string)
- `lat`
- `lng`

### `get_state_summary` (~53 tokens)

Get facility counts by type (fire, police, EMS, hospital) for one state.

Args:
    state_code: Two-letter state abbreviation, e.g. "CA"

Input parameters:

- `state_code` (string, required)

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/dev-publicsafetyapi-publicsafetyapi-mcp/publicsafetyapi-mcp#diagnostics

## Score history

- 2026-08-20: 65
- 2026-08-19: 65
- 2026-08-18: 65
- 2026-08-17: 65
- 2026-08-16: 65

## Links

- PyPI project: https://pypi.org/project/publicsafetyapi-mcp/
- Socket report: https://socket.dev/pypi/package/publicsafetyapi-mcp
- Repository: https://github.com/public-safety-api/publicsafetyapi-mcp
- Website: https://publicsafetyapi.dev/
- Changelog RSS feed: https://verifymcp.io/servers/dev-publicsafetyapi-publicsafetyapi-mcp/publicsafetyapi-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-publicsafetyapi-publicsafetyapi-mcp/publicsafetyapi-mcp.json
- HTML version of this page: https://verifymcp.io/servers/dev-publicsafetyapi-publicsafetyapi-mcp/publicsafetyapi-mcp