Comparing locations can mean switching between a map, an API response, and a conversation with your team. CrimeScore MCP lets a compatible AI assistant fetch the location context it needs through four focused tools. You choose the question; CrimeScore supplies the data behind the answer.
Start with a small request: resolve a US address, then retrieve its score. If the address has multiple matches, ask the assistant to confirm the location before scoring it. A successful geocode-plus-score sequence uses one CrimeScore request. Asking for the contributor details uses another. A conversation can contain several separately charged calls.
The available tools resolve addresses, retrieve location scores, explain score contributors, and query nearby recent incident activity. They return customer-facing API data, including model and geography metadata. The assistant does not get arbitrary database access, billing controls, or the scoring implementation.
The hosted connection sends requests to CrimeScore over HTTPS with your secret API key. The local option uses a small npm package launched by a desktop or CLI client. Local describes where the MCP process runs, not where the dataset lives: it still calls the CrimeScore API online.
Choose the CrimeScore organization before creating a dedicated key. That key determines whose allowance is used, even if you later switch organizations in the dashboard. A shared AI-workspace connector may also share its credential, so the people using it should be authorized to spend that organization's quota.
The distinctions in the response matter. Coordinate scores describe Census block groups, not individual buildings. ZIP results are ZCTA estimates. Contributors describe model associations rather than causes. Nearby activity is incomplete, and an empty result does not mean no crime occurred. Modeled Safety Scores are not official crime rates or guarantees.
Start with one covered location, check the returned geography, and compare your usage before and after. Keep tool approvals enabled for the first calls and ask the assistant not to retry failures automatically. A timeout can happen after a charge, so inspect usage before making another request.
The setup guide contains the maintained client instructions, secure credential templates, tool costs, and troubleshooting. No OAuth connection is included in this release. Share locations and results with your AI provider only when your organization's data policy allows it.