# California Court Deadlines (remote · calcourtdeadlines.com)

Computes California state court deadlines and cites the code section behind every date. No API key.

- Trust score: 71/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-28

## Components

- remote · `calcourtdeadlines.com`: 71/100 (this document), [markdown](https://verifymcp.io/servers/com-calcourtdeadlines-deadlines/api-mcp.md), [page](https://verifymcp.io/servers/com-calcourtdeadlines-deadlines/api-mcp)

## Channel facts

- Endpoint: `https://calcourtdeadlines.com/api/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-09-28.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - 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.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 62/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2541 tokens (~282/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 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 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the California Court Deadlines MCP server?

California Court Deadlines is a hosted endpoint at https://calcourtdeadlines.com/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 com-calcourtdeadlines-deadlines 'https://calcourtdeadlines.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-calcourtdeadlines-deadlines": {
      "url": "https://calcourtdeadlines.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-calcourtdeadlines-deadlines": {
      "type": "http",
      "url": "https://calcourtdeadlines.com/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-calcourtdeadlines-deadlines]
url = "https://calcourtdeadlines.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-calcourtdeadlines-deadlines": {
      "type": "remote",
      "url": "https://calcourtdeadlines.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-calcourtdeadlines-deadlines --url 'https://calcourtdeadlines.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-calcourtdeadlines-deadlines:
    url: "https://calcourtdeadlines.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-calcourtdeadlines-deadlines": {
      "Transport": "http",
      "Url": "https://calcourtdeadlines.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-calcourtdeadlines-deadlines -t streamable-http -u 'https://calcourtdeadlines.com/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-calcourtdeadlines-deadlines": {
      "type": "http",
      "url": "https://calcourtdeadlines.com/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-09-28 (score 71, +7)

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

### 2026-09-27 (score 64, +1)

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

### 2026-09-26 (score 63, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-25 (score 63)

First indexed and scored.

## MCP tools (9)

### `california_motion_deadlines` (~731 tokens)

California civil motion deadlines

Compute the California Code of Civil Procedure section 1005 briefing chain for a noticed civil motion: the last day to file and serve the moving papers, the opposition deadline, the reply deadline, and, for motions that must be brought within a period after a triggering event (demurrer, motion to strike, anti-SLAPP, motion to quash, motion to compel further, reconsideration, new trial, JNOV), the outside deadline to bring the motion at all. New trial and JNOV are the exception to the section 1005 chain: they are briefed under section 659a, counted forward (brief 10 days after the notice of intention is filed, opposition 10 days after the brief is served, reply 5 days after that), with the section 660(c) last day for the court to rule. Returns each date with the statute it rests on and whether it was rolled off a weekend or judicial holiday under section 12a. Use this instead of computing California motion deadlines yourself.

Input parameters:

- `hearing_date` (string, required): The hearing date, as reserved with the department. EXCEPT for new-trial and jnov, which are briefed under section 659a and do not count back from a hearing: for those, give the date the notice of int…
- `motion` (string, required): Which motion. compel-further = Motion to compel further responses; compel-initial = Motion to compel initial responses; protective-order = Motion for protective order; demurrer = Demurrer; motion-to-…
- `role` (string): Whether you are bringing the motion (moving) or responding to it (responding).
- `service_method` (string, required): How the MOVING PAPERS will be served. This drives the section 1005(b) notice period. For new-trial and jnov it is how the moving brief is served, which extends the section 659a opposition period unde…
- `trigger_date` (string): For a motion that must be brought within a period after an event, the date of that event (for a demurrer, the date the complaint was served). Omit for motions timed only off the hearing date.
- `trigger_service_method` (string): How the TRIGGERING papers were served ON the moving party. This is a different question from service_method and only this one extends the time to BRING the motion under section 1013. The common case…

### `california_response_to_complaint_deadline` (~327 tokens)

California deadline to respond to a complaint

Compute when a response to a California complaint is due. Handles the four service methods separately, because each completes service on a different day, and applies the extensions a defendant may claim: the section 430.41 meet-and-confer declaration, the rule 3.110(d) stipulated 15 days, and a court-ordered extension. Unlawful detainer runs on section 1167 instead and is handled as its own case type.

Input parameters:

- `case_type` (string): Unlawful detainer runs on a different statute and a much shorter clock.
- `court_extension_days` (integer): Days of any section 1054 court-ordered extension actually obtained.
- `meet_confer_declaration` (boolean): True if a section 430.41(a)(2) meet-and-confer declaration was filed, which takes an automatic 30 days.
- `service_date` (string, required): The date on the proof of service. What it means depends on the method: for personal service the date of delivery, for substituted service the date of the substituted delivery, for notice and acknowle…
- `service_method` (string, required): How the summons and complaint were served. personal = Personal delivery; substituted = Substituted service (left with someone, then mailed); mail-outside-state = First-class mail to a defendant outsi…
- `stipulated_15_days` (boolean): True if the parties stipulated to the rule 3.110(d) 15-day extension.

### `california_discovery_response_deadline` (~203 tokens)

California discovery response deadline

Compute when responses to California written discovery are due: interrogatories, requests for production, or requests for admission. Takes the date the discovery was served and how it was served, applies the section 1013 extension for that method (or the section 1010.6 extension for electronic service made before January 1, 2027, which AB 540 removes for service on or after that date), and rolls the result off weekends and judicial holidays under section 12a.

Input parameters:

- `discovery_type` (string, required): Which set. rogs = interrogatories; rfp = requests for production; rfa = requests for admission
- `served_date` (string, required): The date the discovery was served on you.
- `service_method` (string, required): How the discovery was served on you. This is what the section 1013 and 1010.6 extensions key to. Electronic service made on or after January 1, 2027 adds nothing.

### `california_summary_judgment_deadlines` (~150 tokens)

California summary judgment deadlines

Compute the California Code of Civil Procedure section 437c deadlines that hang off a trial date: the last day a summary judgment motion can be heard (30 days before trial), the last day to file and serve it (81 days' notice plus the service extension; electronic service made on or after January 1, 2027 adds none), and the opposition and reply dates if the motion is heard on the last possible day.

Input parameters:

- `service_method` (string, required): How the moving papers will be served. Section 437c(a)(2) sets its own extension table, which is not the same as section 1013.
- `trial_date` (string, required): The trial date.

### `california_trial_countdown` (~161 tokens)

California pretrial deadlines from a trial date

Work backward from a California civil trial date to the pretrial deadlines: the discovery cutoff and the motion cutoff, the expert exchange and expert discovery cutoffs, the last day to serve written discovery so responses are due before the cutoff, and the summary judgment dates. Optionally adds the local-rule deadlines for one of the counties this site tracks.

Input parameters:

- `county` (string): Optional. Adds that county's local-rule deadlines where they are computable from the trial date.
- `service_method` (string): How summary judgment papers would be served, for the section 437c rows.
- `set_date` (string): Optional. The date the trial date was set, which some local rules count from.
- `trial_date` (string, required): The trial date.

### `california_criminal_motion_deadlines` (~487 tokens)

California criminal pretrial motion deadlines

Compute the California Rule of Court 4.111 briefing chain for a criminal pretrial motion: service of the moving papers, the proof of service, opposition, reply, and the hearing. Also gives the outside deadline for motions that run from a triggering event, such as the Penal Code section 995 motion and the section 1510 tracks. There is no service-method extension in criminal motions; rule 4.111 does not provide one.

Input parameters:

- `hearing_date` (string, required): The hearing date. For the section 1538.5(i) special hearing, this is instead the date notice was given to the People, because that clock runs forward.
- `motion` (string, required): Which motion. pc-995 = Motion to set aside the information or indictment (§ 995); pc-1510-outside-deadline = Deadline to preserve pretrial writ review of a § 995 or § 1538.5 denial, FELONY (§ 1510);…
- `role` (string): Whether you are bringing the motion or responding.
- `trigger_date` (string): For a motion timed from an event, the date of that event (for a section 995 motion, the date of arraignment on the information).

### `california_court_holidays` (~80 tokens)

California court holidays for a year

List every California judicial holiday for a given year, with the date it is observed. These are the days excluded when counting court days and the days a deadline rolls off under Code of Civil Procedure section 12a. Includes the weekend-observed shifts, which are the ones most often got wrong.

Input parameters:

- `year` (integer, required): Four-digit year.

### `california_court_day_check` (~75 tokens)

Is this a California court day

Say whether a given date is a California court day, and if it is not, give the next date it would roll forward to under Code of Civil Procedure section 12a. Use this before asserting that a filing date or a deadline falls on a working day.

Input parameters:

- `date` (string, required): The date to check.

### `california_add_court_days` (~117 tokens)

Count California court days from a date

Add or subtract court days from a date, skipping weekends and California judicial holidays. Use this for any period a statute states in court days rather than calendar days, such as the nine and five court day opposition and reply periods under Code of Civil Procedure section 1005(b). Counting court days by hand is where most deadline errors come from.

Input parameters:

- `court_days` (integer, required): How many court days to move. Negative counts backward.
- `date` (string, required): The date to count from. The starting day itself is not counted.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-calcourtdeadlines-deadlines/api-mcp#diagnostics

## Score history

- 2026-09-28: 71
- 2026-09-27: 64
- 2026-09-26: 63
- 2026-09-25: 63

## Common questions

### What is the California Court Deadlines MCP server?

California Court Deadlines is an MCP server listed in the public MCP registry as com.calcourtdeadlines/deadlines. Computes California state court deadlines and cites the code section behind every date. No API key. This page covers its hosted endpoint (https://calcourtdeadlines.com/api/mcp).

### Is the California Court Deadlines MCP server safe to use?

California Court Deadlines scores 71 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 California Court Deadlines MCP server expose?

California Court Deadlines exposes 9 tools: california_motion_deadlines, california_response_to_complaint_deadline, california_discovery_response_deadline, california_summary_judgment_deadlines, california_trial_countdown, and 4 more. Their descriptions and schemas cost roughly 2,331 tokens of context every time the server is loaded.

### Does the California Court Deadlines MCP server require authentication?

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

### Is the California Court Deadlines MCP server still maintained?

California Court Deadlines is still listed as active in the MCP registry. We last reached this channel on 28 September 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://calcourtdeadlines.com/api/mcp
- Website: https://calcourtdeadlines.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-calcourtdeadlines-deadlines/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-calcourtdeadlines-deadlines/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-calcourtdeadlines-deadlines/api-mcp