_ registry / mcp streamable-http · checked 32m ago

calcourtdeadlines

https://calcourtdeadlines.com

Registry code: 0b64cd1f73f5bf27

api record

California civil and criminal litigation deadlines, computed from the Code of Civil Procedure, the Penal Code and the California Rules of Court.

Use these tools for ANY California deadline question rather than computing the date yourself. Court-day counting has to skip weekends and every judicial holiday, service extensions differ by method and run in different directions, and several periods are extended by how the OTHER side served papers rather than by how you will serve yours. Those are the errors that look right.

endpoint
https://calcourtdeadlines.com/api/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is calcourtdeadlines live?
Yes — it answered the hub's last check (checked 32m ago). It answered 99% of checks over the last 30 days.
Is calcourtdeadlines free to use?
Yes — the hub reached it with no key and no payment.
What tools does calcourtdeadlines have?
9 tools: california_add_court_days, california_response_to_complaint_deadline, california_summary_judgment_deadlines, california_trial_countdown, california_motion_deadlines, california_court_holidays, california_criminal_motion_deadlines, california_discovery_response_deadline, ….
Is calcourtdeadlines safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.4%

90 days 99.6%· all time 99.6%

latency
919ms

last good check

priced tools
0

of 9 tools

_ answered our checks, 90 days 284 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • unknown → live
_ what it is for
topic
government & legal legal
used for
  • compute california litigation deadlines
  • add court days to a date
  • check california court holidays
  • compute discovery response deadline
takes → gives
data → data
tools
9 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 9 tools
9 never probed 0 of 9 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • california_add_court_days reads unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "date",
    "court_days"
  ],
  "properties": {
    "date": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "The date to count from. The starting day itself is not counted."
    },
    "court_days": {
      "type": "integer",
      "maximum": 365,
      "minimum": -365,
      "description": "How many court days to move. Negative counts backward."
    }
  },
  "additionalProperties": false
}
    arguments 21 lines
  • california_response_to_complaint_deadline reads unknown 22h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "service_date",
    "service_method"
  ],
  "properties": {
    "case_type": {
      "enum": [
        "general-civil",
        "unlawful-detainer"
      ],
      "type": "string",
      "description": "Unlawful detainer runs on a different statute and a much shorter clock."
    },
    "service_date": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "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 acknowledgment the date the defendant signed."
    },
    "service_method": {
      "enum": [
        "personal",
        "substituted",
        "mail-outside-state",
        "notice-and-acknowledgment"
      ],
      "type": "string",
      "description": "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 outside California; notice-and-acknowledgment = Notice and acknowledgment of receipt"
    },
    "stipulated_15_days": {
      "type": "boolean",
      "description": "True if the parties stipulated to the rule 3.110(d) 15-day extension."
    },
    "court_extension_days": {
      "type": "integer",
      "maximum": 30,
      "minimum": 0,
      "description": "Days of any section 1054 court-ordered extension actually obtained."
    },
    "meet_confer_declaration": {
      "type": "boolean",
      "description": "True if a section 430.41(a)(2) meet-and-confer declaration was filed, which takes an automatic 30 days."
    }
  },
  "additionalProperties": false
}
    arguments 47 lines
  • california_summary_judgment_deadlines reads unknown 15h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "trial_date",
    "service_method"
  ],
  "properties": {
    "trial_date": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "The trial date."
    },
    "service_method": {
      "enum": [
        "electronic",
        "personal",
        "mail-ca",
        "mail-os",
        "mail-intl",
        "overnight"
      ],
      "type": "string",
      "description": "How the moving papers will be served. Section 437c(a)(2) sets its own extension table, which is not the same as section 1013."
    }
  },
  "additionalProperties": false
}
    arguments 27 lines
  • california_trial_countdown reads unknown 15h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "trial_date"
  ],
  "properties": {
    "county": {
      "enum": [
        "los-angeles",
        "san-diego",
        "orange",
        "riverside",
        "san-bernardino",
        "santa-clara",
        "alameda",
        "sacramento",
        "fresno"
      ],
      "type": "string",
      "description": "Optional. Adds that county's local-rule deadlines where they are computable from the trial date."
    },
    "set_date": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "Optional. The date the trial date was set, which some local rules count from."
    },
    "trial_date": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "The trial date."
    },
    "service_method": {
      "enum": [
        "electronic",
        "personal",
        "mail-ca",
        "mail-os",
        "mail-intl",
        "overnight"
      ],
      "type": "string",
      "description": "How the summary judgment papers and the section 998 offer would be served. It sets the section 437c rows and the last day to serve a section 998 offer, which takes the section 1013 and 1010.6 extensions. No published decision applies section 1013(c) or 1010.6 to a 998 offer; the tool applies both on the reasoning of Lecuyer v. Sunset Trails Apts. (2004) 120 Cal.App.4th 920, which decided a mailed offer."
    }
  },
  "additionalProperties": false
}
    arguments 46 lines
  • california_motion_deadlines reads unknown 22h ago

    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 moved off a weekend or judicial holiday: forward under section 12a for a period that runs forward, or back to the preceding court day for a count backward from the hearing, which is this site's stated convention. Use this instead of computing California motion deadlines yourself.

    mcp-tool

    {
  "type": "object",
  "required": [
    "motion",
    "hearing_date",
    "service_method"
  ],
  "properties": {
    "role": {
      "enum": [
        "moving",
        "responding"
      ],
      "type": "string",
      "description": "Whether you are bringing the motion (moving) or responding to it (responding)."
    },
    "motion": {
      "enum": [
        "compel-further",
        "compel-initial",
        "protective-order",
        "demurrer",
        "motion-to-strike",
        "judgment-on-pleadings",
        "quash-service",
        "anti-slapp",
        "msj",
        "reconsideration",
        "new-trial",
        "jnov",
        "preference",
        "reopen-discovery",
        "compel-arbitration",
        "ex-parte"
      ],
      "type": "string",
      "description": "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-strike = Motion to strike; judgment-on-pleadings = Motion for judgment on the pleadings; quash-service = Motion to quash service of summons; anti-slapp = Anti-SLAPP special motion to strike; msj = Motion for summary judgment / adjudication; reconsideration = Motion for reconsideration; new-trial = Motion for new trial; jnov = Motion for judgment notwithstanding the verdict; preference = Motion for trial preference; reopen-discovery = Motion to reopen discovery; compel-arbitration = Motion to compel arbitration; ex-parte = Ex parte application"
    },
    "entry_date": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "new-trial and jnov only: the date judgment was entered. Section 659(a)(2) ends the time 180 days after entry if that comes before 15 days after notice of entry, and with no notice of entry served it is the only limit. Give it whenever it is known."
    },
    "hearing_date": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "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 intention was filed (moving party) or the date the moving brief was served on you (responding party)."
    },
    "trigger_date": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "For a motion that must be brought within a period after an event, the date of that event (for a demurrer to a complaint served with the summons, the date service of the summons was complete, see trigger_papers; for new-trial and jnov, the first service of notice of entry of judgment, by the clerk or by any party). Omit for motions timed only off the hearing date."
    },
    "service_method": {
      "enum": [
        "electronic",
        "personal",
        "mail-ca",
        "mail-os",
        "mail-intl",
        "overnight",
        "mail-sos"
      ],
      "type": "string",
      "description": "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 under section 1013, and under section 1010.6 for electronic service made before January 1, 2027. From that date electronic service adds no time (AB 540, Stats. 2026, ch. 263). Not the same question as trigger_service_method."
    },
    "trigger_papers": {
      "enum": [
        "summons",
        "served",
        "answer"
      ],
      "type": "string",
      "description": "For demurrer, motion-to-strike and anti-slapp only: which papers started the clock. summons = the complaint or cross-complaint served with a summons (the default); trigger_date is then the date service was COMPLETE (delivery for personal service, the 10th day after mailing for substituted service or mail outside California, the signing date for notice and acknowledgment), and no service extension applies. served = an amended complaint, or a cross-complaint served on a party that has appeared; 30 days (60 for anti-slapp) after service, extended under sections 1013 and 1010.6 by trigger_service_method. answer = an answer or amended answer (demurrer and motion-to-strike only); 10 days after service, extended the same way. Ignored for other motions."
    },
    "trigger_service_method": {
      "enum": [
        "electronic",
        "personal",
        "mail-ca",
        "mail-os",
        "mail-intl",
        "overnight",
        "mail-sos"
      ],
      "type": "string",
      "description": "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. It never extends a period that runs from service of a summons: section 1016 takes service of a summons outside sections 1010.6 and 1013, so for a complaint served with the summons it is ignored. The common case is a complaint served personally and a demurrer served electronically. Defaults to personal, which adds nothing, so an unknown answer errs early rather than granting days that were not earned."
    }
  },
  "additionalProperties": false
}
    arguments 91 lines
  • california_court_holidays reads unknown 4h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "year"
  ],
  "properties": {
    "year": {
      "type": "integer",
      "maximum": 2100,
      "minimum": 2000,
      "description": "Four-digit year."
    }
  },
  "additionalProperties": false
}
    arguments 15 lines
  • california_criminal_motion_deadlines reads unknown 4h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "motion",
    "hearing_date"
  ],
  "properties": {
    "role": {
      "enum": [
        "moving",
        "responding"
      ],
      "type": "string",
      "description": "Whether you are bringing the motion or responding."
    },
    "motion": {
      "enum": [
        "pc-995",
        "pc-1510-outside-deadline",
        "pc-1510-outside-deadline-misdemeanor",
        "pc-1424",
        "pc-1538-5-prelim",
        "pc-1538-5-special-hearing",
        "pitchess-criminal",
        "pc-1054-5-compel",
        "pc-1054-7-disclosure",
        "pc-1050-continuance",
        "pc-1049-prepare",
        "crc-4-110-information"
      ],
      "type": "string",
      "description": "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); pc-1510-outside-deadline-misdemeanor = Deadline to preserve pretrial writ review of a § 995 or § 1538.5 denial, misdemeanor (§ 1510); pc-1424 = Motion to recuse the district attorney (§ 1424); pc-1538-5-prelim = Motion to suppress at the preliminary hearing (§ 1538.5(f)); pc-1538-5-special-hearing = Special suppression hearing in superior court (§ 1538.5(i)); pitchess-criminal = Pitchess motion, criminal (Evid. Code § 1043(a)(2)); pc-1054-5-compel = Motion to compel criminal discovery (§ 1054.5(b)); pc-1054-7-disclosure = Reciprocal discovery disclosure deadline (§ 1054.7); pc-1050-continuance = Motion to continue (§ 1050(b)); pc-1049-prepare = Time to prepare for trial (§ 1049); crc-4-110-information = Information after a holding order (CRC 4.110)"
    },
    "hearing_date": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "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."
    },
    "trigger_date": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "For a motion timed from an event, the date of that event (for a section 995 motion, the date of arraignment on the information)."
    }
  },
  "additionalProperties": false
}
    arguments 46 lines
  • california_discovery_response_deadline reads unknown 4h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "served_date",
    "discovery_type",
    "service_method"
  ],
  "properties": {
    "served_date": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "The date the discovery was served on you."
    },
    "discovery_type": {
      "enum": [
        "rogs",
        "rfp",
        "rfa"
      ],
      "type": "string",
      "description": "Which set. rogs = interrogatories; rfp = requests for production; rfa = requests for admission"
    },
    "service_method": {
      "enum": [
        "electronic",
        "personal",
        "mail-ca",
        "mail-os",
        "mail-intl",
        "overnight",
        "mail-sos"
      ],
      "type": "string",
      "description": "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."
    }
  },
  "additionalProperties": false
}
    arguments 38 lines
  • california_court_day_check reads unknown 15h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "date"
  ],
  "properties": {
    "date": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "The date to check."
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 0b64cd1f73f5bf27.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/0b64cd1f73f5bf27/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/0b64cd1f73f5bf27/badge.svg)](https://brick.blue/agent/0b64cd1f73f5bf27?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.