# 1Court Directory (remote · state.1court.ai)

US county court directory: clerk, courthouse address, e-filing, filing fees, and case lookup.

- Trust score: 81/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `state.1court.ai`: 81/100 (this document), [markdown](https://verifymcp.io/servers/ai-1court-state-court-directory/api-mcp.md), [page](https://verifymcp.io/servers/ai-1court-state-court-directory/api-mcp)

## Channel facts

- Endpoint: `https://state.1court.ai/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## 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-11-05.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1164 tokens (~194/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 50/100
  - Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the 1Court Directory MCP server?

1Court Directory is a hosted endpoint at https://state.1court.ai/api/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 ai-1court-state-court-directory 'https://state.1court.ai/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ai-1court-state-court-directory": {
      "url": "https://state.1court.ai/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ai-1court-state-court-directory": {
      "type": "http",
      "url": "https://state.1court.ai/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ai-1court-state-court-directory]
url = "https://state.1court.ai/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-1court-state-court-directory": {
      "type": "remote",
      "url": "https://state.1court.ai/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-1court-state-court-directory --url 'https://state.1court.ai/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-1court-state-court-directory:
    url: "https://state.1court.ai/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ai-1court-state-court-directory": {
      "Transport": "http",
      "Url": "https://state.1court.ai/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-1court-state-court-directory -t streamable-http -u 'https://state.1court.ai/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ai-1court-state-court-directory": {
      "type": "http",
      "url": "https://state.1court.ai/api/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-11-05 (score 81, +1)

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

### 2026-11-03 (score 80, +1)

- [security] Tool “list_deadline_rules” rewrote its description, which is the text the model reads
- [cosmetic] “calculate_deadline” reworded the description of “state”
- [cosmetic] “list_deadline_rules” reworded the description of “state”

### 2026-11-01 (score 79, +1)

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

### 2026-10-29 (score 78, +1)

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

### 2026-10-28 (score 77, 0)

- [security] Tool “list_deadline_rules” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 164 → 190
- [cosmetic] “calculate_deadline” reworded the description of “state”
- [cosmetic] “list_deadline_rules” reworded the description of “state”

### 2026-10-27 (score 77, 0)

- [security] Tool “list_deadline_rules” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 147 → 164
- [cosmetic] “calculate_deadline” reworded the description of “state”
- [cosmetic] “calculate_deadline” reworded the description of “court”
- [cosmetic] “list_deadline_rules” reworded the description of “court”
- [cosmetic] “list_deadline_rules” reworded the description of “state”

### 2026-10-25 (score 77, +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.

### 2026-10-24 (score 76, −1)

- [functional regression] Schema quality: pass → fail
- [functional] New tool “calculate_deadline”
- [functional] New tool “list_deadline_rules”

## MCP tools (6)

### `list_deadline_rules` (~523 tokens)

List the court deadline types 1Court can calculate for a jurisdiction. Available ids: TX; CA (civil), CA-FAM (family), CA-PROB (probate), CA-UD (unlawful detainer), CA-SC (small claims), CA-GOV (government claims), CA-CRIM (criminal), CA-JUV (juvenile dependency and delinquency), CA-PRESUIT (employment, housing and pre-suit clocks: foreclosure, HOA, ADA/Unruh, FEHA, EEOC, PAGA, arbitration fees, med-mal notice, CEQA, mechanics liens), CA-AGENCY (WCAB, OAH, CUIAB, SPB, PERB, Labor Commissioner, Cal/OSHA Appeals Board, Office of Tax Appeals, DMV, CPUC, ALRB, State Bar Court), CA-SPECIAL (eminent domain, elections, LPS, elder abuse, traffic), CA-APP (appeals and writs), CA-SOL (statutes of limitations); US (federal civil and appellate), US-CRIM (federal criminal), US-BK (bankruptcy). Add county (California superior court, e.g. los-angeles) or court (cacd, cand, casd, caed, ca9 for US and US-CRIM; cacb, canb, casb, caeb for US-BK; 1dca to 6dca for CA-APP) to include local rules. Returns each deadline with the governing rule citation for each. Use before calculate_deadline to get valid deadline_type ids.

Input parameters:

- `county` (string): California county slug for local rules, e.g. "los-angeles", "san-diego" (CA sets only)
- `court` (string): Court for local rules: cacd, cand, casd, caed, ca9 (US); cacb, canb, casb, caeb (US-BK); 1dca, 2dca, 3dca, 4dca, 5dca, 6dca (CA-APP)
- `state` (string, required): Rule-set id: TX, CA, CA-FAM, CA-PROB, CA-UD, CA-SC, CA-GOV, CA-CRIM, CA-JUV, CA-PRESUIT, CA-AGENCY, CA-SPECIAL, CA-APP, CA-SOL, US, US-CRIM, or US-BK

### `calculate_deadline` (~313 tokens)

Calculate a court deadline deterministically from cited rules (weekends, legal holidays, short-period and mail-service rules applied). Returns the date, each computation step, and the rule text and source. Always show the user the citation and caveats; this is not legal advice.

Input parameters:

- `county` (string): California county slug, to use that superior court's local rules and closures
- `court` (string): Court id for local rules: cacd, cand, casd, caed, ca9, cacb, canb, casb, caeb, or 1dca to 6dca (CA-APP)
- `deadline_type` (string, required): Deadline id from list_deadline_rules, e.g. "answer_district_county"
- `service_method` (string): How the triggering paper or summons was served, e.g. "mail" (TX), "mail_in_state", "electronic", "substituted" (CA). Omit for personal service.
- `state` (string, required): Rule-set id: TX, CA, CA-FAM, CA-PROB, CA-UD, CA-SC, CA-GOV, CA-CRIM, CA-JUV, CA-PRESUIT, CA-AGENCY, CA-SPECIAL, CA-APP, CA-SOL, US, US-CRIM, or US-BK
- `trigger_date` (string, required): Trigger date as YYYY-MM-DD (e.g. date of service or date judgment signed)

### `list_states` (~44 tokens)

List all U.S. states currently covered by the 1Court Directory, with how many counties are available in each. Use this to discover coverage before looking up a specific county.

### `list_counties` (~79 tokens)

List the counties covered in a given U.S. state (accepts a full state name, 2-letter code, or slug). Returns each county name and its 1Court page URL.

Input parameters:

- `state` (string, required): State name, 2-letter code, or slug, e.g. "California", "CA", or "california"

### `get_court_info` (~130 tokens)

Get verified court information for a specific U.S. county: clerk of court contacts, e-filing provider and whether e-filing is mandatory, filing fees (civil, small claims, divorce), case lookup, self-help, jury service, and payment links. Data is sourced from official court/clerk records. Always cite the returned 1Court source URL.

Input parameters:

- `county` (string, required): County name, e.g. "Harris" or "Harris County"
- `state` (string, required): State name, 2-letter code, or slug, e.g. "Texas", "TX"

### `search_courts` (~75 tokens)

Search the 1Court Directory by county or state name and get matching counties with their 1Court page URLs. Use when you are unsure of the exact county or state format.

Input parameters:

- `query` (string, required): A county or state name, e.g. "Maricopa", "Cook County", or "Nevada"

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-1court-state-court-directory/api-mcp#diagnostics

## Score history

- 2026-11-05: 81
- 2026-11-04: 80
- 2026-11-03: 80
- 2026-11-02: 79
- 2026-11-01: 79
- 2026-10-31: 78
- 2026-10-30: 78
- 2026-10-29: 78
- 2026-10-28: 77
- 2026-10-27: 77
- 2026-10-26: 77
- 2026-10-25: 77
- 2026-10-24: 76
- 2026-10-23: 77
- 2026-10-22: 77
- 2026-10-21: 76

## Common questions

### What is the 1Court Directory MCP server?

1Court Directory is an MCP server listed in the public MCP registry as ai.1court.state/court-directory. US county court directory: clerk, courthouse address, e-filing, filing fees, and case lookup. This page covers its hosted endpoint (https://state.1court.ai/api/mcp).

### Is the 1Court Directory MCP server safe to use?

1Court Directory scores 81 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 1Court Directory MCP server expose?

1Court Directory exposes 6 tools: list_deadline_rules, calculate_deadline, list_states, list_counties, get_court_info, search_courts. Their descriptions and schemas cost roughly 1,164 tokens of context every time the server is loaded.

### Does the 1Court Directory MCP server require authentication?

No. We connected to 1Court Directory without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the 1Court Directory MCP server still maintained?

1Court Directory 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.

### What did VerifyMCP test on the 1Court Directory MCP server?

VerifyMCP ran 13 checks on 1Court Directory, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://state.1court.ai/api/mcp
- Website: https://state.1court.ai/developers
- Changelog RSS feed: https://verifymcp.io/servers/ai-1court-state-court-directory/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-1court-state-court-directory/api-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/ai-1court-state-court-directory/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/ai-1court-state-court-directory/api-mcp