Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
Federal Court Deadlines is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
96/100
tool-list score
4
tools declared
remote
at its publisher
—
calls last 7d
What it does
Federal civil deadlines (FRCP, FRAP 4, removal, listed district local rules), with the rule quoted.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http federal-court-deadlines-mcp https://federalcourtdeadlines.com/api/mcp
# 2 — ask your agent for something these tools do
# federal_deadline, federal_legal_holidays, federal_count_days and 1 more
Federal Court Deadlines costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
FEAll 1 server
federalcourtdeadlines1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http federal-court-deadlines-mcp https://federalcourtdeadlines.com/api/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
4 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Compute one federal civil deadline under the Federal Rules of Civil Procedure, FRAP 4 or 28 U.S.C. 1446 and 1447, from the date of the event the rule counts from. Counts under FRCP 6(a) (FRAP 26(a) for an appeal), rolls off weekends and legal holidays in the direction the rule requires, and adds 3 days under Rule 6(d) or FRAP 26(c) only when that rule reaches the period and the method of service c
| Parameter | Type | Required | Notes |
|---|---|---|---|
| rule | string | yes | The rule row to compute. Each id names the rule and subdivision: fed-frcp-4m (FRCP 4(m), after the complaint is filed); fed-frcp-4d1F (FRCP 4(d)(1)(F), after the request was sent); fed-frcp-12a1Ai (FR |
| trigger_date | string | no | Required, except on fed-frcp-26f1 when defendant_served_date is given. The date of the event the rule counts from, in the rule's own words above: the date of service, entry, filing, the conference, or |
| defendant_served_date | string | no | FRCP 26(f)(1) only, when neither the scheduling conference date nor the date the scheduling order is due is known: the date any defendant was served with the complaint. Rule 16(b)(2) is then computed |
| defendant_appeared_date | string | no | FRCP 26(f)(1) only, with defendant_served_date: the date any defendant appeared, if known. |
| second_trigger_date | string | no | A second date, for a row that compares two periods: FRCP 12(a)(3) the other service date; 15(a)(1)(B) the service date of the other paper; 15(a)(3) the date the response to the original pleading was d |
| third_trigger_date | string | no | A third date, used only by FRCP 81(c)(2): service of the summons for an initial pleading on file. |
| service_method | string | no | How the paper that starts the period was served, under FRCP 5(b)(2). Only mail, leaving it with the clerk and other consented means add 3 days, and only on a period that runs after being served: 5b2C- |
| frap_delivery | string | no | For an appeal period that runs after being served: how the paper was delivered, under FRAP 26(c). served-electronically = Served electronically: adds nothing; delivered-on-proof-date = Delivered on th |
| district | string | no | Optional. The CM/ECF id of the district court, such as casd (S.D. Cal.), cacd (C.D. Cal.), nysd (S.D.N.Y.) or dcd (D.D.C.). Adds the time the last day ends where the court states it, the notes for tha |
| compliance_date | string | no | FRCP 45(d)(2)(B) only, required there: the date for compliance stated in the subpoena. |
| compliance_time | string | no | FRCP 45(d)(2)(B) only, required there: the time for compliance stated in the subpoena, 24-hour HH:MM. |
| reason | integer | no | FRCP 60(c)(1) only, required there: the reason under Rule 60(b), 1 to 6. Reasons 1 to 3 have a one-year outer limit; reasons 4 to 6 have no fixed date. |
| outside_district | boolean | no | FRCP 4(d)(1)(F) and 12(a)(1)(A)(ii): true when the waiver request was sent to the defendant outside any judicial district of the United States. |
| us_party | boolean | no | FRAP 4(a)(3), 4(a)(4) and 4(a)(5): true when one of the parties is the United States, a United States agency, or an officer or employee in one of the four categories FRAP 4(a)(1)(B) lists, which makes |
List the legal holidays for a year under FRCP 6(a)(6) and FRAP 26(a)(6): the eleven days in 5 U.S.C. 6103(a), the Friday observed for a Saturday holiday (5 U.S.C. 6103(b)(1)), the Monday observed for a Sunday holiday (Executive Order 11582), and the days the President closed the executive branch. These are the days a federal deadline rolls off. Each observed or closure day says which reading treat
| Parameter | Type | Required | Notes |
|---|---|---|---|
| year | integer | yes | Four-digit year, 2024 to 2030. |
Count a period stated in days from a date under FRCP 6(a) or FRAP 26(a): leave out the trigger day, count every day, and if the last day is a weekend or legal holiday roll to the next open day (or, for a period counted backward before an event, to the preceding one). Optionally adds 3 days under FRCP 6(d) or FRAP 26(c) after the roll, for a period that runs after being served. Returns the due date
| Parameter | Type | Required | Notes |
|---|---|---|---|
| date | string | yes | The date of the event the period counts from. That day itself is not counted. |
| days | integer | yes | How many days: calendar days, or with court_open_days only days the court is open. Negative counts backward, for a period measured before an event. Not zero. |
| court_open_days | boolean | no | Optional, FRCP only, and only with a district whose local rules this site applies (federal_local_deadline accepts it): true counts only days that court is open, skipping weekends, legal holidays and t |
| regime | string | no | frcp (default) counts under FRCP 6(a), for the district court; frap counts under FRAP 26(a), for an appeal. |
| service_method | string | no | FRCP only, and only when the period runs after being served: how the paper was served under Rule 5(b)(2). Mail, leaving it with the clerk and other consented means add 3 days under Rule 6(d); the rest |
| frap_delivery | string | no | FRAP only, and only when the period runs after being served: how the paper was delivered. "other" adds 3 days under FRAP 26(c). served-electronically = Served electronically: adds nothing; delivered-o |
| district | string | no | Optional. The CM/ECF id of the district court, such as casd, cacd, nysd or dcd. Adds the notes for that district and the Ninth Circuit notes for California districts. Required with court_open_days. |
Compute a deadline a federal district court's own local rules set, for the districts whose local rules this site applies: a motion, an opposition or a reply counted back from the hearing date, and the court's other periods the rules fix. Give the rule as the court's own citation or a row id; rule "list" returns the district's rows and the date each counts from. Counts under FRCP 6(a) and the court
| Parameter | Type | Required | Notes |
|---|---|---|---|
| district | string | yes | Required. The CM/ECF id of the district court, such as "casd". Only districts whose local rules this site applies are accepted; any other id returns the list of those that are. |
| rule | string | yes | Required. The row to compute: a row id from the list, the court's own citation as its local rules print it (for example "CivLR 7.1.e.1"), matched without regard to case, or "list" for every row this s |
| trigger_date | string | no | Required unless rule is "list". The date the row counts from, in the row's own words (the list gives them): for a motion, opposition or reply, the hearing date; for an earliest-hearing row, the date t |
| second_trigger_date | string | no | Only on a row that asks for a second date (the list says which): the other date of a row that takes the later of two periods, or the date a federal rule's own period counts from. |
| service_method | string | no | How the paper was served, under FRCP 5(b)(2), on a row whose date depends on it (the list says which). A local rule's own extra days for mail, or Rule 6(d)'s 3 days, are added only where that rule rea |
| schedule | boolean | no | Optional. true returns every paper of the briefing schedule the row belongs to, for the one hearing date in trigger_date, with the dates under FRCP 6(c) alone beside them. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Federal Court Deadlines or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 96 / 100
Release 1.0.0 · scanned 28 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score96
Findings0 threat · 0 capability
Capabilityminimal
Coveragemanifest
Verificationnot in this report
Surface digest7b6ebef9b04ccb823954d92eaeaa28bd4a097c56040837c3c563f05b3fc3412f
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| federal_deadline | no tags | |
| federal_legal_holidays | no tags | |
| federal_count_days | no tags | |
| federal_local_deadline | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest7b6ebef9b04ccb82
Scanned2026-10-28
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Federal Court Deadlines can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.