Court Rules
REMOTE · MCP.COURTRULES.APP · SCANNED OCT 3
Judge-level filing rules, court holidays and enforcement data for US federal and state courts.
Available components
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 Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
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. Claim this server and supply a read-only token to verify it and lift the score.
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.
remote · mcp.courtrules.app
claude mcp add --transport http app-courtrules-court-rules 'https://mcp.courtrules.app/mcp'
{
"mcpServers": {
"app-courtrules-court-rules": {
"url": "https://mcp.courtrules.app/mcp"
}
}
} {
"servers": {
"app-courtrules-court-rules": {
"type": "http",
"url": "https://mcp.courtrules.app/mcp"
}
}
} [mcp_servers.app-courtrules-court-rules] url = "https://mcp.courtrules.app/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"app-courtrules-court-rules": {
"type": "remote",
"url": "https://mcp.courtrules.app/mcp",
"enabled": true
}
}
} openclaw mcp add app-courtrules-court-rules --url 'https://mcp.courtrules.app/mcp' --transport streamable-http
mcp_servers:
app-courtrules-court-rules:
url: "https://mcp.courtrules.app/mcp" {
"McpServers": {
"app-courtrules-court-rules": {
"Transport": "http",
"Url": "https://mcp.courtrules.app/mcp"
}
}
} assistant mcp add app-courtrules-court-rules -t streamable-http -u 'https://mcp.courtrules.app/mcp'
{
"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.
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.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 −39
- Endpoint reachability: reachable → behind authorisation ▼ security
- Stability: 0.77 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → unverified ▼ security
- Authorization: unverified → pass ▲ security
- First check of Authorization: partial security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 23 Sept 26 0
- “search_judges” added an optional parameter “include_inactive” cosmetic
1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.
- 22 Sept 26 +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.
- 21 Sept 26 0
- Tool “search_filing_rules” rewrote its description, which is the text the model reads security
- 20 Sept 26 +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.
- 18 Sept 26 +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.
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 3 Oct 2026 · Probed https://mcp.courtrules.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.courtrules.app | CN=YR2,O=Let's Encrypt,C=US | 27 Sept 2026 | 26 Dec 2026 | RSA 2048 | SHA256-RSA | 541554b0f0483043711144c8eec8f914bdb |
| SANs: mcp.courtrules.app | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.courtrules.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| courtrules.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer resource_metadata="https://mcp.courtrules.app/.well-known/oauth-protected-resource"
Bearer resource_metadata="https://mcp.courtrules.app/.well-known/oauth-protected-resource"| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
| www-authenticate | Bearer resource_metadata="https://mcp.courtrules.app/.well-known/oauth-protected-resource" |
Protected resource metadata
| Document | https://mcp.courtrules.app/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.courtrules.app |
| Authorisation server | https://oqvwpyfecjnloczitpfx.supabase.co/auth/v1 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.courtrules.app/mcp | Auth required | 401 | |
| http (plaintext) | http://mcp.courtrules.app/mcp | HTTPS enforced | 308 | https://mcp.courtrules.app/mcp |
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 →
check_compliance Check document compliance ~313
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).
| Name | Type | Req | Description |
|---|---|---|---|
| district_id | string | yes | The district ID (e.g., "edny") |
| document_scope | string | yes | 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 | yes | 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 | yes | Number of pages in the document |
| word_count | number | yes | Number of words in the document |
No output schema declared.
No examples provided.
get_enforcement_details Get enforcement action details ~48
Get full details of a specific enforcement action including laws cited, remedies, source quotes, and document URLs.
| Name | Type | Req | Description |
|---|---|---|---|
| event_id | string | yes | The UUID or public slug of the enforcement event |
No output schema declared.
No examples provided.
get_enforcement_stats Get enforcement statistics ~92
Get summary statistics of enforcement actions. Group by jurisdiction, violation type, risk level, or month to understand enforcement trends.
| Name | Type | Req | Description |
|---|---|---|---|
| date_from | string | – | Start date filter (YYYY-MM-DD) |
| date_to | string | – | End date filter (YYYY-MM-DD) |
| group_by | string | yes | Grouping dimension: "jurisdiction", "violation_type", "risk_level", or "month" |
No output schema declared.
No examples provided.
get_judge_rules Get judge rules ~72
Get all extracted rules for a specific judge. Rules come from standing orders and individual practices documents.
| Name | Type | Req | Description |
|---|---|---|---|
| district_id | string | yes | The district ID (e.g., "edny") |
| judge_slug | string | yes | The judge's URL slug (e.g., "carol-bagley-amon") |
No output schema declared.
No examples provided.
list_court_holidays List court holidays ~127
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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) |
No output schema declared.
No examples provided.
list_courts List courts ~43
List all courts with their status and judge counts
| Name | Type | Req | Description |
|---|---|---|---|
| status | string | – | Filter by court status: "live", "preview", or "coming_soon" |
No output schema declared.
No examples provided.
search_enforcement_actions Search enforcement actions ~233
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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") |
No output schema declared.
No examples provided.
search_filing_rules Search filing rules ~345
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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". |
No output schema declared.
No examples provided.
search_judges Search judges ~149
Search for judges by district, name, or type. Returns judge name, slug, type, district, and status.
| Name | Type | Req | Description |
|---|---|---|---|
| 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) |
No output schema declared.
No examples provided.
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.