Offendersearch MCP server
{
"mcpServers": {
"offendersearch": {
"type": "http",
"url": "https://mcp.offendersearch.app/mcp"
}
}
}{
"mcpServers": {
"offendersearch": {
"type": "http",
"url": "https://mcp.offendersearch.app/mcp"
}
}
}{
"mcpServers": {
"offendersearch": {
"type": "http",
"url": "https://mcp.offendersearch.app/mcp"
}
}
}{
"servers": {
"offendersearch": {
"type": "http",
"url": "https://mcp.offendersearch.app/mcp"
}
}
}{
"mcpServers": {
"offendersearch": {
"type": "http",
"url": "https://mcp.offendersearch.app/mcp"
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsonversion 1.29.1
What it does
Search across all 58 US sex-offender registries (50 states, DC, and territories) with a single API call. Results include confidence scores and citations to official registry sources. Intended for background screening, safety checks, and compliance workflows.
- Screen an individual by name and date of birth against all state registries to check for matches.
- Search a geographic area by zip code and radius to find registered offenders in a specific location.
- Batch-screen multiple people at once using the batch endpoint for roster-based compliance or intake processes.
Tools this server exposes
| Tool | Does |
|---|---|
| search | Query sex-offender registries by name, date of birth, age, or geographic location (zip code and radius). |
| batch | Screen multiple records in a single API call. |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.