An MCP server for sex-offender search
Connect Claude and any Model Context Protocol client to nationwide sex-offender data. Agents get safe, scored, source-tagged search tools over the full dataset — no custom integration code.
Private beta. The server is built and the tools below are final, but the hosted endpoint is not yet open to self-serve signups. Create an account and ask us for MCP access, or use the REST API today.
Connect in one config block
Once you have beta access, point your MCP client at the server URL with your API key and the tools become available to the model immediately.
- Scored, de-duplicated results the model can reason over
- Three tools: search_offenders, batch_search, get_registry_coverage
- Per-source provenance the agent can cite
- Same metered pricing as the REST API
{
"mcpServers": {
"offendersearch": {
"url": "https://mcp.offendersearch.app",
"headers": { "X-API-Key": "os_live_••••" }
}
}
}MCP FAQ
What is the Offendersearch MCP server?
An MCP (Model Context Protocol) endpoint that exposes our nationwide sex-offender search as a tool any MCP-compatible AI client — including Claude — can call, with scored, source-tagged results. It is built and in private beta; the hosted endpoint is not open to self-serve signups yet, so contact us for access.
Which tools does it expose?
Three: search_offenders (a name, DOB, location or radius search over all 58 US registries), batch_search (up to 1,000 queries in one call, one row in and one row out), and get_registry_coverage (the public catalog of every US registry we cover, with its scope, legal status and health — no API key required). The first two return the same normalized, provenance-tagged records as the REST API.
How is it billed?
MCP tool calls are metered the same as REST API calls — $0.15 per call ($0.11 after 2,000/mo). A Regular search is the base rate; live re-verification adds $0.02 per completed source, capped at $2.00 a search. batch_search bills one metered search per row, not one per call. get_registry_coverage is free.