# Court Rules

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

- name: app.courtrules/court-rules
- version: 1.0.0
- connection class: R2 (oauth_consent_once)
- trust: 80/100 flags: no-repository
- quality: 85/100 (good)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/app.courtrules%2Fcourt-rules
- tools: https://api.protogrid.dev/v1/servers/app.courtrules%2Fcourt-rules/tools

**An agent can connect after a one-time OAuth consent by a human.** Remote endpoint behind OAuth 2. Tokens stay with the agent; the registry only exposes the authorization metadata.

## Connection (mcpServers)

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


## Trust

- hygiene: 80
- liveness: 100
- freshness: 85
- provenance: 55
- drivers: +dns-namespace +website +reachable +uptime-100% ~updated-49d-ago -no-repository
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 85/100 (good)

### protocol: n/a (weight 25)

- n/a `protocol.modern`, `protocol.stateless`, `protocol.transport`, `protocol.list_ttl`: no remote answered a protocol handshake (not probed yet, unreachable, or local-only)

### authorization: 83 (weight 15)

- pass `auth.prm`: Protected Resource Metadata (RFC 9728) published
- pass `auth.as_metadata`: authorization server metadata reachable
- warn `auth.cimd`: only Dynamic Client Registration, deprecated in 2026-07-28 in favour of CIMD
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 86 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 9 of 9 tools declare readOnlyHint or destructiveHint
- fail `tools.directory_hints`: no tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: list_courts (destructiveHint, idempotentHint); search_filing_rules (destructiveHint, idempotentHint); search_judges (destructiveHint, idempotentHint); …
- pass `tools.token_cost`: about 2,238 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: n/a (weight 15)

- n/a `stability.changes`, `stability.rug_pull`: tool history not recorded yet

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 9, about 2,238 tokens to load them all
- badge: [![protogrid quality](https://protogrid.dev/badge/app.courtrules/court-rules.svg)](https://protogrid.dev/servers/app.courtrules/court-rules)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

_No tool definition changes recorded._

## Remotes

- https://mcp.courtrules.app/mcp (streamable-http, auth oauth2, reachable true, uptime30d 1)

## Packages

_none_

## Tools (9)

- `check_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).
- `get_enforcement_details`: Get full details of a specific enforcement action including laws cited, remedies, source quotes, and document URLs.
- `get_enforcement_stats`: Get summary statistics of enforcement actions. Group by jurisdiction, violation type, risk level, or month to understand enforcement trends.
- `get_judge_rules`: Get all extracted rules for a specific judge. Rules come from standing orders and individual practices documents.
- `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.
- `list_courts`: List all courts with their status and judge counts
- `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.
- `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.
- `search_judges`: Search for judges by district, name, or type. Returns judge name, slug, type, district, and status.