A
licenseNot graded
qualityB
maintenanceEnables querying FBI crime data using UCR/NIBRS statistics through a simple MCP interface.
24 npm
MIT
fbi-crime-mcp-server
Server Details
FBI Crime Data Explorer — UCR offense rates and counts, plus LEOKA officer-safety statistics.
If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- Repository
- cyanheads/fbi-crime-mcp-server
- GitHub Stars
- 1
- Server Listing
- fbi-crime-mcp-server
TDQS
Score is being calculated.
Available Tools
2 toolsfbi_get_crime_estimatesFBI Get Crime EstimatesRead-onlyIdempotentInspect
Monthly offense rates (per 100k population), raw counts, population denominators and provider reporting coverage from FBI CDE. National scope omits identifiers; state requires only state_abbr; agency requires only ori. Identifiers are case-insensitive; start must be no later than end. Missing coverage stays null and participation may be incomplete. Offenses: violent-crime, property-crime, robbery, burglary, larceny, motor-vehicle-theft, arson, aggravated-assault, rape, homicide.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| ori | No | Nine ASCII-letter/digit ORI code (e.g. CA0010400, DCMPD0000); case-insensitive. Only permitted and required for agency scope. | |
| scope | Yes | Geographic scope: national (omit identifiers), state (only state_abbr), or agency (only ori). | |
| offense | Yes | Offense type: violent-crime, property-crime, robbery, burglary, larceny, motor-vehicle-theft, arson, aggravated-assault, rape, or homicide. | |
| to_year | Yes | End year of the data range (inclusive). | |
| to_month | No | End month (1–12). Defaults to December. | |
| from_year | Yes | Start year of the data range (inclusive). The API uses monthly granularity. | |
| from_month | No | Start month (1–12). Defaults to January. | |
| state_abbr | No | Two ASCII-letter state abbreviation (e.g. CA, DC, PR); case-insensitive. Only permitted and required for state scope. |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| to | No | End of data range (MM-YYYY). |
| ori | No | ORI code when scope is "agency". |
| from | No | Start of data range (MM-YYYY). |
| error | No | Present when the call failed. Absent on success. |
| scope | No | Geographic scope. |
| months | No | Monthly data rows sorted chronologically. |
| offense | No | Offense type queried. |
| state_abbr | No | State abbreviation when scope is "state". |
| entity_name | No | Provider entity selected from scoped offense actuals. |
| total_months | No | Number of months returned. |
| max_data_date | No | Latest data date reported by CDE, in the provider format. |
| data_last_updated | No | Date the CDE last refreshed this data. |
fbi_get_leokaFBI Get LEOKARead-onlyIdempotentInspect
LEOKA officer fatality trends, weapons, activity, circumstances, demographics, geographic regions, and time-of-day/month breakdowns. Period "ytd" requests a year; "monthly" requires month and includes comparison-year monthly series. Both periods return the CDE YTD totals block, separately from month-specific breakdowns. Raw dod/doi totals have unspecified interpretation; classified deaths remain in the trend and region series.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| year | Yes | Year to retrieve LEOKA data for. Required — the API does not default to a year. | |
| month | No | Month number (1–12). Required for monthly; must be omitted for YTD. | |
| period | Yes | Data period: ytd for the year, monthly for month-specific breakdowns and comparison years. Both include the CDE YTD totals block. |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| year | No | The data year requested. |
| error | No | Present when the call failed. Absent on success. |
| month | No | The data month, when period is "monthly". |
| period | No | The requested data period. |
| totals | No | Raw incidents_victim_officer_totals_ytd block, including in monthly responses. Not combined fatalities or requested-month totals. |
| weapons | No | Count by weapon type (e.g. Handguns, Rifles, Vehicle). |
| deaths_by_year | No | Annual officer death totals by type. Keys: "Felonious", "Accidental". Values: { "2022": 61, ... } |
| body_armor_worn | No | Body armor worn category to count; null counts are unavailable. |
| deaths_by_region | No | Officer death counts by killing type then region. Keys: "Felonious", "Accidental". Values: { "South": 31, "West": 12, ... } |
| officer_activity | No | Count by what the officer was doing at the time of the incident. |
| location_of_attack | No | Location of attack category to count; all reported categories are retained. |
| weather_conditions | No | Weather condition to count. |
| lighting_conditions | No | Count by lighting conditions at time of incident. |
| officer_demographic | No | Officer demographic dimension to category to count; null groups and counts are unavailable. |
| offender_demographic | No | Offender demographic dimension to category to count; null groups and counts are unavailable. |
| officer_incident_type | No | Officer incident type to count. |
| officer_death_by_month | No | Killing type to year to month to count. Includes returned comparison years and zero values without filtering. |
| officer_type_of_assignment | No | Officer assignment type to count. |
| offender_prior_relationship | No | Offender prior relationship category to count. |
| officer_death_by_time_of_day | No | Killing type to hour key to count. Hour keys, including -1, are preserved literally. |
| offender_prior_mental_illness | No | Offender prior mental illness category to count. |
| offender_previously_known_to_agency | No | Previously known offender category to count. |
| officer_circumstances_time_of_attack | No | Circumstance at time of attack category to count. |
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
2 tool updates
- First observed
fbi_get_crime_estimates - First observed
fbi_get_leoka
Related MCP Connectors
FBI Crime Data Explorer MCP — UCR/NIBRS statistics
Crime estimates by type, state arrest data, and national crime trends from the FBI UCR
National crime incident estimates from NIBRS by offense type, weapon, and location
US crime scores, incidents, neighborhood demographics, rent data, and offender search by address.
Related MCP Servers
- AlicenseAqualityAmaintenanceProvides access to FBI Crime Data Explorer API, enabling queries for crime statistics, arrests, hate crimes, NIBRS incidents, law enforcement employment, and more via 17 tools with smart caching and spillover handling.171MIT
- AlicenseAqualityBmaintenanceUS crime safety scores, recent incidents, neighborhood demographics, rent data, and registered-offender search by address. Free tier available.4MIT
- AlicenseNot gradedqualityBmaintenanceEnables searching the FBI's official wanted-persons database and retrieving full profiles — including physical descriptions, aliases, cautions, rewards, and images — for fugitives, Ten Most Wanted fugitives, cyber and terrorism suspects, white-collar cases, and kidnappings or missing persons. Queries are keyless and can be made over MCP or plain HTTP, with no account required for the first calls.20 npmMIT
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd
Glama MCP Gateway
Add one secure layer between your agents and this server.