Fjc Case Outcomes
NPM · @PIPEWORX/MCP-FJC-CASE-OUTCOMES · 2 COMPONENTS
Federal Judicial Center (FJC), Integrated Database — federal case outcomes (fleet #3271).…
Available components
Last scanned (2 hours ago)
Scores higher than 65% of npm servers
Category Education and Research
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-fjc-case-outcomes). 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 Usability56
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 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.
- 4 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.
- 2 Nov 26 +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.
- 1 Nov 26 +1
- 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.07 ▲ functional
- First check of Schema quality: unverified functional
- Package version: 0.2.0 → 0.2.1 functional
- 31 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 30 Oct 26 77
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-fjc-case-outcomes@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-fjc-case-outcomes |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-fjc-case-outcomes/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3635943732 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:91b3ef525a10b41a5dd789312f25e0f775971d7340a9e4281f0e77e2f8d798f00170a215974683ddf8f544351bda1ba5bc5c90230d651c92e3c3049ba |
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 →
fjc_case_outcome_lookup ~306
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.
| Name | Type | Req | Description |
|---|---|---|---|
| case_type | string | yes | 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 | yes | FJC numeric district code (civil/criminal) or circuit code (appellate) the case was filed in. |
| docket | string | yes | 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). |
No output schema declared.
No examples provided.
fjc_case_outcomes_summary ~360
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.
| Name | Type | Req | Description |
|---|---|---|---|
| case_type | string | yes | 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. |
No output schema declared.
No examples provided.
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.
npm · @pipeworx/mcp-fjc-case-outcomes
claude mcp add pipeworx-io-fjc-case-outcomes -- npx -y @pipeworx/mcp-fjc-case-outcomes
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.