CrashStory MCP
REMOTE · CRASHSTORY-MCP-PRODUCTION.UP.RAILWAY.APP · 2 COMPONENTS · SCANNED AUG 3
Colorado personal injury attorney directory, AI-analyzed review intelligence, and crash data
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 18 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1900 tokens (~105/item across 18 items; 18 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · crashstory-mcp-production.up.railway.app
claude mcp add --transport http com-crashstory-crashstory https://crashstory-mcp-production.up.railway.app/sse
[mcp_servers.com-crashstory-crashstory] url = "https://crashstory-mcp-production.up.railway.app/sse"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-crashstory-crashstory": {
"type": "remote",
"url": "https://crashstory-mcp-production.up.railway.app/sse",
"enabled": true
}
}
} openclaw mcp add com-crashstory-crashstory --url https://crashstory-mcp-production.up.railway.app/sse --transport streamable-http
mcp_servers:
com-crashstory-crashstory:
url: "https://crashstory-mcp-production.up.railway.app/sse" {
"mcpServers": {
"com-crashstory-crashstory": {
"type": "http",
"url": "https://crashstory-mcp-production.up.railway.app/sse"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 −1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 60
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Probed https://crashstory-mcp-production.up.railway.app/sse
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.up.railway.app | CN=YE1,O=Let's Encrypt,C=US | 29 Jul 2026 | 27 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 6da79bb561da3efeb0e751ca21abd3999fe |
| SANs: *.up.railway.app, up.railway.app | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
DNSSEC insecure
Validation of crashstory-mcp-production.up.railway.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| railway.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 404 |
| Header | Value |
|---|---|
| content-security-policy | default-src 'none' |
| x-content-type-options | nosniff |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| sse | https://crashstory-mcp-production.up.railway.app/sse | Verified | 200 | |
| http (plaintext) | http://crashstory-mcp-production.up.railway.app/sse | HTTPS enforced | 301 | https://crashstory-mcp-production.up.railway.app/sse |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
compare_attorneys ~67
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.
| Name | Type | Req | Description |
|---|---|---|---|
| slugs | array | yes | Array of 2-4 attorney slugs to compare |
No output schema declared.
No examples provided.
compare_review_intelligence ~68
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.
| Name | Type | Req | Description |
|---|---|---|---|
| firm_slugs | array | yes | Array of 2-5 firm slugs to compare |
No output schema declared.
No examples provided.
find_nearby_attorneys ~99
Find personal injury attorneys near a geographic location. Uses Haversine distance calculation. Returns attorneys sorted by distance with contact info and ratings.
| Name | Type | Req | Description |
|---|---|---|---|
| latitude | number | yes | Latitude of the location |
| limit | integer | — | Max results (1-50, default 10) |
| longitude | number | yes | Longitude of the location |
| radius_miles | number | — | Search radius in miles (1-100, default 10) |
No output schema declared.
No examples provided.
get_attorney_leaderboard ~60
Get the top-ranked personal injury attorneys in Colorado. Returns attorneys ranked by a composite score considering ratings, reviews, experience, and case outcomes.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | — | Number of attorneys to return (1-50, default 20) |
No output schema declared.
No examples provided.
get_attorney_profile ~75
Get a detailed attorney profile by slug. Returns full bio, practice areas, reviews, credentials, office location, and AI-analyzed intelligence data when available.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Canonical attorney slug from search_attorneys or list_attorney_cities (e.g. "levine-law-llc-denver") |
No output schema declared.
No examples provided.
get_attorney_reviews ~73
Get paginated client reviews for a specific attorney. Includes review text, rating, reviewer name, date, and rating distribution breakdown.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | — | Reviews per page (1-50, default 20) |
| page | integer | — | Page number |
| slug | string | yes | Attorney slug identifier |
No output schema declared.
No examples provided.
get_city_review_leaderboard ~85
Get the review-based leaderboard for attorneys in a specific Colorado city. Ranks attorneys by composite review metrics including velocity, freshness, momentum, and rating.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | yes | City name (e.g. "Denver", "Boulder", "Colorado Springs") |
| limit | integer | — | Number of attorneys to return (1-50, default 10) |
No output schema declared.
No examples provided.
get_crash_details ~71
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cuid | string | yes | CDOT Crash Unique ID (e.g. "2024-001234") |
No output schema declared.
No examples provided.
get_nearby_crashes ~151
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.
| Name | Type | Req | Description |
|---|---|---|---|
| attorney_slug | string | yes | Canonical attorney slug from search_attorneys, used as the center point |
| limit | integer | — | Max results (1-200, default 50) |
| months | integer | — | Look-back period in months (1-120, default 12) |
| radius_km | number | — | Search radius in km (0.5-50, default 3) |
| sort | string | — | Sort by distance or date |
No output schema declared.
No examples provided.
get_research_dataset_summary ~69
Get the structured summary/report for a CrashStory research dataset. Use this before row-level querying to understand coverage, methodology, findings, and limitations.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Dataset slug. Options: gas-prices-vs-crashes, gas-prices-vs-fatalities-national. |
No output schema declared.
No examples provided.
get_review_analytics ~72
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.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Canonical attorney slug from search_attorneys (e.g. "levine-law-llc-denver") |
No output schema declared.
No examples provided.
get_review_intelligence ~79
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.
| Name | Type | Req | Description |
|---|---|---|---|
| firm_slug | string | yes | Canonical firm slug from search_attorneys (e.g. "levine-law-llc-denver") |
No output schema declared.
No examples provided.
list_attorney_cities ~39
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_research_datasets ~36
List CrashStory research datasets that can be queried through the MCP server, including gas-price analysis datasets and their available data views.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
query_research_dataset ~229
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.
| Name | Type | Req | Description |
|---|---|---|---|
| dataset | string | yes | Data view. Colorado options: analysis_window, full_window. National options: state_year_panel, state_year_yoy, state_profiles, national_summary. |
| limit | integer | — | Maximum rows to return. |
| month_from | string | — | Optional minimum month filter in YYYY-MM format, mainly for the Colorado monthly dataset. |
| month_to | string | — | Optional maximum month filter in YYYY-MM format, mainly for the Colorado monthly dataset. |
| order | string | — | Sort order (default desc). |
| slug | string | yes | Dataset slug. Options: gas-prices-vs-crashes, gas-prices-vs-fatalities-national. |
| sort | string | — | Optional sort field. |
| state | string | — | Optional two-letter state abbreviation filter, mainly for national datasets. |
| year_from | integer | — | Optional minimum year filter. |
| year_to | integer | — | Optional maximum year filter. |
No output schema declared.
No examples provided.
search_attorney_reviews ~211
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.
| Name | Type | Req | Description |
|---|---|---|---|
| case_type | string | — | Case type, e.g. "wrongful death", "motorcycle", "truck accident" |
| dimension | string | — | Specific review-intelligence dimension, e.g. "Communication" or "FeeTransparency" |
| firm_slug | string | yes | Canonical firm slug from search_attorneys or get_review_intelligence |
| injury | string | — | Injury or harm keyword, e.g. "back injury", "death", "concussion" |
| limit | integer | — | Max ranked reviews to return |
| need | string | — | Natural-language client need or concern, e.g. "good communication" or "fast settlement" |
| sentiment | string | — | Filter toward praise, complaints, or mixed reviews |
No output schema declared.
No examples provided.
search_attorneys ~174
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.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | — | City name (e.g. "Denver", "Colorado Springs") |
| county | string | — | Service county name |
| limit | integer | — | Max results (1-50) |
| min_rating | number | — | Minimum average rating (1.0-5.0) |
| page | integer | — | Page number |
| query | string | — | Search by name or firm name |
| sort_by | string | — | Sort order |
| specialty | string | — | Specialty filter (e.g. "Car Accident", "Wrongful Death") |
| verified | boolean | — | Only return verified attorneys |
No output schema declared.
No examples provided.
search_crashes ~242
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.
| Name | Type | Req | Description |
|---|---|---|---|
| crash_type | string | — | Crash type: BROADSIDE, REAR_END, SIDESWIPE_SAME_DIRECTION, SIDESWIPE_OPPOSITE_DIRECTION, HEAD_ON, ROLLOVER, FIXED_OBJECT, ANIMAL, PEDESTRIAN, BICYCLE, MOTORCYCLE, OTHER |
| date_from | string | — | Start date (ISO 8601, e.g. "2024-01-01") |
| date_to | string | — | End date (ISO 8601, e.g. "2024-12-31") |
| limit | integer | — | Max results (1-100, default 20) |
| location | string | — | City, county, or street name (case-insensitive partial match) |
| severity | string | — | Severity: FATAL, SERIOUS_INJURY, MINOR_INJURY, POSSIBLE_INJURY, PROPERTY_DAMAGE_ONLY |
No output schema declared.
No examples provided.