CrashStory MCP server

• Registry namecom.crashstory/crashstoryverified in the MCP registry

The registry name sits under crashstory.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-24
• Tools18
• Server calls itselfcrashstory
• Server version1.0.0
• Protocol version2025-06-18

On 2026-10-24 the server answered initialize and tools/list without a sign-in. First answer in 85 ms.

• Whether its tools do the product's job has not been judged yet.
• Checked on 4 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 4 so far
• Answeredmeasuring4 of the 7 daily checks it takes to print a share
• Median first answer104 ms
• Space in an agent's context≈ 3,351 tokensthe definitions of all its tools (18), which an agent carries on every turn
• Tool definitionsB · 83 of 100
• Typed results0 of 18 toolsdeclared outputSchema: results come typed, read once

• Not saying whether it only reads or can destroy: 18 of 18

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• search_attorneys

  Search for personal injury attorneys in Colorado. Filter by city, county, specialty, rating, and verification status. Returns attorney profiles plus the canonical slug to use with profile, review, and comparison tools.

• get_attorney_profile

  Get a detailed attorney profile by slug. Returns full bio, practice areas, reviews, credentials, office location, and AI-analyzed intelligence data when available.

• find_nearby_attorneys

  Find personal injury attorneys near a geographic location. Uses Haversine distance calculation. Returns attorneys sorted by distance with contact info and ratings.

• list_attorney_cities

  List all Colorado cities that have active personal injury attorneys, with the count of attorneys in each city. Useful for discovering which cities have coverage.

• get_attorney_leaderboard

  Get the top-ranked personal injury attorneys in Colorado. Returns attorneys ranked by a composite score considering ratings, reviews, experience, and case outcomes.

• compare_attorneys

  Compare 2-4 attorney profiles side-by-side. Use canonical slugs from search_attorneys. Returns key comparison metrics including ratings, reviews, specialties, practice areas, and known experience fields.

• get_attorney_reviews

  Get paginated client reviews for a specific attorney. Includes review text, rating, reviewer name, date, and rating distribution breakdown.

• get_review_analytics

  Get review velocity analytics for a specific attorney. Includes review frequency trends, freshness score, momentum indicators, composite score, city percentile rank, and month-over-month time series.

• get_city_review_leaderboard

  Get the review-based leaderboard for attorneys in a specific Colorado city. Ranks attorneys by composite review metrics including velocity, freshness, momentum, and rating.

• get_review_intelligence

  Get AI-analyzed review intelligence for a law firm. Returns plain-language praise and complaint summaries, 12 consumer pain point dimensions, case type distribution, trust signals, response quality, and highlight reviews.

• compare_review_intelligence

  Compare AI-analyzed review intelligence across 2-5 law firms. Returns side-by-side pain point dimensions, sentiment, trust signals, response quality, and case type distributions for competitive analysis.

• search_attorney_reviews

  Search a law firm's detailed reviews for the most relevant matches to a specific need, case type, injury, sentiment, or pain point. Use this when someone asks for reviews about communication, wrongful death, motorcycle crashes, fees…

• search_crashes

  Search Colorado crash records by location, date range, crash type, and severity. Database contains 500,000+ CDOT crash records. Returns key fields including location, date, severity, injuries, fatalities, and contributing factors.

• get_crash_details

  Get full details of a specific Colorado crash by its CUID (Crash Unique Identifier). Returns complete crash record including all vehicles involved, injuries, contributing factors, road conditions, weather, and narrative.

• get_nearby_crashes

  Get crash records near a specific attorney's office location. This tool is attorney-centered, not a raw lat/lng search. Use a canonical attorney slug from search_attorneys, then this tool will search around that office address.

• list_research_datasets

  List CrashStory research datasets that can be queried through the MCP server, including gas-price analysis datasets and their available data views.

• get_research_dataset_summary

  Get the structured summary/report for a CrashStory research dataset. Use this before row-level querying to understand coverage, methodology, findings, and limitations.

• query_research_dataset

  Query rows from CrashStory research datasets. Supports the gas-price analysis datasets with optional state, year, and month filters so agents can perform their own follow-on analysis.