# Court Rules (remote · mcp.courtrules.app)

Judge-level filing rules, court holidays and enforcement data for US federal and state courts.

- Trust score: 38/100 (low)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-03

## Components

- remote · `mcp.courtrules.app`: 38/100 (this document), [markdown](https://verifymcp.io/servers/app-courtrules-court-rules/mcp.md), [page](https://verifymcp.io/servers/app-courtrules-court-rules/mcp)

## Channel facts

- Endpoint: `https://mcp.courtrules.app/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-03.

- **Endpoint Security**: 94/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 0/100
  - Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http.
- **Schema Quality & AI Usability**: 0/100
  - Schema blocked by authentication: the endpoint requires auth we don't have to read it.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.
- **Tool Safety**: 0/100
  - Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
- **Capabilities**: 0/100
  - Capabilities blocked by authentication: the endpoint requires auth we don't have to read them.

**Unverified: 6 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the Court Rules MCP server?

Court Rules is a hosted endpoint at https://mcp.courtrules.app/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.

### Claude

```bash
claude mcp add --transport http app-courtrules-court-rules 'https://mcp.courtrules.app/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "app-courtrules-court-rules": {
      "url": "https://mcp.courtrules.app/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "app-courtrules-court-rules": {
      "type": "http",
      "url": "https://mcp.courtrules.app/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.app-courtrules-court-rules]
url = "https://mcp.courtrules.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "app-courtrules-court-rules": {
      "type": "remote",
      "url": "https://mcp.courtrules.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add app-courtrules-court-rules --url 'https://mcp.courtrules.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  app-courtrules-court-rules:
    url: "https://mcp.courtrules.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "app-courtrules-court-rules": {
      "Transport": "http",
      "Url": "https://mcp.courtrules.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add app-courtrules-court-rules -t streamable-http -u 'https://mcp.courtrules.app/mcp'
```

### Other

```json
{
  "mcpServers": {
    "app-courtrules-court-rules": {
      "type": "http",
      "url": "https://mcp.courtrules.app/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-28 (score 38, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-25 (score 38, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 38, −39)

- [security regression] Endpoint reachability: reachable → behind authorisation
- [security regression] Stability: 0.77 → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] Transport: pass → unverified
- [security improvement] Authorization: unverified → pass
- [security] First check of Authorization: partial
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-09-23 (score 77, 0)

- [cosmetic] “search_judges” added an optional parameter “include_inactive”

### 2026-09-22 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-21 (score 76, 0)

- [security] Tool “search_filing_rules” rewrote its description, which is the text the model reads

### 2026-09-20 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-18 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (9)

### `list_courts` (~43 tokens)

List courts

List all courts with their status and judge counts

Input parameters:

- `status` (string): Filter by court status: "live", "preview", or "coming_soon"

### `list_court_holidays` (~127 tokens)

List court holidays

List court holidays and closure dates. Filter by district, calendar year, or date range. Returns official source URLs and the last time Court Rules checked the source.

Input parameters:

- `date_from` (string): Start date filter (YYYY-MM-DD)
- `date_to` (string): End date filter (YYYY-MM-DD)
- `district_id` (string): Court identifier (e.g., "edny")
- `limit` (number): Maximum results to return (default: 50, max: 200)
- `year` (number): Calendar year (e.g., 2026)

### `search_filing_rules` (~345 tokens)

Search filing rules

Search extracted court filing rules from active source documents. Use this for state and federal e-filing requirements, service and proof of service, filing timing, fees, courtesy copies, rejection or cure windows, and judge or courtroom preferences. Returns structured summaries with source provenance by default. Omitted structured fields are not stated in the source quote; do not infer defaults or negative values.

Input parameters:

- `case_type` (string): Filter by case type. General rules and rules without a case-type limit are included.
- `district_id` (string): Court identifier (e.g., "il-cook-circuit", "ca-los-angeles-superior")
- `include_court_rules` (boolean): When judge_slug is supplied, also include court-level rules where judge_slug is "court". Default: true.
- `include_raw_content` (boolean): Include the full validated ExtractedRuleContentV3 object. Default: false.
- `judge_slug` (string): Judge, calendar, department, or courtroom slug. Use "court" for court-level rules.
- `limit` (number): Maximum results to return. Default: 100, max: 500.
- `logic_type` (string): Filter by rule type, such as "ElectronicFilingRule", "FilingTimingRule", "ServiceRule", "FilingFeeRule", or "CourtesyCopyRule".
- `q` (string): Search terms that must appear in the summary, source text, tags, or structured data, such as "rejected cure" or "courtesy copies".
- `workflow_phase` (string): Filter by workflow phase, such as "FILING" or "MOTION_PRACTICE".

### `search_judges` (~149 tokens)

Search judges

Search for judges by district, name, or type. Returns judge name, slug, type, district, and status.

Input parameters:

- `district_id` (string): Filter by district ID (e.g., "edny", "sdny")
- `include_inactive` (boolean): Include judges who no longer sit in the court's published roster. Off by default: these carry no current rules.
- `judge_type` (string): Filter by judge type (e.g., "district", "magistrate", "senior")
- `limit` (number): Maximum results to return (default: 20)
- `name` (string): Search by judge name (partial match, case-insensitive)

### `get_judge_rules` (~72 tokens)

Get judge rules

Get all extracted rules for a specific judge. Rules come from standing orders and individual practices documents.

Input parameters:

- `district_id` (string, required): The district ID (e.g., "edny")
- `judge_slug` (string, required): The judge's URL slug (e.g., "carol-bagley-amon")

### `check_compliance` (~313 tokens)

Check document compliance

Generate a curl command for the Court Rules compliance check API. This tool does NOT run the check itself; it formats your inputs into a ready-to-use curl command targeting api.courtrules.app/api/v1/check (requires an API key).

Input parameters:

- `district_id` (string, required): The district ID (e.g., "edny")
- `document_scope` (string, required): The document scope being filed. Valid values: "brief_support", "brief_reply", "brief_opposition", "reconsideration_support", "reconsideration_reply", "letter", "discovery_letter", "proposed_findings"…
- `is_pro_se` (boolean): Whether the filer is self-represented (pro se)
- `judge_slug` (string, required): The judge's URL slug (e.g., "carol-bagley-amon")
- `motion_type` (string): The motion type if applicable. Valid values: "Rule_12", "Rule_56", "Rule_50", "Rule_59", "Rule_60", "Daubert", "TRO", "preliminary_injunction", "reconsideration", "discovery", "motion_to_amend", "mot…
- `page_count` (number, required): Number of pages in the document
- `word_count` (number, required): Number of words in the document

### `search_enforcement_actions` (~233 tokens)

Search enforcement actions

Search privacy and regulatory enforcement actions. Filter by jurisdiction (CA, TX, NY, FTC, etc.), date range, industry, violation type, risk level, or entity name. Returns structured enforcement events with fines, violations, and source citations.

Input parameters:

- `date_from` (string): Start date filter (YYYY-MM-DD)
- `date_to` (string): End date filter (YYYY-MM-DD)
- `entity_name` (string): Search by entity/company name (partial match)
- `industry` (string): Industry filter (e.g., "technology", "gaming", "education", "healthcare")
- `jurisdiction` (string): Jurisdiction code (e.g., "CA", "FTC", "NY", "TX", "HHS")
- `limit` (number): Maximum results to return (default: 20, max: 100)
- `risk_level` (string): Risk level filter: "critical", "high", "medium", or "low"
- `violation_type` (string): Violation type filter (e.g., "opt_out_failure", "children_data", "data_breach")

### `get_enforcement_details` (~48 tokens)

Get enforcement action details

Get full details of a specific enforcement action including laws cited, remedies, source quotes, and document URLs.

Input parameters:

- `event_id` (string, required): The UUID or public slug of the enforcement event

### `get_enforcement_stats` (~92 tokens)

Get enforcement statistics

Get summary statistics of enforcement actions. Group by jurisdiction, violation type, risk level, or month to understand enforcement trends.

Input parameters:

- `date_from` (string): Start date filter (YYYY-MM-DD)
- `date_to` (string): End date filter (YYYY-MM-DD)
- `group_by` (string, required): Grouping dimension: "jurisdiction", "violation_type", "risk_level", or "month"

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/app-courtrules-court-rules/mcp#diagnostics

## Score history

- 2026-10-03: 38
- 2026-10-02: 38
- 2026-10-01: 38
- 2026-09-30: 38
- 2026-09-29: 38
- 2026-09-28: 38
- 2026-09-27: 38
- 2026-09-26: 38
- 2026-09-25: 38
- 2026-09-24: 38
- 2026-09-23: 77
- 2026-09-22: 77
- 2026-09-21: 76
- 2026-09-20: 76
- 2026-09-19: 75
- 2026-09-18: 75
- 2026-09-17: 74
- 2026-09-16: 74
- 2026-09-15: 73
- 2026-09-14: 73
- 2026-09-13: 72
- 2026-09-12: 72
- 2026-09-11: 72
- 2026-09-10: 71
- 2026-09-09: 71
- 2026-09-08: 70
- 2026-09-07: 70
- 2026-09-06: 69
- 2026-09-05: 69
- 2026-09-04: 68

## Common questions

### What is the Court Rules MCP server?

Court Rules is an MCP server listed in the public MCP registry as app.courtrules/court-rules. Judge-level filing rules, court holidays and enforcement data for US federal and state courts. This page covers its hosted endpoint (https://mcp.courtrules.app/mcp).

### Is the Court Rules MCP server safe to use?

Court Rules scores 38 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 Court Rules MCP server expose?

Court Rules exposes 9 tools: list_courts, list_court_holidays, search_filing_rules, search_judges, get_judge_rules, and 4 more. Their descriptions and schemas cost roughly 1,422 tokens of context every time the server is loaded.

### Does the Court Rules MCP server require authentication?

Yes. Court Rules asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the Court Rules MCP server still maintained?

Court Rules is still listed as active in the MCP registry. We last reached this channel on 3 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.courtrules.app/mcp
- Website: https://docs.courtrules.app/
- Changelog RSS feed: https://verifymcp.io/servers/app-courtrules-court-rules/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/app-courtrules-court-rules/mcp.json
- HTML version of this page: https://verifymcp.io/servers/app-courtrules-court-rules/mcp