Federal Court Deadlines MCP server
com.federalcourtdeadlines/deadlinesfederalcourtdeadlines.comstreamable-httpv1.0.0Scanned
Federal civil deadlines (FRCP, FRAP 4, removal, listed district local rules), with the rule quoted.
4 tools: 2 change things and 2 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Federal Court Deadlines MCP server can do
The Federal Court Deadlines MCP server is published by federalcourtdeadlines.com, a domain the MCP Registry verified. It has 4 tools. It can create or change data (2 tools: federal_deadline and federal_local_deadline), but cannot delete data. 2 tools only read.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 9, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
4 tools
Changes things 2Claude Code: ask
federal_deadlineCompute one federal civil deadline under the Federal Rules of Civil Procedure, FRAP 4 or 28 U.S.C.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
federal_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 h…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
Only reads 2Show 2 read-only tools
federal_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 n…No findings
Why it is in this group
- The name "federal_count_days" says "count": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
federal_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.No findings
Why it is in this group
- The description's first verb is "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 18, 2026, 16:23 UTC, unchanged since Oct 27, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 2
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://federalcourtdeadlines.com/api/mcp: tools/list returned 4 tools to an anonymous client, including federal_deadline (write), federal_local_deadline (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http deadlines https://federalcourtdeadlines.com/api/mcpclaude mcp add --transport http deadlines https://federalcourtdeadlines.com/api/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__deadlines__federal_legal_holidays",
"mcp__deadlines__federal_count_days"
],
"ask": [
"mcp__deadlines__federal_deadline",
"mcp__deadlines__federal_local_deadline"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as deadlines. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.federalcourtdeadlines/deadlines/verify?hash=6475caeb8b4eec1049250bbea20d8f8b29c30b636b667212f8346a828e3f435d" | jq -e '.changed == false'Pinned hash 6475caeb8b4e, from Nov 9, 2026, 13:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.federalcourtdeadlines/deadlines/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.federalcourtdeadlines/deadlines)Source: MCP Registry. Synced Oct 26, 2026, 23:17 UTC.
Federal Court Deadlines MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Federal Court Deadlines MCP server safe?
- No scan can promise that. What its definitions show: 4 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Federal Court Deadlines MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Federal Court Deadlines MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Federal Court Deadlines MCP server have?
- 4 tools: 2 write, 2 read. federal_deadline, federal_local_deadline, federal_legal_holidays and federal_count_days.
Does the Federal Court Deadlines MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Federal Court Deadlines MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Federal Court Deadlines MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 9, 2026.