# Federal Court Deadlines (remote · federalcourtdeadlines.com) Federal civil deadlines (FRCP, FRAP 4, removal, listed district local rules), with the rule quoted. - Trust score: 72/100 (medium) - Change this week: +3 - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-11-05 ## Components - remote · `federalcourtdeadlines.com`: 72/100 (this document), [markdown](https://verifymcp.io/servers/com-federalcourtdeadlines-deadlines/api-mcp.md), [page](https://verifymcp.io/servers/com-federalcourtdeadlines-deadlines/api-mcp) ## Channel facts - Endpoint: `https://federalcourtdeadlines.com/api/mcp` - Transports: `streamable-http` - Auth: `none` - Version: `1.0.0` ## Trust breakdown 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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog) Scored 2026-11-05. - **Endpoint Security**: 80/100 - The endpoint's TLS certificate is valid, in date, and uses a strong key. - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. - HTTPS is enforced; there's no plaintext access path. - The HSTS (Strict-Transport-Security) header is present. - DNSSEC check failed: this domain isn't protected by DNSSEC. - **Transport & Reachability**: 100/100 - Verified streamable-http transport via a live MCP handshake. - **Schema Quality & AI Usability**: 54/100 - AI-judged instruction clarity (excellent). - Context-footprint check failed: tool/resource definitions use about 4834 tokens (~1208/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. - Usage-examples check failed: none of the tools include examples. - **Stability & Change Management**: 30/100 - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses. - **Tool Coverage**: 100/100 - 100% of tools have a non-trivial description (not blank, and not just the tool's name). - 100% of tool parameters carry a description. - **Tool Safety**: 100/100 - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured. - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation. - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it. - **Capabilities**: 60/100 - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. ## Install ### How do I install the Federal Court Deadlines MCP server? Federal Court Deadlines is a hosted endpoint at https://federalcourtdeadlines.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. ### Claude ```bash claude mcp add --transport http com-federalcourtdeadlines-deadlines 'https://federalcourtdeadlines.com/api/mcp' ``` ### Cursor ```json { "mcpServers": { "com-federalcourtdeadlines-deadlines": { "url": "https://federalcourtdeadlines.com/api/mcp" } } } ``` ### VS Code ```json { "servers": { "com-federalcourtdeadlines-deadlines": { "type": "http", "url": "https://federalcourtdeadlines.com/api/mcp" } } } ``` ### Codex ```toml [mcp_servers.com-federalcourtdeadlines-deadlines] url = "https://federalcourtdeadlines.com/api/mcp" ``` ### opencode ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "com-federalcourtdeadlines-deadlines": { "type": "remote", "url": "https://federalcourtdeadlines.com/api/mcp", "enabled": true } } } ``` ### OpenClaw ```bash openclaw mcp add com-federalcourtdeadlines-deadlines --url 'https://federalcourtdeadlines.com/api/mcp' --transport streamable-http ``` ### Hermes ```yaml mcp_servers: com-federalcourtdeadlines-deadlines: url: "https://federalcourtdeadlines.com/api/mcp" ``` ### Netclaw ```json { "McpServers": { "com-federalcourtdeadlines-deadlines": { "Transport": "http", "Url": "https://federalcourtdeadlines.com/api/mcp" } } } ``` ### Vellum ```bash assistant mcp add com-federalcourtdeadlines-deadlines -t streamable-http -u 'https://federalcourtdeadlines.com/api/mcp' ``` ### Other ```json { "mcpServers": { "com-federalcourtdeadlines-deadlines": { "type": "http", "url": "https://federalcourtdeadlines.com/api/mcp" } } } ``` The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs. ## Changelog Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims. ### 2026-11-04 (score 72, +1) No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-11-01 (score 71, +1) No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-10-30 (score 70, +1) No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-10-28 (score 69, +1) - [functional improvement] Stability: unverified → 0.03 ### 2026-10-27 (score 68) First indexed and scored. ## MCP tools (4) ### `federal_deadline` (~2796 tokens) Federal civil deadline for one rule 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 calls for it. Returns the due date under the prevailing reading and, when the readings differ, the earliest date (safe for a party computing its own deadline) and the latest date (the floor for arguing someone else was late), with every open question, the rule text, the authority and the countersign status. A deadline a district court's own local rules set is returned by federal_local_deadline. Input parameters: - `compliance_date` (string): FRCP 45(d)(2)(B) only, required there: the date for compliance stated in the subpoena. - `compliance_time` (string): FRCP 45(d)(2)(B) only, required there: the time for compliance stated in the subpoena, 24-hour HH:MM. - `defendant_appeared_date` (string): FRCP 26(f)(1) only, with defendant_served_date: the date any defendant appeared, if known. - `defendant_served_date` (string): 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… - `district` (string): 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 th… - `frap_delivery` (string): 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 t… - `outside_district` (boolean): 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. - `reason` (integer): 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. - `rule` (string, required): 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 (F… - `second_trigger_date` (string): 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… - `service_method` (string): 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… - `third_trigger_date` (string): A third date, used only by FRCP 81(c)(2): service of the summons for an initial pleading on file. - `trigger_date` (string): 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, o… - `us_party` (boolean): 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 make… ### `federal_legal_holidays` (~151 tokens) Federal legal holidays for a year 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 treats it as a legal holiday and that the point is not settled. State holidays are not applied. Input parameters: - `year` (integer, required): Four-digit year, 2024 to 2030. ### `federal_count_days` (~724 tokens) Count a federal period in days 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 under the prevailing reading, and the earliest and latest dates when observed or closure days make the readings differ. Use this for a period no specific rule row covers, such as one set by a court order. With court_open_days, counts only days a district court is open instead, for a local rule that states its period that way. Input parameters: - `court_open_days` (boolean): 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… - `date` (string, required): The date of the event the period counts from. That day itself is not counted. - `days` (integer, required): 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. - `district` (string): 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. - `frap_delivery` (string): 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-… - `regime` (string): frcp (default) counts under FRCP 6(a), for the district court; frap counts under FRAP 26(a), for an appeal. - `service_method` (string): 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 res… ### `federal_local_deadline` (~707 tokens) Deadline under a district court's local rules 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's computation rule, applies the days the court's posted schedule closes it and the court's own mail rule, and returns the due date under the prevailing reading with the earliest and latest dates where the readings differ, the federal date a local rule replaces, the time of day where the rule sets one, the court's notes, the rule text and the countersign status. A district this site does not cover returns the districts it does. Input parameters: - `district` (string, required): 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, required): 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… - `schedule` (boolean): 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. - `second_trigger_date` (string): 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): 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 re… - `trigger_date` (string): 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… ## Diagnostics Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-federalcourtdeadlines-deadlines/api-mcp#diagnostics ## Score history - 2026-11-05: 72 - 2026-11-04: 72 - 2026-11-03: 71 - 2026-11-02: 71 - 2026-11-01: 71 - 2026-10-31: 70 - 2026-10-30: 70 - 2026-10-29: 69 - 2026-10-28: 69 - 2026-10-27: 68 ## Common questions ### What is the Federal Court Deadlines MCP server? Federal Court Deadlines is an MCP server listed in the public MCP registry as com.federalcourtdeadlines/deadlines. Federal civil deadlines (FRCP, FRAP 4, removal, listed district local rules), with the rule quoted. This page covers its hosted endpoint (https://federalcourtdeadlines.com/api/mcp). ### Is the Federal Court Deadlines MCP server safe to use? Federal Court Deadlines scores 72 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 Federal Court Deadlines MCP server expose? Federal Court Deadlines exposes 4 tools: federal_deadline, federal_legal_holidays, federal_count_days, federal_local_deadline. Their descriptions and schemas cost roughly 4,378 tokens of context every time the server is loaded. ### Does the Federal Court Deadlines MCP server require authentication? No. We connected to Federal Court Deadlines without credentials and it answered, so anything it exposes is reachable by anyone who knows the address. ### Is the Federal Court Deadlines MCP server still maintained? Federal Court Deadlines is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced. ## Links - Remote endpoint: https://federalcourtdeadlines.com/api/mcp - Website: https://federalcourtdeadlines.com/ - Changelog RSS feed: https://verifymcp.io/servers/com-federalcourtdeadlines-deadlines/api-mcp.xml - Changelog JSON feed: https://verifymcp.io/servers/com-federalcourtdeadlines-deadlines/api-mcp.json - HTML version of this page: https://verifymcp.io/servers/com-federalcourtdeadlines-deadlines/api-mcp