California Court Deadlines
com.calcourtdeadlines/deadlines · 1.0.0
Computes California state court deadlines and cites the code section behind every date. No API key.
Nobody here has read this server's code, because it publishes none. The description above is the maker's own, from the registry. A connection test shows whether it answers and what tools it says it has; it never calls a tool, so it cannot show what one does with your data.
Where it sits in the directory's order
What can be seen from outside, weighed as the directory publishes.
Observable signals: 45 of 100 points (at most 60 here)
| Input | Points | What was seen |
|---|---|---|
| Source published | held at 0 | No entry here publishes source: that is what puts it in this directory. |
| Licence stated | held at 0 | With no files, there is nothing for a licence to be stated in or held against. |
| Advisory state | held at 0 | Advisory databases index packages, and these entries publish none, so there is nothing to look up. |
| Auth declared | 0 of 15 | The registry entry declares no key. That is what it declares, not a finding that it has no protection. |
| Latest connection test reached it | 20 of 20 |
Where it answers
https://calcourtdeadlines.com/api/mcpstreamable-http
Connection test
The MCP handshake, then a request for the tool list, with no key and no data of yours. Run nightly, and by anyone, at most once every ten minutes per server.
It completed the handshake and listed 9 tools.
- Protocol
- 2025-06-18
- Calls itself
- calcourtdeadlines 1.2.0
- Handshake time
- 68 ms
- HTTP status
- 200
The tools it lists (9, as of 4 days ago)
The tool-description rules found nothing in these descriptions. They look for instructions aimed at a model and for hidden characters; they cannot see what a tool does when it runs.
california_motion_deadlinesCompute 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 int
california_response_to_complaint_deadlineCompute 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.
california_discovery_response_deadlineCompute 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.
california_summary_judgment_deadlinesCompute 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.
How this entry becomes a listing
For the maker. The catalogue lists what it can read, and this server publishes nothing to read yet. There are two routes, and only the first is open today.
Publish the source Open today
- Put the server's source in a public repository on github.com, with a licence.
- Keep a server.json in that repository naming this server,
com.calcourtdeadlines/deadlines, and declare the repository in it:"repository": { "url": "https://github.com/owner/repo", "source": "github" }, adding"subfolder"when the server lives in a folder. - Publish that version to the official MCP registry.
- The nightly registry sweep records the declaration. This page stays, dated, and says the source is declared but not yet read.
- The catalogue reads declared repositories at a pinned commit, in batches run by hand, and lists the servers that meet the batch's rules (among them a server.json at that commit naming the server, an https endpoint and a licence). When it lists this server, this page links to the listing. There is no schedule, so no date can be promised.
List it through the maker studio Not open yet
From the official MCP registry, last updated there 12 days ago. The registry entry · calcourtdeadlines.com