MCP server for DeepL translation API
CrashStory is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Colorado personal injury attorney directory, AI-analyzed review intelligence, and crash data
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http crashstory-mcp https://crashstory-mcp-production.up.railway.app/mcp
# 2 — ask your agent for something these tools do
# search_attorneys, get_attorney_profile, find_nearby_attorneys and 15 more
CrashStory costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http crashstory-mcp https://crashstory-mcp-production.up.railway.app/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
18 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | Search by name or firm name |
| city | string | no | City name (e.g. "Denver", "Colorado Springs") |
| county | string | no | Service county name |
| specialty | string | no | Specialty filter (e.g. "Car Accident", "Wrongful Death") |
| min_rating | number | no | Minimum average rating (1.0-5.0) |
| verified | boolean | no | Only return verified attorneys |
| sort_by | string | no | Sort order |
| limit | integer | no | Max results (1-50) |
| page | integer | no | Page number |
Get a detailed attorney profile by slug. Returns full bio, practice areas, reviews, credentials, office location, and AI-analyzed intelligence data when available.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Canonical attorney slug from search_attorneys or list_attorney_cities (e.g. "levine-law-llc-denver") |
Find personal injury attorneys near a geographic location. Uses Haversine distance calculation. Returns attorneys sorted by distance with contact info and ratings.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| latitude | number | yes | Latitude of the location |
| longitude | number | yes | Longitude of the location |
| radius_miles | number | no | Search radius in miles (1-100, default 10) |
| limit | integer | no | Max results (1-50, default 10) |
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.
No parameter schema on file.
Get the top-ranked personal injury attorneys in Colorado. Returns attorneys ranked by a composite score considering ratings, reviews, experience, and case outcomes.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | Number of attorneys to return (1-50, default 20) |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slugs | array | yes | Array of 2-4 attorney slugs to compare |
Get paginated client reviews for a specific attorney. Includes review text, rating, reviewer name, date, and rating distribution breakdown.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Attorney slug identifier |
| page | integer | no | Page number |
| limit | integer | no | Reviews per page (1-50, default 20) |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Canonical attorney slug from search_attorneys (e.g. "levine-law-llc-denver") |
Get the review-based leaderboard for attorneys in a specific Colorado city. Ranks attorneys by composite review metrics including velocity, freshness, momentum, and rating.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| city | string | yes | City name (e.g. "Denver", "Boulder", "Colorado Springs") |
| limit | integer | no | Number of attorneys to return (1-50, default 10) |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| firm_slug | string | yes | Canonical firm slug from search_attorneys (e.g. "levine-law-llc-denver") |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| firm_slugs | array | yes | Array of 2-5 firm slugs to compare |
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, settlement clarity, or similar client concerns.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| firm_slug | string | yes | Canonical firm slug from search_attorneys or get_review_intelligence |
| need | string | no | Natural-language client need or concern, e.g. "good communication" or "fast settlement" |
| case_type | string | no | Case type, e.g. "wrongful death", "motorcycle", "truck accident" |
| injury | string | no | Injury or harm keyword, e.g. "back injury", "death", "concussion" |
| dimension | string | no | Specific review-intelligence dimension, e.g. "Communication" or "FeeTransparency" |
| sentiment | string | no | Filter toward praise, complaints, or mixed reviews |
| limit | integer | no | Max ranked reviews to return |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| location | string | no | City, county, or street name (case-insensitive partial match) |
| date_from | string | no | Start date (ISO 8601, e.g. "2024-01-01") |
| date_to | string | no | End date (ISO 8601, e.g. "2024-12-31") |
| crash_type | string | no | Crash type: BROADSIDE, REAR_END, SIDESWIPE_SAME_DIRECTION, SIDESWIPE_OPPOSITE_DIRECTION, HEAD_ON, ROLLOVER, FIXED_OBJECT, ANIMAL, PEDESTRIAN, BICYCLE, MOTORCYCLE, OTHER |
| severity | string | no | Severity: FATAL, SERIOUS_INJURY, MINOR_INJURY, POSSIBLE_INJURY, PROPERTY_DAMAGE_ONLY |
| limit | integer | no | Max results (1-100, default 20) |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| cuid | string | yes | CDOT Crash Unique ID (e.g. "2024-001234") |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| attorney_slug | string | yes | Canonical attorney slug from search_attorneys, used as the center point |
| radius_km | number | no | Search radius in km (0.5-50, default 3) |
| months | integer | no | Look-back period in months (1-120, default 12) |
| limit | integer | no | Max results (1-200, default 50) |
| sort | string | no | Sort by distance or date |
List CrashStory research datasets that can be queried through the MCP server, including gas-price analysis datasets and their available data views.
No parameter schema on file.
Get the structured summary/report for a CrashStory research dataset. Use this before row-level querying to understand coverage, methodology, findings, and limitations.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Dataset slug. Options: gas-prices-vs-crashes, gas-prices-vs-fatalities-national. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Dataset slug. Options: gas-prices-vs-crashes, gas-prices-vs-fatalities-national. |
| dataset | string | yes | Data view. Colorado options: analysis_window, full_window. National options: state_year_panel, state_year_yoy, state_profiles, national_summary. |
| state | string | no | Optional two-letter state abbreviation filter, mainly for national datasets. |
| year_from | integer | no | Optional minimum year filter. |
| year_to | integer | no | Optional maximum year filter. |
| month_from | string | no | Optional minimum month filter in YYYY-MM format, mainly for the Colorado monthly dataset. |
| month_to | string | no | Optional maximum month filter in YYYY-MM format, mainly for the Colorado monthly dataset. |
| sort | string | no | Optional sort field. |
| order | string | no | Sort order (default desc). |
| limit | integer | no | Maximum rows to return. |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install CrashStory or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish CrashStory can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.