Open data from the Missouri Vehicle Stops Report
Traffic stops are how most people experience policing. This data shows who gets stopped, why, and what happens next—revealing how traffic enforcement varies across Missouri’s agencies.
Key findings
Missouri law enforcement made 1.28 million traffic stops in 2024
Vehicle stops have been on an overall downward trend, but still rebounded after the pandemic.
Consent searches have been dropping since the early 2010s
Law enforcement officers are carrying out discretionary searches less often.
Black drivers were involved in 17% of stops in 2024, but represent less than 11% of Missouri's population
Black drivers have the largest disparity in stops vs. percentage of the state population.
Law enforcement issues citations at a rate of 41 per 100 stops, down from a peak of around 60 a decade ago
Outcome rates are computed against total stops. A single stop may have multiple outcomes.
Stop outcomes (citations, arrests, warnings, no action) were not reported before 2004.
How Agencies Compare
Showing 0 agencies (out of 0).
Download the data
Download the complete Missouri Vehicle Stop Report dataset for your own analysis.
v2 (2000–2024)
CSV
Spreadsheet-compatible. Works with Excel, Google Sheets, etc.
Vehicle stops report statistics by agency 878 MBAgency comments by year 448 KBAgency list 137 KBParquet
Efficient columnar format. Best for Python, R, or SQL analysis.
Vehicle stops report statistics by agency 69.4 MBAgency comments by year 100 KBAgency list 63.5 KBWide format — one row per agency-year
Every metric flattened into named columns (about 1,450 of them, shaped as <metric>_<race>). Built for Excel and Google Sheets, where filtering and pivoting is easier on wide tables than long ones.
One year at a time
Smaller files, easier to scan if you only need recent years.
CSV — 2024 1.8 MB Parquet — 2024 1.7 MBv1 — Previous release (2020–2024)
See the About the Data section for usage details, methodology, and more downloads.
Love our work? Hire us for your next data project.
Get in touchQuery the data from any MCP client
Connect any MCP-compatible AI assistant — Claude Desktop, Cursor, ChatGPT, and more — to this dataset. Ask in plain English for trends, comparisons, and maps; the model explains what each metric means and what it doesn't, explains fundamental data limitations, and shares links to resources about the methods used.
Provisional service — verify your work
This MCP server is offered as-is. No warranty, no uptime guarantee, and tool behavior may change without notice. Treat every numeric claim as something to verify against the published source data before publishing.
Try asking…
- Which Missouri agencies have rising Hispanic stop share over the last five years?
- Show me agencies with high contraband hit rates and low search rates.
- Map search rates across St. Louis-area agencies in 2023.
Usage limits
Free and public, with hard rate limits (600 requests per 5 minutes per IP) for the time being.
Usage tracking consists of anonymous counts of tool calls and their arguments, so we can see which queries and agencies are popular. These are stored in the EU using Umami with all identifying information stripped.
Connect your client
Add this to your Claude Desktop config and restart the app:
- macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
- Windows: %APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"missouri-vsr": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.vsr.recoveredfactory.net/"
]
}
}
}