Compatible with every major AI agent and IDE
What is the FBI Crime Data Explorer MCP Server?
Connect to the FBI Crime Data Explorer (CDE) to retrieve comprehensive law enforcement statistics directly through natural language. This server provides access to the Uniform Crime Reporting (UCR) program's extensive datasets.
What you can do
- National Estimates — Retrieve estimated crime totals for the entire United States across specific year ranges.
- State Summaries — Fetch detailed offense data (violent crime, property crime, etc.) for any specific US state.
- Agency-Level Data — Query statistics reported by specific local, county, or state law enforcement agencies using their unique ORI identifier.
- Victim Demographics — Analyze NIBRS data to see breakdowns of victims by age, race, and sex for various offenses.
How it works
- Subscribe to this server
- Enter your FBI CDE API Key
- Start querying public safety data from Claude, Cursor, or any MCP client
Who is this for?
- Data Analysts & Researchers — quickly pull structured crime data for academic or professional reports.
- Journalists — verify crime statistics and trends for specific regions or agencies instantly.
- Policy Makers — evaluate the impact of safety initiatives using official historical data.
Built-in capabilities (4)
Retrieve crime data for a specific law enforcement agency
Retrieve national crime estimates
Retrieve NIBRS victim demographic data
Retrieve crime statistics for a specific state
Why CrewAI?
When paired with CrewAI, FBI Crime Data Explorer becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call FBI Crime Data Explorer tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.
- —
Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools
- —
CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the
mcpsparameter and agents auto-discover every available tool at runtime - —
Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls
- —
Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports
FBI Crime Data Explorer in CrewAI
FBI Crime Data Explorer and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect FBI Crime Data Explorer to CrewAI through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for FBI Crime Data Explorer in CrewAI
The FBI Crime Data Explorer MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 4 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in CrewAI only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
FBI Crime Data Explorer for CrewAI
Every tool call from CrewAI to the FBI Crime Data Explorer MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I find data for a specific local police department?
You can use the get_agency_summarized tool. You will need the agency's 9-character ORI (Originating Agency Identifier) to retrieve their specific reported statistics.
What kind of demographic information is available for crime victims?
The get_nibrs_victim_demographics tool allows you to filter victim data by age, race, or sex for specific offenses in states that support NIBRS reporting.
Can I compare crime trends over multiple years?
Yes. Tools like get_national_estimates and get_state_summarized accept start_year and end_year parameters to provide data across a historical range.
How does CrewAI discover and connect to MCP tools?
CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.
Can different agents in the same crew use different MCP servers?
Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.
What happens when an MCP tool call fails during a crew run?
CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.
Can CrewAI agents call multiple MCP tools in parallel?
CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.
Can I run CrewAI crews on a schedule (cron)?
Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.
MCP tools not discovered
Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.
Agent not using tools
Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".
Timeout errors
CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.
Rate limiting or 429 errors
Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.
Explore More MCP Servers
View all →
PagerDuty
11 toolsManage incidents, services, on-call schedules, and escalation policies via PagerDuty — trigger, acknowledge, and resolve alerts from any AI agent.

Simian
12 toolsVideo sharing and collaboration platform.

Polygon.io
6 toolsAccess real-time and historical stock market data, including trades, quotes, aggregates, and company metadata directly via AI.

AccuWeather
10 toolsEnterprise-grade weather intelligence — current conditions, forecasts, alarms, and activity indices via AI.
