Home / MCP registry index / com.crashstory/crashstory
CrashStory MCP
com.crashstory/crashstory in the official MCP registry.
Endpoint https://crashstory-mcp-production.up.railway.app/mcp.
The registry describes it as: Colorado personal injury attorney directory, AI-analyzed review intelligence, and crash data
We read its 18 tools on 2026-10-27. Nothing in them matched our tool-poisoning rules.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
search_attorneys get_attorney_profile find_nearby_attorneys list_attorney_cities get_attorney_leaderboard compare_attorneys get_attorney_reviews get_review_analytics get_city_review_leaderboard get_review_intelligence compare_review_intelligence search_attorney_reviews search_crashes get_crash_details get_nearby_crashes list_research_datasets get_research_dataset_summary query_research_dataset
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-crashstory-crashstory)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.