Official hosted MCP server for the DoorProfit API — US crime, safety, and neighborhood data for any address, inside Claude, ChatGPT, Cursor, and any MCP-capable client.
https://api.doorprofit.com/mcpAsk your AI assistant "Is 500 Adams St in Tulsa safe?" and it answers with real data: a letter-grade safety score, recent incidents within 1,000 ft, neighborhood demographics, income, rent, home values, and more.
Tool | Description | Quota |
| Safety score (A+ to F), crime breakdown vs national average, recent incidents within 1,000 ft | 1 call |
| Demographics, income, home values, rent, cost of living, weather & disaster risk | 1 call |
| Registered offenders near a location (≤3 mi) or by name | 1 call |
| Your plan, usage, and remaining quota | Free |
Related MCP server: PropertyScoop MCP Server
Add https://api.doorprofit.com/mcp as a remote MCP server / custom
connector in your client. You'll be prompted to sign in to your DoorProfit
account and approve access. No keys to copy.
Get a free key at api.doorprofit.com/signup, then configure:
{
"mcpServers": {
"doorprofit": {
"url": "https://api.doorprofit.com/mcp",
"headers": {
"Authorization": "Bearer dp_your_api_key"
}
}
}
}Clients that only accept a URL can use
https://api.doorprofit.com/mcp?key=dp_your_api_key instead.
For clients that only speak stdio, this repository contains a small bridge that exposes the hosted server as a local process. It requires Node 18+.
{
"mcpServers": {
"doorprofit": {
"command": "npx",
"args": ["-y", "github:shawndoor/doorprofit-mcp"],
"env": {
"DOORPROFIT_API_KEY": "dp_your_api_key"
}
}
}
}Or with Docker:
docker build -t doorprofit-mcp .
docker run -i --rm -e DOORPROFIT_API_KEY=dp_your_api_key doorprofit-mcpThe bridge forwards every tool call to https://api.doorprofit.com/mcp and
pulls its tool definitions from the same place, falling back to the snapshot
in src/tools.json when the API is unreachable. Set DOORPROFIT_MCP_URL to
point it somewhere else. Run npm run sync-tools to refresh the snapshot
after the hosted tool definitions change.
The test address 500 Main St, Dallas, TX 75202 returns real data and
never consumes quota — perfect for kicking the tires.
Transport: Streamable HTTP (stateless)
Auth: OAuth 2.1 (authorization code + PKCE, dynamic client registration) or API key
Coverage: United States addresses (street address or lat/lng)
Quotas: tool calls are metered against your DoorProfit plan; free tier available, paid plans raise limits
Support: support@doorprofit.com
This repository contains the documentation and the open-source stdio bridge
for the hosted server. The data pipeline behind api.doorprofit.com is not
open source.
Report the plan, monthly and daily call usage, remaining quota, reset times, rate limit and overage status for the DoorProfit API key authenticating this session. Takes no arguments — it always describes the calling key, never another account. Call it when the user asks how many calls they have left, or after any other tool returns QUOTA_EXCEEDED or DAILY_LIMIT_EXCEEDED, to confirm the limit and reset time before suggesting an upgrade. This is the only tool that never consumes quota.
Inputs: no named parameters. Returns: data, success
Crime safety grade and incident history for one US address or coordinate pair: a letter score (A+ safest through F), a per-crime-type breakdown against the national average, and the individual incidents recorded within 1000ft over a rolling 90-day window. Use this for "is this address/neighborhood safe?" questions. Do NOT use it for demographics, income, rent or schools (use get_neighborhood_data) or for registered offenders (use search_offenders) — neither is included here. Pass either address or lat+lng, not both. US locations only; requires a DoorProfit API key and consumes 1 call from that key's quota, except for the free test address "500 Main St, Dallas, TX 75202".
Inputs: lat, lng, address. Returns: success, location, incidents, test_mode, +4 more
Profile of the neighborhood (or census block group) containing one US address or coordinate pair: demographics, median household income, home values, rent by bedroom count, education attainment, cost-of-living indices, climate and natural-disaster risk. Use this when the question is about who lives in an area or what it costs to live there. Do NOT use it for crime or safety scores (use get_crime_data) — no crime data is returned here. Pass either address or lat+lng, not both. The neighborhood field is null where no data exists for the location. US locations only; requires a DoorProfit API key and consumes 1 call from that key's quota, except for the free test address "500 Main St, Dallas, TX 75202".
Inputs: lat, lng, address. Returns: success, location, test_mode, neighborhood
Search US registered offenders in one of two modes. Location mode: pass address or lat+lng, plus an optional radius in miles (default 1, capped at 3); results include each offender's distance from the search point. Name mode: pass at least one of first_name, last_name or dob, optionally narrowed by city/state/zipcode — those three filters alone are not accepted. Location parameters take precedence when both are supplied. Use this only for registered-offender questions; for an overall safety grade use get_crime_data instead. Results are paginated (page, limit, max 100 per page) and each page requested requires a DoorProfit API key and consumes 1 call from that key's quota.
Inputs: dob, lat, lng, city, +8 more. Returns: page, radius, success, offenders, +5 more
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 4 tools
Each tool targets a clearly distinct data domain: crime/safety, neighborhood demographics, registered offenders, and API usage. The descriptions explicitly cross-reference one another (e.g., 'use search_offenders, not get_crime_data') to prevent misselection. There is no overlap between any two tools.
Tools follow a consistent get_/search_ verb-noun pattern (get_crime_data, get_neighborhood_data, get_api_usage, search_offenders). get_ vs search_ is a minor semantic deviation where search_offenders conveys a different query mode, but the pattern is otherwise highly regular.
Four tools is a well-scoped surface for a neighborhood-data server. Each tool covers a distinct domain (crime, demographics, offenders, quota) and earns its place without bloat or redundancy.
The surface covers the three core residential-data questions (safety, demographics, offenders) plus operational quota management. Minor gaps exist — no school or transit data — but the stated domains are fully addressed and the free-test-address and pagination details suggest mature handling of edge cases.
US crime scores, incidents, neighborhood demographics, rent data, and offender search by address.
US neighborhood Safety Scores, score drivers, geocoding and nearby activity from CrimeScore.io.
Access street-level crime reports, stop and search data, and outcomes across UK police forces
US rental market data by zip: rent, cap rates, vacancy, hazard risk, rent trends. Free, no auth.
