# Fjc Case Outcomes (npm · @pipeworx/mcp-fjc-case-outcomes)

Federal Judicial Center (FJC), Integrated Database — federal case outcomes (fleet #3271).…

- Trust score: 80/100 (high trust)
- 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-fjc-case-outcomes/fjc-case-outcomes-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-fjc-case-outcomes/fjc-case-outcomes-mcp)
- npm · `@pipeworx/mcp-fjc-case-outcomes`: 80/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-fjc-case-outcomes/pipeworx-mcp-fjc-case-outcomes.md), [page](https://verifymcp.io/servers/pipeworx-io-fjc-case-outcomes/pipeworx-mcp-fjc-case-outcomes)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-fjc-case-outcomes`
- 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-fjc-case-outcomes).
  - 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**: 56/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 724 tokens (~362/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**: 20/100
  - Stability observed for 6 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 Fjc Case Outcomes MCP server?

Fjc Case Outcomes runs locally as an npm package, launched with npx -y @pipeworx/mcp-fjc-case-outcomes. 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-fjc-case-outcomes -- npx -y @pipeworx/mcp-fjc-case-outcomes
```

### Cursor

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

### VS Code

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

### Codex

```bash
codex mcp add pipeworx-io-fjc-case-outcomes -- npx -y @pipeworx/mcp-fjc-case-outcomes
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add pipeworx-io-fjc-case-outcomes --command npx --arg -y --arg @pipeworx/mcp-fjc-case-outcomes
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-fjc-case-outcomes:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-fjc-case-outcomes"]
```

### Netclaw

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

### Vellum

```bash
assistant mcp add pipeworx-io-fjc-case-outcomes -t stdio -c npx -a -y @pipeworx/mcp-fjc-case-outcomes
```

### Other

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

## 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 80, +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-02 (score 79, +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-11-01 (score 78, +1)

- [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.07
- [functional] First check of Schema quality: unverified
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-31 (score 77, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-10-30 (score 77)

First indexed and scored.

## MCP tools (2)

### `fjc_case_outcome_lookup` (~306 tokens)

Look up a SPECIFIC federal case or criminal defendant by docket number in the Federal Judicial Center's Integrated Database (FJC IDB) — civil case, criminal defendant, or appellate case. Needs a docket number plus a district (civil/criminal, FJC's own numeric district code) or circuit (appellate, FJC's own numeric circuit code). Returns filing/termination dates, nature-of-suit or offense code, disposition code, and (civil only) party names / judgment amount, or (criminal only) sentence terms. Complements court-listener (which has the docket TEXT and filings, not this statistical-outcome record). A no-match response names the filters tried. Periodic snapshot, refreshed on a schedule — the response carries `data_as_of`. Keyless.

Input parameters:

- `case_type` (string, required): Which FJC IDB dataset to search.
- `defendant_number` (number): Criminal only: defendant number within a multi-defendant case (the IDB is defendant-level for criminal cases).
- `district_or_circuit` (string, required): FJC numeric district code (civil/criminal) or circuit code (appellate) the case was filed in.
- `docket` (string, required): Docket number, FJC's own format (as published in the IDB, not the PACER-formatted number).
- `fiscal_year` (number): Narrow to one fiscal year, if known (recommended — the same docket can recur across years).

### `fjc_case_outcomes_summary` (~360 tokens)

Aggregate federal caseload statistics from the Federal Judicial Center's Integrated Database (FJC IDB) — case counts by nature of suit (civil/appellate), offense code (criminal), disposition, fiscal year and district/circuit. Returns the TOTAL count first, then a breakdown grouped by whichever dimensions you ask for. Requires fiscal_year AND/OR district_or_circuit (an unfiltered query across every year and district cannot be answered accurately). Use this for "how many X cases were filed/terminated in district Y in year Z" questions — for a single case's outcome use fjc_case_outcome_lookup instead. Periodic snapshot, refreshed on a schedule — the response carries `data_as_of`. Keyless.

Input parameters:

- `case_type` (string, required): Which FJC IDB dataset to aggregate.
- `disposition_code` (number): FJC disposition code at termination.
- `district_or_circuit` (string): FJC numeric district code (civil/criminal) or circuit code (appellate). Required if fiscal_year is omitted.
- `fiscal_year` (number): Restrict to one FJC fiscal year (October-September; pre-1992 is July-June — see the pack README). Required if district_or_circuit is omitted.
- `group_by` (array): Dimensions to break the total down by (default: nature_of_suit_code for civil/appellate, offense_code for criminal).
- `limit` (number): Max breakdown rows to return, 1-200 (default 50).
- `nature_of_suit_code` (number): Civil/appellate only: FJC nature-of-suit code.
- `offense_code` (string): Criminal only: FJC lead-offense code at filing.

## Diagnostics

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

## Score history

- 2026-11-05: 80
- 2026-11-04: 80
- 2026-11-03: 79
- 2026-11-02: 79
- 2026-11-01: 78
- 2026-10-31: 77
- 2026-10-30: 77

## Common questions

### What is the Fjc Case Outcomes MCP server?

Fjc Case Outcomes is an MCP server listed in the public MCP registry as io.github.pipeworx-io/fjc-case-outcomes. Federal Judicial Center (FJC), Integrated Database, federal case outcomes (fleet #3271).… This page covers its npm package (@pipeworx/mcp-fjc-case-outcomes).

### Is the Fjc Case Outcomes MCP server safe to use?

Fjc Case Outcomes scores 80 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 Fjc Case Outcomes MCP server expose?

Fjc Case Outcomes exposes 2 tools: fjc_case_outcome_lookup, fjc_case_outcomes_summary. Their descriptions and schemas cost roughly 666 tokens of context every time the server is loaded.

### Is the Fjc Case Outcomes MCP server still maintained?

Fjc Case Outcomes 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 Fjc Case Outcomes MCP server under?

Fjc Case Outcomes 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-fjc-case-outcomes
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-fjc-case-outcomes
- Repository: https://github.com/pipeworx-io/mcp-fjc-case-outcomes
- Website: https://pipeworx.io/packs/fjc-case-outcomes
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-fjc-case-outcomes/pipeworx-mcp-fjc-case-outcomes.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-fjc-case-outcomes/pipeworx-mcp-fjc-case-outcomes.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-fjc-case-outcomes/pipeworx-mcp-fjc-case-outcomes