# Federal Civil (npm · @pipeworx/mcp-federal-civil)

Federal civil litigation — US federal court dockets.

- Trust score: 81/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 77/100, [markdown](https://verifymcp.io/servers/pipeworx-io-federal-civil/federal-civil-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-federal-civil/federal-civil-mcp)
- npm · `@pipeworx/mcp-federal-civil`: 81/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-federal-civil/pipeworx-mcp-federal-civil.md), [page](https://verifymcp.io/servers/pipeworx-io-federal-civil/pipeworx-mcp-federal-civil)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-federal-civil`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

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. 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.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-federal-civil).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 3 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 60/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add pipeworx-io-federal-civil -- npx -y @pipeworx/mcp-federal-civil
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-federal-civil": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-federal-civil"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-federal-civil": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-federal-civil"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-federal-civil -- npx -y @pipeworx/mcp-federal-civil
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-federal-civil": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-federal-civil"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-federal-civil --command npx --arg -y --arg @pipeworx/mcp-federal-civil
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-federal-civil:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-federal-civil"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-federal-civil": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-federal-civil"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-federal-civil -t stdio -c npx -a -y @pipeworx/mcp-federal-civil
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-federal-civil": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-federal-civil"
      ]
    }
  }
}
```

## 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-03 (score 81, +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-11-01 (score 80, +2)

- [security regression] 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.
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional improvement] Stability: unverified → 0.10
- [functional] First check of Schema quality: unverified
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-29 (score 78)

First indexed and scored.

## MCP tools (2)

### `federal_civil_search` (~376 tokens)

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.

Input parameters:

- `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, required): Party name or a distinctive part of it, e.g. "Monsanto".

### `federal_civil_recent` (~156 tokens)

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.

Input parameters:

- `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).

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-federal-civil/pipeworx-mcp-federal-civil#diagnostics

## Score history

- 2026-11-05: 81
- 2026-11-04: 81
- 2026-11-03: 81
- 2026-11-02: 80
- 2026-11-01: 80
- 2026-10-31: 78
- 2026-10-30: 78
- 2026-10-29: 78

## Common questions

### 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.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-federal-civil
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-federal-civil
- Repository: https://github.com/pipeworx-io/mcp-federal-civil
- Website: https://pipeworx.io/packs/federal-civil
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-federal-civil/pipeworx-mcp-federal-civil.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-federal-civil/pipeworx-mcp-federal-civil.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-federal-civil/pipeworx-mcp-federal-civil