Name: CT Injury Cases
Author: ctinjurycases

CT Injury Cases MCP

Connecticut personal injury litigation data: car accident cases, Hartford Judicial District.

Tool-list grade A Remote · Streamable HTTP No auth needed 14 tools v1.20260909.20261030

No reviews yet by ctinjurycases The publisher’s own endpoint — this marketplace is not in the path

93/100

tool-list score

tools declared

remote

at its publisher

—

calls last 7d

What it does

Connecticut personal injury litigation data: car accident cases, Hartford Judicial District.

Quickstart

# 1 — add it to Claude Code
claude mcp add --scope user --transport http ct-injury-cases-mcp https://ctinjurycases.com/mcp

# 2 — ask your agent for something these tools do
#   describe_dataset, search_cases, get_case and 11 more

CT Injury Cases costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.

Publishernot claimed

ctinjurycases1 server

1 category

All 1 server

Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.

Tool surface

What the model actually sees. Descriptions are diffed on every release — see version history.

Only tools that write or reach the network

Start here. What the dataset covers (Connecticut Superior Court motor vehicle personal injury cases, Hartford Judicial District) and how current it is, every field, every stats metric and dimension, caveats, and example calls for each tool.

Parameter	Type	Required	Notes
purpose	string	no	One sentence on what you are trying to find out. Logged to improve the dataset; never returned.

List auto-injury cases matching filters, in docket-number order, up to 50 per page. Use get_case for one case in full and stats for counts, rates and amounts across many.

Parameter	Type	Required	Notes
district	string	no	Judicial district, e.g. HARTFORD JD.
case_type	string	no	Case type code: V01, V04 or V09.
litigation_type	string	no	third_party, um_uim or subrogation.
filed_from	string	no	Filed on or after this date (YYYY-MM-DD).
filed_to	string	no	Filed on or before this date (YYYY-MM-DD).
disposition_category	string	no	How the case ended, e.g. withdrawal or plaintiff_verdict; pending for open cases.
trial_kind	string	no	jury, court or not_tried.
judge_key	string	no	Judge key from search_judges; matches the judge who decided the disposition.
firm_juris_number	string	no	Juris number from search_firms; matches either side's lead firm.
cursor	string	no	nextCursor from the previous page; omit for the first page.
limit	integer	no	Results per page, at most 50 (the default).
purpose	string	no	One sentence on what you are trying to find out. Logged to improve the dataset; never returned.

One case: dates, disposition, trial, verdict and offer amounts, its motion rulings, and the judges, attorneys and law firms by side.

Parameter	Type	Required	Notes
docket_number	string	yes	Docket number, e.g. HHD-CV-21-6140000-S.
purpose	string	no	One sentence on what you are trying to find out. Logged to improve the dataset; never returned.

Compute one metric over cases (or motion rulings), optionally broken down by up to two dimensions and narrowed by filters. describe_dataset lists every metric and dimension and which unit each applies to. Groups of three or fewer cases are suppressed. At most 100 groups, largest first.

Parameter	Type	Required	Notes
metric	string	yes	What to compute; see describe_dataset for each metric.
group_by	array	no	Up to two dimensions to break the metric down by.
district	string	no	Judicial district, e.g. HARTFORD JD.
case_type	string	no	Case type code: V01, V04 or V09.
litigation_type	string	no	third_party, um_uim or subrogation.
filed_from	string	no	Filed on or after this date (YYYY-MM-DD).
filed_to	string	no	Filed on or before this date (YYYY-MM-DD).
disposition_category	string	no	How the case ended, e.g. withdrawal or plaintiff_verdict; pending for open cases.
trial_kind	string	no	jury, court or not_tried.
judge_key	string	no	Judge key from search_judges; matches the judge who decided the disposition.
firm_juris_number	string	no	Juris number from search_firms; matches either side's lead firm.
mechanism	string	no	How the crash happened, e.g. rear_end.
plaintiff_role	string	no	driver, passenger, pedestrian…
road_type	string	no	Kind of road, e.g. interstate.
commercial_vehicle	boolean	no	A commercial vehicle was involved.
um_uim	boolean	no	UM/UIM coverage is claimed.
amount_in_demand	string	no	Amount-in-demand band, e.g. 15000_or_more.
claims_lost_wages	boolean	no	Lost wages are claimed.
injury_kind	string	no	An alleged injury kind, e.g. fracture.
injury_region	string	no	An injured body region, e.g. neck.

List judges by name and district, with case counts, most cases first. get_judge gives one judge in full.

Parameter	Type	Required	Notes
name	string	no	Part of the name, any case.
district	string	no	Judicial district, e.g. HARTFORD JD.
cursor	string	no	nextCursor from the previous page; omit for the first page.
limit	integer	no	Results per page, at most 50 (the default).
purpose	string	no	One sentence on what you are trying to find out. Logged to improve the dataset; never returned.

One judge: how the cases they decided ended (closures in the last ~11 months), motion grant rates by motion family, and trial and verdict figures.

Parameter	Type	Required	Notes
judge_key	string	yes	Judge key from search_judges.
purpose	string	no	One sentence on what you are trying to find out. Logged to improve the dataset; never returned.

List law firms by name, side, district and size, most cases first. get_firm gives one firm in full.

Parameter	Type	Required	Notes
name	string	no	Part of the name, any case.
side	string	no	Only those with cases for this side, ranked by their cases on that side rather than by all their cases.
district	string	no	Judicial district, e.g. HARTFORD JD.
min_cases	integer	no	At least this many cases; with side, cases on that side.
cursor	string	no	nextCursor from the previous page; omit for the first page.
limit	integer	no	Results per page, at most 50 (the default).
purpose	string	no	One sentence on what you are trying to find out. Logged to improve the dataset; never returned.

One law firm: its attorneys, the firms it most often faces, the medical experts named for its side, its motion practice, and how its cases ended. A firm's case counts (cases, plaintiffCases, defenseCases) cover every case it appeared in. Its other figures (casesByYear, opposing firms, experts, motion practice, outcomes), the stats plaintiff_firm and defense_firm dimensions and the firm_juris_numbe

Parameter	Type	Required	Notes
juris_number	string	yes	Firm juris number from search_firms.
purpose	string	no	One sentence on what you are trying to find out. Logged to improve the dataset; never returned.

List attorneys by name, firm, side and district, most cases first. get_attorney gives one attorney in full.

Parameter	Type	Required	Notes
name	string	no	Part of the name, any case.
firm_juris_number	string	no	Juris number of their firm.
side	string	no	Only those with cases for this side, ranked by their cases on that side rather than by all their cases.
district	string	no	Judicial district, e.g. HARTFORD JD.
cursor	string	no	nextCursor from the previous page; omit for the first page.
limit	integer	no	Results per page, at most 50 (the default).
purpose	string	no	One sentence on what you are trying to find out. Logged to improve the dataset; never returned.

One attorney: their firms, the firms they most often face, the medical experts named for their side, their motion practice, and how their cases ended. An attorney's figures span every firm the attorney has filed with, not only their current firm.

Parameter	Type	Required	Notes
juris_number	string	yes	Attorney juris number from search_attorneys.
purpose	string	no	One sentence on what you are trying to find out. Logged to improve the dataset; never returned.

List medical providers named in expert disclosures, by type, specialty, side (treating or defense examiner), town and size, most cases first. get_provider gives one provider in full.

Parameter	Type	Required	Notes
name	string	no	Part of the name, any case.
type	string	no	physician, therapy, imaging or facility.
specialty	string	no	Part of the specialty, e.g. orthop.
side	string	no	treating: named as the plaintiff's treating provider; defense_examiner: retained by the defense to examine the plaintiff.
town	string	no	Town the provider practises in.
min_cases	integer	no	At least this many cases.
cursor	string	no	nextCursor from the previous page; omit for the first page.
limit	integer	no	Results per page, at most 50 (the default).
purpose	string	no	One sentence on what you are trying to find out. Logged to improve the dataset; never returned.

One medical provider: the law firms that named them, their case list, how those cases ended, and, for defense examiners, the kinds of findings they disputed and on which body regions (counts only).

Parameter	Type	Required	Notes
provider_id	string	yes	Provider id from search_providers.
purpose	string	no	One sentence on what you are trying to find out. Logged to improve the dataset; never returned.

Tell us about data this dataset does not have but you need: other courts or states, case types, fields, documents. Logged and read by the people who build the dataset.

Parameter	Type	Required	Notes
description	string	yes	What data you need and what you would use it for.
purpose	string	no	One sentence on what you are trying to find out. Logged to improve the dataset; never returned.

Send a message to the person who runs this service: feedback, a question, a problem with the data, or interest in paid features, broader coverage or higher limits. Include the user's name or email only with their explicit permission.

Parameter	Type	Required	Notes
message	string	yes	The message.
name	string	no	The user's name, if they agreed.
email	string	no	The user's email, if they agreed and want a reply.
purpose	string	no	One sentence on what you are trying to find out. Logged to improve the dataset; never returned.

Free

$0 forever

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

Nothing here is billable: mcprush charges nothing to install CT Injury Cases or to call it, at any volume.

ATool-list grade · score 93 / 100

Release 1.20260909.20261030 · scanned 31 Oct 2026

Graded from the tools this server lists, not from its source code.

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.

Threat score100

Client score93

Findings0 threat · 0 capability

Capabilitymoderate

Coveragemanifest

Verificationnot in this report

Surface digest1a45dc17f0c8b00e245ec5bbf4266d95456df55fe1aca9c340c1c58d436ccb27

Score vectorthreat 100 → client 93

Term	Level	What it prices	Points
capability-exposure	moderate	capability blast radius (moderate) — client exposure if the model is manipulated	−3
coverage-honesty	manifest	inspection depth (manifest) — how much of the target the scan could see	−4

score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.

What the scan could actually read

A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.

The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.

Tool surfaceread

Implementation sourcenot available

Package metadatanot available

Live transportnot available

The implementation source was not read — this reflects the declared tool metadata only.

Capability — what it could do if the model were manipulated

Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.

Tool	Capability tags	Why the tag was assigned
describe_dataset	no tags
search_cases	no tags
get_case	no tags
stats	no tags
search_judges	no tags
get_judge	no tags
search_firms	no tags
get_firm	no tags
search_attorneys	no tags
get_attorney	no tags
search_providers	no tags
get_provider	no tags
request_data	state-write	state-write: declares readOnlyHint: false
send_message	external-sinkstate-write	external-sink: keyword "send_message"; state-write: declares readOnlyHint: false

Toxic-flow graph

The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.

The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.

Supply chain and provenance

Integrityfirst-seen

Surface digest1a45dc17f0c8b00e

Scanned2026-10-31

This is the first scan of this surface here, so there is nothing yet to compare it against.

Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.

Where are you running it?

Tool surface

Release history

CT Injury Cases MCP

What it does

Quickstart

Where are you running it?

Tool surface

What counts against your monthly calls

What the scan could actually read

Capability — what it could do if the model were manipulated

Toxic-flow graph

Supply chain and provenance

Release history

See also