General Tools
federalcourtdeadlines.com
Computes federal civil litigation deadlines and legal holiday counts under FRCP, FRAP, and local court rules.
ENDPOINT 1
https://federalcourtdeadlines.com/api/mcp
MCP server metadata
- Name
- federalcourtdeadlines
- Version
- 1.0.0
Federal civil litigation deadlines, computed from the Federal Rules of Civil Procedure, Federal Rule of Appellate Procedure 4, and 28 U.S.C. 1446 and 1447, and from a district court's own local rules for the districts federal_local_deadline accepts. Use these tools for ANY federal civil deadline question rather than computing the date yourself. Rule 6(a) rolls a period measured after an event forward and a period measured before an event back, Rule 6(d) adds 3 days only after the roll and only for some methods of service, and several questions (observed holidays, presidential closure days, whether Rule 6(d) reaches a period) are not settled. Those are the errors that look right. For a motion, an opposition or a reply in a district whose local rules apply, use federal_local_deadline: a local rule usually sets times that replace FRCP 6(c). Every answer gives the due date under the prevailing reading, and when the readings differ it also gives the earliest date (safe for a party computing its own deadline) and the latest date (the floor for arguing that someone else filed late). Every open question and note travels with the date. Repeat the authority, the earliest date and the notes when you report a date. Do not present any of this as legal advice: chambers rules, a case management order or a judge's standing order can move almost any of these dates. Local rules apply only for the districts federal_local_deadline accepts; for any other district the dates follow the federal rules alone. No state holidays are applied yet. 70 rule rows transcribed from the official text, the latest on October 5, 2026. None has been countersigned yet. Every answer says "not yet countersigned" until an attorney countersigns the rows it used. Nothing here reads or writes any user's data.
Known tools 4
federal_deadlineCompute one federal civil deadline under the Federal Rules of Civil Procedure, FRAP 4 or 28 U.S.C.
Inferred read-onlyfederal_legal_holidaysList the legal holidays for a year under FRCP 6(a)(6) and FRAP 26(a)(6): the eleven days in 5 U.S.C.
Inferred read-onlyfederal_count_daysCount 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).
Inferred read-onlyfederal_local_deadlineCompute 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.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.federalcourtdeadlines]
url = "https://federalcourtdeadlines.com/api/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"federalcourtdeadlines": {
"type": "http",
"url": "https://federalcourtdeadlines.com/api/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: federalcourtdeadlines
Remote MCP URL: https://federalcourtdeadlines.com/api/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"federalcourtdeadlines": {
"url": "https://federalcourtdeadlines.com/api/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"federalcourtdeadlines": {
"type": "http",
"url": "https://federalcourtdeadlines.com/api/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "federalcourtdeadlines",
"transport": "streamable-http",
"url": "https://federalcourtdeadlines.com/api/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.