
Connects to the FBI's public Wanted API through Pipeworx's gateway infrastructure. The source doesn't list specific tools, but given the FBI Wanted context, you're likely getting operations to search for wanted persons, retrieve case details, and filter by categories like most wanted, cyber crimes, or terrorism. Useful when you need Claude to pull live FBI data for research, fact checking, or building investigative workflows. Part of Pipeworx's larger gateway that bundles 853+ data sources, so you can either use this standalone or tap into the full collection. Supports the ask_pipeworx natural language interface if you'd rather describe what you want than call tools directly.
FBI Wanted MCP.
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
| Tool | Description |
|---|---|
search_wanted | Search the FBI's Wanted persons database — fugitives, Most Wanted, cyber's-most-wanted, terrorists, white-collar suspects, kidnappings/missing persons, and law-enforcement-assistance cases. Returns compact records with reward, warning, and image. Keyless, official FBI data. |
get_wanted | Get the full FBI Wanted profile for one person by uid — physical description, aliases, occupations, caution/remarks/details (plain text), reward, field offices, and images. Keyless, official FBI data. |
most_wanted | The FBI's Ten Most Wanted Fugitives. Returns the current top-ten list with reward, warning, and image for each. Keyless, official FBI data. |
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"fbi-wanted": {
"url": "https://gateway.pipeworx.io/fbi-wanted/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/fbi-wanted/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}
Both URLs reach the same gateway and the same 1476+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Fbi Wanted data" })
The gateway picks the right tool and fills the arguments automatically.
MIT
curl -X POST https://gateway.pipeworx.io/v1/tools/search_wanted \
-H 'Content-Type: application/json' \
-d '{"query":"bank robbery suspect"}'
No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/search_wanted. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.