CrimeMetric
Server Details
Modeled crime rates per resident for U.S. addresses: 16 crime types vs the U.S., with 80% intervals.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 9 tools
Most tools occupy clearly distinct niches: point-level index (crime_index), city-level profile (place_profile), neighborhood breakdown (place_block_groups), record counts (incident_stats) vs. individual records (nearby_incidents), plus free reference/geocoding helpers. The only real overlap is crime_index vs crime_index_batch, and the description explicitly explains when to use each, so the boundary is legible.
All names are snake_case and follow a resource-first pattern (crime_index, place_profile, incident_stats, data_coverage), which is predictable and readable. The lone deviation is find_places, a verb-led name in an otherwise noun-led set, which is a minor inconsistency rather than a confusing one.
Nine tools is well within the sweet spot and each earns its place: two free orientation tools, one free reference tool, one free city profile, and a small set of paid data tools with a clear batch variant. Nothing looks redundant or padded.
The surface covers the full lifecycle of the domain: definitions/plan rules, coverage checks, place lookup, point indexes, city profiles, neighborhood breakdowns, and both aggregated counts and raw incident records, with a batch path for volume. Minor gaps remain — no explicit multi-place comparison tool, no standalone historical/time-series query, and no plan/usage or key-management tool despite frequent plan-limit references.
Available Tools
9 toolscrime_definitionsCrime definitionsARead-onlyInspect
What every crime, summary, record type and license class means, plan limits, and the usage rules. Free.
Inputs: no named parameters.
crime_indexCrime indexARead-onlyInspect
Crime indexes for the 2020 census block group at a U.S. location. Pass exactly one of: address, lat and lon, or bg_geoid (12 digits). Returns 16 crimes and four summaries with expected annual counts, indexes (100 = U.S. rate per resident), 80% intervals, confidence, national percentiles, city and county comparisons, and notes.
Inputs: lat, lon, address, bg_geoid.
crime_index_batchCrime index for several locationsBRead-onlyInspect
crime_index for up to 10 locations at once; each successful one counts as a call. Developer and Business plans; on the free plan, call crime_index once per location.
Inputs: locations (required).
data_coverageData coverageBRead-onlyInspect
Which police agencies publish records near a point, which record types, and how fresh (last 90 days, within 1 km). Free, no key needed. Use it before reading too much into a low count.
Inputs: to, lat, lon, from, +2 more.
find_placesFind placesARead-onlyInspect
Search U.S. cities, towns and CDPs by name (and state), largest first. Free, no key needed. Returns place_id values for place_profile and place_block_groups.
Inputs: limit, query, state.
incident_statsIncident countsARead-onlyInspect
Counts of police-published records around a point by type and record type, by month, and against the same-length period before, with the sources behind them. Counts describe published records, not all crime.
Inputs: to, lat, lon, from, +5 more.
nearby_incidentsNearby incidentsARead-onlyInspect
Police-published incident records around an address or point, newest first: what, when, block-level address, type, record type and source, typed as crimemetric.com's city pages type them. Sensitive cases come without a location. Calls (calls for service, and records that read as calls) are left out unless include_calls is true. Developer and Business plans; on the free plan, use incident_stats for counts.
Inputs: to, lat, lon, from, +7 more.
place_block_groupsBlock groups in a placeARead-onlyInspect
Every census block group inside a place with its index for one measure (default total_major), 80% interval, percentile and confidence. Use it to describe how crime varies across a city.
Inputs: place_id (required), sort, crime.
place_profilePlace profileARead-onlyInspect
City-level crime indexes for a place: four summaries and 16 crimes (index, expected count, change over one year and to the projection year, spread across neighborhoods), time of week, confidence and the data-quality gate. Free, no key needed.
Inputs: place_id (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
US crime scores, incidents, neighborhood demographics, rent data, and offender search by address.
Crime estimates by type, state arrest data, and national crime trends from the FBI UCR
FBI Crime Data Explorer — offense rates, hate crime, arrests, NIBRS, LEOKA stats, agency search.
US neighborhood Safety Scores, score drivers, geocoding and nearby activity from CrimeScore.io.
Related MCP Servers
- AlicenseAqualityCmaintenanceUS crime safety scores, recent incidents, neighborhood demographics, rent data, and registered-offender search by address. Free tier available.4MIT
- FlicenseNot gradedqualityDmaintenanceProperty intelligence API for US real estate. Returns 16+ data points for any US address: noise levels, wetlands, slope, natural light, powerline proximity, crime rates, property facing direction, zoning, public record, radon risk, natural hazards (earthquake, flood, wildfire), neighborhood demographics, falling tree risk, RF/cell tower exposure, and nearby school.-
- FlicenseNot gradedqualityDmaintenanceProvides measured vertical ground motion (subsidence and uplift) for US addresses using NASA OPERA Sentinel-1 InSAR data.-

perilpulseofficial
AlicenseNot gradedqualityCmaintenanceProvides per-property multi-peril risk scores (flood, wildfire, wind, hail, crime, etc.) for an address, returning A-F grades and 0-100 scores across 25+ hazard types for insurance underwriting and due diligence.297 npmMIT
Glama MCP Gateway
Add one secure layer between your agents and this server.