Federal Civil
NPM · @PIPEWORX/MCP-FEDERAL-CIVIL · 2 COMPONENTS
Federal civil litigation — US federal court dockets.
Available components
Last scanned (2 hours ago)
Scores higher than 68% of npm servers
Category Documents and Files
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-federal-civil). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability60
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 587 tokens (~293/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Nov 26 +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.
- 1 Nov 26 +2
- Tool safety: pass → unverified ▼ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Stability: unverified → 0.10 ▲ functional
- First check of Schema quality: unverified functional
- Package version: 0.2.0 → 0.2.1 functional
- 29 Oct 26 78
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/@pipeworx/mcp-federal-civil@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-federal-civil |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-federal-civil/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3635941147 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:67289b0610368fe79c1fee0c1725e90c432d70b4b30225efc5cce73f9f75d2b7dd4df7d5dee6547c41dea348fa3aacb748df6344e086d9bf752f39639 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
federal_civil_recent ~156
List recent US federal civil lawsuits, newest first, optionally limited to one district. No API key. A case removed from state court carries a removed_from object naming the originating state court and its state docket number.
| Name | Type | Req | Description |
|---|---|---|---|
| check_removal | boolean | – | Look up which state court each case was removed from (default true). Set false to skip one upstream request per call when you do not need it. |
| court | string | – | Optional federal district id, e.g. "cand", "nysd", "ilnd". |
| filed_after | string | – | Only cases filed on or after this date, YYYY-MM-DD. |
| limit | number | – | Maximum dockets to return (1-50, default 20). |
No output schema declared.
No examples provided.
federal_civil_search ~376
Find US FEDERAL CIVIL LAWSUITS by party name. Searches federal district court civil dockets, no API key — contract disputes, civil rights, employment, product liability, ERISA, social security appeals and prisoner petitions. Returns case caption, docket number, district, filing and termination dates, assigned judge, and the nature-of-suit code where the court recorded one. Use for "is this company being sued in federal court" and litigation exposure checks. A party search also runs a live, token-less CourtListener search for anything filed after the snapshot_date the bulk data carries and merges it in, so a suit filed last week is found; those rows are marked coverage:"live" and carry the full party list, which catches a derivative suit captioned against officers rather than the company. A case REMOVED from state court carries a removed_from object giving the originating state court and its state docket number, so the state and federal records can be linked — a removal is otherwise invisible on a federal docket, whose cause code describes the federal statute invoked rather than where the case came from.
| Name | Type | Req | Description |
|---|---|---|---|
| check_removal | boolean | – | Look up which state court each case was removed from (default true). Set false to skip one upstream request per call when you do not need it. |
| court | string | – | Optional federal district id, e.g. "cand", "nysd", "ilnd". |
| filed_after | string | – | Only cases filed on or after this date, YYYY-MM-DD. |
| filed_before | string | – | Only cases filed on or before this date, YYYY-MM-DD. |
| limit | number | – | Maximum dockets to return (1-50, default 10). |
| party | string | yes | Party name or a distinctive part of it, e.g. "Monsanto". |
No output schema declared.
No examples provided.
How do I install the Federal Civil MCP server?
Federal Civil runs locally as an npm package, launched with npx -y @pipeworx/mcp-federal-civil. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-federal-civil
claude mcp add pipeworx-io-federal-civil -- npx -y @pipeworx/mcp-federal-civil
What is the Federal Civil MCP server?
Federal Civil is an MCP server listed in the public MCP registry as io.github.pipeworx-io/federal-civil. Federal civil litigation, US federal court dockets. This page covers its npm package (@pipeworx/mcp-federal-civil).
Is the Federal Civil MCP server safe to use?
Federal Civil scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Civil MCP server expose?
Federal Civil exposes 2 tools: federal_civil_search, federal_civil_recent. Their descriptions and schemas cost roughly 532 tokens of context every time the server is loaded.
Is the Federal Civil MCP server still maintained?
Federal Civil 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.
What licence is the Federal Civil MCP server under?
Federal Civil declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.