CT Injury Cases
REMOTE · CTINJURYCASES.COM
Connecticut personal injury litigation data: car accident cases, Hartford Judicial District.
Available components
Last scanned (3 hours ago)
Scores higher than 53% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Education and Research
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 → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 2334 tokens (~166/item across 14 items; 14 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 5 Nov 26 +1
- Server version: 1.20260909.20261030 → 2.0.0 functional
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 30 Oct 26 65
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 5 Nov 2026 · Probed https://ctinjurycases.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=ctinjurycases.com | CN=WE1,O=Google Trust Services,C=US | 29 Oct 2026 | 27 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 116d93523e2ba3310eac1be216159dec |
| SANs: ctinjurycases.com, *.ctinjurycases.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of ctinjurycases.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| ctinjurycases.com. | 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 | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://ctinjurycases.com/mcp | Verified | 200 | |
| http (plaintext) | http://ctinjurycases.com/mcp | Inconclusive | 405 |
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
describe_dataset Describe the dataset ~81
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.
| Name | Type | Req | Description |
|---|---|---|---|
| purpose | string | – | One sentence on what you are trying to find out. Logged to improve the dataset; never returned. |
| Name | Type | Req | Description |
|---|---|---|---|
| caveats | array | yes | What to keep in mind across the dataset. |
| coverage | object | yes | What the dataset covers and how current it is. |
| dimensions | array | yes | Every stats dimension. |
| examples | array | yes | One example call per tool: the tool name, then its arguments as JSON. |
| fields | object | yes | Field glossary. |
| metrics | array | yes | Every stats metric. |
| source | string | yes | Where the data comes from and where to find a case's official record. |
No examples provided.
get_attorney Attorney profile ~100
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.
| Name | Type | Req | Description |
|---|---|---|---|
| juris_number | string | yes | Attorney juris number from search_attorneys. |
| purpose | string | – | One sentence on what you are trying to find out. Logged to improve the dataset; never returned. |
Structured output declared, but exposes no named fields.
No examples provided.
get_case Case details ~90
One case: dates, disposition, trial, verdict and offer amounts, its motion rulings, and the judges, attorneys and law firms by side.
| Name | Type | Req | Description |
|---|---|---|---|
| docket_number | string | yes | Docket number, e.g. HHD-CV-21-6140000-S. |
| purpose | string | – | One sentence on what you are trying to find out. Logged to improve the dataset; never returned. |
| Name | Type | Req | Description |
|---|---|---|---|
| attorneys | array | yes | Attorneys who appeared, with their juris numbers for get_attorney. |
| case | object | yes | The case record. |
| dispositionJudge | – | yes | The judge who decided the disposition; null when no judge did. |
| firms | object | yes | Lead law firm on each side; null when none is known. |
| rulings | array | yes | Motion rulings in the case. |
No examples provided.
get_firm Law firm profile ~163
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_number filter cover only the cases where it is a side's lead firm, so one firm's case total can differ slightly from place to place.
| Name | Type | Req | Description |
|---|---|---|---|
| juris_number | string | yes | Firm juris number from search_firms. |
| purpose | string | – | One sentence on what you are trying to find out. Logged to improve the dataset; never returned. |
Structured output declared, but exposes no named fields.
No examples provided.
get_judge Judge profile ~81
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.
| Name | Type | Req | Description |
|---|---|---|---|
| judge_key | string | yes | Judge key from search_judges. |
| purpose | string | – | One sentence on what you are trying to find out. Logged to improve the dataset; never returned. |
Structured output declared, but exposes no named fields.
No examples provided.
get_provider Medical provider profile ~90
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).
| Name | Type | Req | Description |
|---|---|---|---|
| provider_id | string | yes | Provider id from search_providers. |
| purpose | string | – | One sentence on what you are trying to find out. Logged to improve the dataset; never returned. |
Structured output declared, but exposes no named fields.
No examples provided.
request_data Request data ~88
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.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | What data you need and what you would use it for. |
| purpose | string | – | One sentence on what you are trying to find out. Logged to improve the dataset; never returned. |
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | Acknowledgement to pass on to the user. |
| received | boolean | yes | The submission was recorded. |
No examples provided.
search_attorneys Search attorneys ~171
List attorneys by name, firm, side and district, most cases first. get_attorney gives one attorney in full.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | nextCursor from the previous page; omit for the first page. |
| district | string | – | Judicial district, e.g. HARTFORD JD. |
| firm_juris_number | string | – | Juris number of their firm. |
| limit | integer | – | Results per page, at most 50 (the default). |
| name | string | – | Part of the name, any case. |
| purpose | string | – | One sentence on what you are trying to find out. Logged to improve the dataset; never returned. |
| side | string | – | Only those with cases for this side, ranked by their cases on that side rather than by all their cases. |
| Name | Type | Req | Description |
|---|---|---|---|
| nextCursor | – | yes | Pass as cursor for the next page; null on the last. |
| results | array | yes | This page of matches. |
| total | integer | yes | Matches across all pages. |
No examples provided.
search_cases Search cases ~289
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.
| Name | Type | Req | Description |
|---|---|---|---|
| case_type | string | – | Case type code: V01, V04 or V09. |
| cursor | string | – | nextCursor from the previous page; omit for the first page. |
| disposition_category | string | – | How the case ended, e.g. withdrawal or plaintiff_verdict; pending for open cases. |
| district | string | – | Judicial district, e.g. HARTFORD JD. |
| filed_from | string | – | Filed on or after this date (YYYY-MM-DD). |
| filed_to | string | – | Filed on or before this date (YYYY-MM-DD). |
| firm_juris_number | string | – | Juris number from search_firms; matches either side's lead firm. |
| judge_key | string | – | Judge key from search_judges; matches the judge who decided the disposition. |
| limit | integer | – | Results per page, at most 50 (the default). |
| litigation_type | string | – | third_party, um_uim or subrogation. |
| purpose | string | – | One sentence on what you are trying to find out. Logged to improve the dataset; never returned. |
| trial_kind | string | – | jury, court or not_tried. |
| Name | Type | Req | Description |
|---|---|---|---|
| nextCursor | – | yes | Pass as cursor for the next page; null on the last. |
| results | array | yes | This page of matches. |
| total | integer | yes | Matches across all pages. |
No examples provided.
search_firms Search law firms ~177
List law firms by name, side, district and size, most cases first. get_firm gives one firm in full.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | nextCursor from the previous page; omit for the first page. |
| district | string | – | Judicial district, e.g. HARTFORD JD. |
| limit | integer | – | Results per page, at most 50 (the default). |
| min_cases | integer | – | At least this many cases; with side, cases on that side. |
| name | string | – | Part of the name, any case. |
| purpose | string | – | One sentence on what you are trying to find out. Logged to improve the dataset; never returned. |
| side | string | – | Only those with cases for this side, ranked by their cases on that side rather than by all their cases. |
| Name | Type | Req | Description |
|---|---|---|---|
| nextCursor | – | yes | Pass as cursor for the next page; null on the last. |
| results | array | yes | This page of matches. |
| total | integer | yes | Matches across all pages. |
No examples provided.
search_judges Search judges ~128
List judges by name and district, with case counts, most cases first. get_judge gives one judge in full.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | nextCursor from the previous page; omit for the first page. |
| district | string | – | Judicial district, e.g. HARTFORD JD. |
| limit | integer | – | Results per page, at most 50 (the default). |
| name | string | – | Part of the name, any case. |
| purpose | string | – | One sentence on what you are trying to find out. Logged to improve the dataset; never returned. |
| Name | Type | Req | Description |
|---|---|---|---|
| nextCursor | – | yes | Pass as cursor for the next page; null on the last. |
| results | array | yes | This page of matches. |
| total | integer | yes | Matches across all pages. |
No examples provided.
search_providers Search medical providers ~210
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | nextCursor from the previous page; omit for the first page. |
| limit | integer | – | Results per page, at most 50 (the default). |
| min_cases | integer | – | At least this many cases. |
| name | string | – | Part of the name, any case. |
| purpose | string | – | One sentence on what you are trying to find out. Logged to improve the dataset; never returned. |
| side | string | – | treating: named as the plaintiff's treating provider; defense_examiner: retained by the defense to examine the plaintiff. |
| specialty | string | – | Part of the specialty, e.g. orthop. |
| town | string | – | Town the provider practises in. |
| type | string | – | physician, therapy, imaging or facility. |
| Name | Type | Req | Description |
|---|---|---|---|
| nextCursor | – | yes | Pass as cursor for the next page; null on the last. |
| results | array | yes | This page of matches. |
| total | integer | yes | Matches across all pages. |
No examples provided.
send_message Send a message ~121
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.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | The user's email, if they agreed and want a reply. | |
| message | string | yes | The message. |
| name | string | – | The user's name, if they agreed. |
| purpose | string | – | One sentence on what you are trying to find out. Logged to improve the dataset; never returned. |
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | Acknowledgement to pass on to the user. |
| received | boolean | yes | The submission was recorded. |
No examples provided.
stats Case statistics ~449
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.
| Name | Type | Req | Description |
|---|---|---|---|
| amount_in_demand | string | – | Amount-in-demand band, e.g. 15000_or_more. |
| case_type | string | – | Case type code: V01, V04 or V09. |
| claims_lost_wages | boolean | – | Lost wages are claimed. |
| commercial_vehicle | boolean | – | A commercial vehicle was involved. |
| disposition_category | string | – | How the case ended, e.g. withdrawal or plaintiff_verdict; pending for open cases. |
| district | string | – | Judicial district, e.g. HARTFORD JD. |
| filed_from | string | – | Filed on or after this date (YYYY-MM-DD). |
| filed_to | string | – | Filed on or before this date (YYYY-MM-DD). |
| firm_juris_number | string | – | Juris number from search_firms; matches either side's lead firm. |
| group_by | array | – | Up to two dimensions to break the metric down by. |
| injury_kind | string | – | An alleged injury kind, e.g. fracture. |
| injury_region | string | – | An injured body region, e.g. neck. |
| judge_key | string | – | Judge key from search_judges; matches the judge who decided the disposition. |
| litigation_type | string | – | third_party, um_uim or subrogation. |
| mechanism | string | – | How the crash happened, e.g. rear_end. |
| metric | string | yes | What to compute; see describe_dataset for each metric. |
| plaintiff_role | string | – | driver, passenger, pedestrian… |
| purpose | string | – | One sentence on what you are trying to find out. Logged to improve the dataset; never returned. |
| road_type | string | – | Kind of road, e.g. interstate. |
| trial_kind | string | – | jury, court or not_tried. |
| um_uim | boolean | – | UM/UIM coverage is claimed. |
| Name | Type | Req | Description |
|---|---|---|---|
| closedFrom | – | yes | For metrics over closed cases, the first disposition date counted, inclusive; the figures are not all-time. Null for metrics over every case. |
| closedTo | – | yes | For metrics over closed cases, the last disposition date counted, inclusive: the as-of date. Null for metrics over every case. |
| groupBy | array | yes | The group_by dimensions, in order. |
| groups | array | yes | One entry per group, largest n first. |
| groupsSuppressed | integer | yes | Returned groups that are suppressed. |
| metric | string | yes | The metric computed. |
| multiValuedDimensions | array | yes | Dimensions where one case can sit in several groups, so group counts overlap. |
| names | object | yes | Names of the judges and firms in the groups. |
| totalGroups | integer | yes | Groups before the cap on how many are returned. |
| truncated | boolean | yes | True when more groups exist than were returned. |
| unit | string | yes | What the metric counts: cases, or motion rulings for motion_grant_rate. |
No examples provided.
How do I install the CT Injury Cases MCP server?
CT Injury Cases is a hosted endpoint at https://ctinjurycases.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · ctinjurycases.com
claude mcp add --transport http com-ctinjurycases-ct-injury-cases 'https://ctinjurycases.com/mcp'
What is the CT Injury Cases MCP server?
CT Injury Cases is an MCP server listed in the public MCP registry as com.ctinjurycases/ct-injury-cases. Connecticut personal injury litigation data: car accident cases, Hartford Judicial District. This page covers its hosted endpoint (https://ctinjurycases.com/mcp).
Is the CT Injury Cases MCP server safe to use?
CT Injury Cases scores 68 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the CT Injury Cases MCP server expose?
CT Injury Cases exposes 14 tools: describe_dataset, search_cases, get_case, stats, search_judges, and 9 more. Their descriptions and schemas cost roughly 2,238 tokens of context every time the server is loaded.
Does the CT Injury Cases MCP server require authentication?
No. We connected to CT Injury Cases without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the CT Injury Cases MCP server still maintained?
CT Injury Cases is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.