MCP server for 104.com.tw job search platform
Free
Tools
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.
ArgumentsA call is made on an account: it counts against an allowance and the publisher sees it, which is why this one asks who you are first.
—
p95 latency
—
call success
—
uptime 90d
0
calls last 7d
What it does
Colorado traffic-crash data search, crash detail lookup and attorney/review intelligence.
Quickstart
# 1 — install (mcprush login holds a key from your dashboard)
npx mcprush@latest add crashstory-mcp
# 2 — ask your agent something
> Colorado traffic-crash data search, crash detail lookup and attorney/review intelligence.
CrashStory is free: there is no plan to choose, no cap to set and nothing that can bill you.
Publishernot claimed
CRAll 1 server
crashstory-mcp-production.up.railway.app1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
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 — this server runs on the publisher’s own infrastructure behind our gateway, and what you install is the connection to it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. Claude Code registers it in one command.
claude mcp add --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.
Free to install, and it runs from its publisher’s own package: no account, no key, no card.
What it writes
One config entry pointing at the gateway. The server itself runs on the publisher’s own infrastructure, so nothing from this listing executes on your machine.
What you approve
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.
Takes no parameters.
Example callreturns →
Get a detailed attorney profile by slug. Returns full bio, practice areas, reviews, credentials, office location, and AI-analyzed intelligence data when available.
Takes no parameters.
Example callreturns →
Find personal injury attorneys near a geographic location. Uses Haversine distance calculation. Returns attorneys sorted by distance with contact info and ratings.
Takes no parameters.
Example callreturns →
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.
Takes no parameters.
Example callreturns →
Get the top-ranked personal injury attorneys in Colorado. Returns attorneys ranked by a composite score considering ratings, reviews, experience, and case outcomes.
Takes no parameters.
Example callreturns →
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.
Takes no parameters.
Example callreturns →
Get paginated client reviews for a specific attorney. Includes review text, rating, reviewer name, date, and rating distribution breakdown.
Takes no parameters.
Example callreturns →
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.
Takes no parameters.
Example callreturns →
Get the review-based leaderboard for attorneys in a specific Colorado city. Ranks attorneys by composite review metrics including velocity, freshness, momentum, and rating.
Takes no parameters.
Example callreturns →
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.
Takes no parameters.
Example callreturns →
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.
Takes no parameters.
Example callreturns →
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.
Takes no parameters.
Example callreturns →
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.
Takes no parameters.
Example callreturns →
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.
Takes no parameters.
Example callreturns →
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.
Takes no parameters.
Example callreturns →
List CrashStory research datasets that can be queried through the MCP server, including gas-price analysis datasets and their available data views.
Takes no parameters.
Example callreturns →
Get the structured summary/report for a CrashStory research dataset. Use this before row-level querying to understand coverage, methodology, findings, and limitations.
Takes no parameters.
Example callreturns →
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.
Takes no parameters.
Example callreturns →
Freeyour plan
$0 forever
- Every tool, no call limit
- No card, no account needed
- Source published under a licence you can read
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because nothing bills
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable. CrashStory costs nothing to install and nothing to call, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: $8.42
$16.58 left
—Grade not published
No rule-by-rule report on file for this release
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 a hosted endpoint: the publisher runs it and we connect to it. The scanner reads packages and source, and neither exists to read here, so there is no grade — not a withheld one, an unmeasured one. What can be checked instead is on Installation: what it asks to reach and what it writes.
Release history
Pinned to 1.0.0 — the install command below asks for that release. A pin is part of an install, so it is kept for this visit and written down when you install.
1.0.0
undated
installedNo release note was published with this version.
—
no reviews yet
Reviews are earned
Only accounts with at least 50 real tool calls against this server in the last 90 days can post. Ratings are weighted by how much the reviewer actually uses it, and publishers can reply once per review.
Reviews are earned
Writing one takes an account with at least 50 real tool calls against CrashStory in the last 90 days. That is the whole gate — there is no other way to post, which is why the counts beside each review are worth reading.
No reviews yet
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 an account with 50 real tool calls against it.