California Court Deadlines
REMOTE · CALCOURTDEADLINES.COM · SCANNED SEP 28
Computes California state court deadlines and cites the code section behind every date. No API key.
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- 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
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability62
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
remote · calcourtdeadlines.com
claude mcp add --transport http com-calcourtdeadlines-deadlines 'https://calcourtdeadlines.com/api/mcp'
{
"mcpServers": {
"com-calcourtdeadlines-deadlines": {
"url": "https://calcourtdeadlines.com/api/mcp"
}
}
} {
"servers": {
"com-calcourtdeadlines-deadlines": {
"type": "http",
"url": "https://calcourtdeadlines.com/api/mcp"
}
}
} [mcp_servers.com-calcourtdeadlines-deadlines] url = "https://calcourtdeadlines.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-calcourtdeadlines-deadlines": {
"type": "remote",
"url": "https://calcourtdeadlines.com/api/mcp",
"enabled": true
}
}
} openclaw mcp add com-calcourtdeadlines-deadlines --url 'https://calcourtdeadlines.com/api/mcp' --transport streamable-http
mcp_servers:
com-calcourtdeadlines-deadlines:
url: "https://calcourtdeadlines.com/api/mcp" {
"McpServers": {
"com-calcourtdeadlines-deadlines": {
"Transport": "http",
"Url": "https://calcourtdeadlines.com/api/mcp"
}
}
} assistant mcp add com-calcourtdeadlines-deadlines -t streamable-http -u 'https://calcourtdeadlines.com/api/mcp'
{
"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.
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 +7
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 +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.
- 26 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 25 Sept 26 63
First indexed and scored.
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 28 Sept 2026 · Probed https://calcourtdeadlines.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=calcourtdeadlines.com | CN=YR2,O=Let's Encrypt,C=US | 26 Sept 2026 | 25 Dec 2026 | RSA 2048 | SHA256-RSA | 68a08d9ffa9e6c329ce98702ffb2f04e224 |
| SANs: calcourtdeadlines.com | ||||||
| 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 calcourtdeadlines.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| calcourtdeadlines.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), interest-cohort=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://calcourtdeadlines.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://calcourtdeadlines.com/api/mcp | HTTPS enforced | 308 | https://calcourtdeadlines.com/api/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 →
california_add_court_days Count California court days from a date ~117
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.
| Name | Type | Req | Description |
|---|---|---|---|
| court_days | integer | yes | How many court days to move. Negative counts backward. |
| date | string | yes | The date to count from. The starting day itself is not counted. |
No output schema declared.
No examples provided.
california_court_day_check Is this a California court day ~75
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.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | The date to check. |
No output schema declared.
No examples provided.
california_court_holidays California court holidays for a year ~80
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.
| Name | Type | Req | Description |
|---|---|---|---|
| year | integer | yes | Four-digit year. |
No output schema declared.
No examples provided.
california_criminal_motion_deadlines California criminal pretrial motion deadlines ~487
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.
| Name | Type | Req | Description |
|---|---|---|---|
| hearing_date | string | yes | 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 | yes | 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). |
No output schema declared.
No examples provided.
california_discovery_response_deadline California discovery response deadline ~203
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.
| Name | Type | Req | Description |
|---|---|---|---|
| discovery_type | string | yes | Which set. rogs = interrogatories; rfp = requests for production; rfa = requests for admission |
| served_date | string | yes | The date the discovery was served on you. |
| service_method | string | yes | 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. |
No output schema declared.
No examples provided.
california_motion_deadlines California civil motion deadlines ~731
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.
| Name | Type | Req | Description |
|---|---|---|---|
| hearing_date | string | yes | 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 | yes | 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 | yes | 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… |
No output schema declared.
No examples provided.
california_response_to_complaint_deadline California deadline to respond to a complaint ~327
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | yes | 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. |
No output schema declared.
No examples provided.
california_summary_judgment_deadlines California summary judgment deadlines ~150
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.
| Name | Type | Req | Description |
|---|---|---|---|
| service_method | string | yes | 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 | yes | The trial date. |
No output schema declared.
No examples provided.
california_trial_countdown California pretrial deadlines from a trial date ~161
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The trial date. |
No output schema declared.
No examples provided.
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.