Offendersearch MCP server
Which servers in the official MCP registry are Offendersearch's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-16
- Registry nameapp.offendersearch/offendersearchverified in the MCP registry
The registry name sits under offendersearch.app. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-16
- Tools5
- Server calls itselfoffendersearch
- Server version1.29.1
- Protocol version2025-06-18
On 2026-10-16 the server answered initialize and tools/list without a sign-in. First answer in 225 ms.
search_offendersSearch US sex-offender registries for one person and/or location. Fans out across all 58 registries (or the ones named in `jurisdictions`), de-duplicates people across registries, scores each match, and returns the normalized records…
batch_searchRun many person/location lookups in one call (row-in / row-out). Each row goes through the SAME engine as search_offenders, so a row's records are identical to what a single search would return. A row that fails is reported with…
get_registry_coverageList every registry we cover plus its scope, legal status, and health. Public coverage catalog (no API key required). Use it to discover the `jurisdictions` codes accepted by search_offenders / batch_search and to check per-registry…
search_criminalSearch US criminal records — county jail bookings, state prison custody, court cases and warrants. Covers county jail rosters, statewide prison systems, court sources, warrant systems and statewide registries across the states, DC and the…
get_criminal_coverageList the criminal-record jurisdictions searched, with kind and status. Use it to discover which states and counties are reachable and which are answering today, before relying on an empty result. Depth is uneven by design: counties…
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"offendersearch": {
"type": "http",
"url": "https://mcp.offendersearch.app/mcp"
}
}
}OpenAPI spec
47 paths, read 2026-10-16. Open the spec ↗
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.