Home / MCP registry index / com.calcourtdeadlines/deadlines
California Court Deadlines
com.calcourtdeadlines/deadlines in the official MCP registry.
Endpoint https://calcourtdeadlines.com/api/mcp.
The registry describes it as: Computes California state court deadlines and cites the code section behind every date. No API key.
We read its 9 tools on 2026-10-26. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
california_motion_deadlines california_response_to_complaint_deadline california_discovery_response_deadline california_summary_judgment_deadlines california_trial_countdown california_criminal_motion_deadlines california_court_holidays california_court_day_check california_add_court_days
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-calcourtdeadlines-deadlines)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.