Court Rules is an MCP server with 9 tools an agent can call, among them check_compliance, get_enforcement_details, get_enforcement_stats. It answers at https://mcp.courtrules.app/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 10 of 10 times since 5 September 2026; the last check, on 18 October 2026, succeeded.
Judge-level filing rules, court holidays and enforcement data for US federal and state courts.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
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). Inputs: judge_slug, district_id, document_scope, motion_type, page_count, word_count |
get_enforcement_details | Get full details of a specific enforcement action including laws cited, remedies, source quotes, and document URLs. Inputs: event_id |
get_enforcement_stats | Get summary statistics of enforcement actions. Group by jurisdiction, violation type, risk level, or month to understand enforcement trends. Inputs: group_by, date_from, date_to |
get_judge_rules | Get all extracted rules for a specific judge. Rules come from standing orders and individual practices documents. Inputs: judge_slug, district_id |
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. Inputs: district_id, year, date_from, date_to, limit |
list_courts | List all courts with their status and judge counts Inputs: status |
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 ci Inputs: jurisdiction, date_from, date_to, industry, violation_type, entity_name |
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 pr Inputs: district_id, judge_slug, include_court_rules, logic_type, workflow_phase, case_type |
search_judges | Search for judges by district, name, or type. Returns judge name, slug, type, district, and status. Inputs: district_id, name, judge_type, limit |
Every block below points at https://mcp.courtrules.app/mcp. Pick your client and copy.
claude mcp add --transport http court-rules https://mcp.courtrules.app/mcp
{
"mcpServers": {
"court-rules": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.courtrules.app/mcp"]
}
}
}{
"mcpServers": {
"court-rules": {
"url": "https://mcp.courtrules.app/mcp"
}
}
}{
"servers": {
"court-rules": {
"type": "http",
"url": "https://mcp.courtrules.app/mcp"
}
}
}{
"context_servers": {
"court-rules": {
"url": "https://mcp.courtrules.app/mcp"
}
}
}{
"mcpServers": {
"court-rules": {
"serverUrl": "https://mcp.courtrules.app/mcp"
}
}
}{
"mcpServers": {
"court-rules": {
"url": "https://mcp.courtrules.app/mcp"
}
}
}name: Court Rules
version: 0.0.1
schema: v1
mcpServers:
- name: Court Rules
type: streamable-http
url: https://mcp.courtrules.app/mcp{
"mcpServers": {
"court-rules": {
"httpUrl": "https://mcp.courtrules.app/mcp"
}
}
}{
"mcpServers": {
"court-rules": {
"type": "http",
"url": "https://mcp.courtrules.app/mcp"
}
}
}{
"mcpServers": {
"court-rules": {
"url": "https://mcp.courtrules.app/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fmcp.courtrules.app%2Fmcp&type=streamable_http&id=court-rules&name=Court%20Rules
It answered our last check on 18 October 2026 in 229 ms. Over 10 checks since 5 September 2026 it answered 10. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by courtrules.app and served from mcp.courtrules.app, the vendor's own domain: https://mcp.courtrules.app/mcp.
9, as returned by the server's own tools/list on 31 August 2026: check_compliance, get_enforcement_details, get_enforcement_stats, get_judge_rules, list_court_holidays, list_courts, search_enforcement_actions, search_filing_rules, and 1 more.
It answered our last check on 18 October 2026 in 229 ms. Over 10 checks since 5 September 2026 it answered 10.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://mcp.courtrules.app/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: app.courtrules. Endpoint host: mcp.courtrules.app. ARD identifier: urn:air:app.courtrules:mcp:court-rules.
First indexed 31 August 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.