Fjc Case Outcomes MCP server

@pipeworx/fjc-case-outcomes

Federal caseload and case-outcome statistics — fleet #3271. Complements the court-listener pack: court-listener finds and reads individual dockets and opinions; this pack answers aggregate statistical questions court-listener has no data for ("how many civil rights cases were filed in SDNY in FY2023, and how did they terminate") plus a direct docket+district outcome lookup.

Part of Pipeworx — an MCP gateway connecting AI agents to 1879+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.

Status (2026-10-19): promoted, data loading, tool-examples pending

Migration 264 is applied and fjc-idb-refresh.yml has run for real (run 39288114956): FY2023-24 is loaded — civil 690,312 rows, criminal 435,234 rows, appellate 80,722 rows, plus their summary tables. FY2020-22 is loading separately. The pack was promoted out of incubator in this session, but tool-examples.json, the live smoke payloads, and the post-deploy re-probe are not yet done** — they need a real call through the pack against the live backing tables, which needs the backing database's URL and service-role credential as environment variables (see the ingest script's own header for the exact names), and this session had neither (confirmed absent from .env, every .dev.vars, and the process environment). Running node scripts/add-pack.mjs fjc-case-outcomes stopped cleanly at step 3/11 ("backing-store credentials not injected"). Whoever has the credential: node scripts/add-pack.mjs fjc-case-outcomes --from 3 resumes exactly there and writes tool-examples.json from the real calls.

Sizing and v1 scope (revised 2026-10-19 on PM review)

The FJC publishes one SAS7BDAT file per fiscal year per case type, no query API, no multi-year bulk export. Per-year file naming was confirmed live for FY2021-FY2023 (cv23.sas7bdat, cr23_0.sas7bdat, ap23.sas7bdat — see scripts/ingest-fjc-idb.mjs's header for the filename-probing logic, since the suffix is inconsistent and undocumented).

v1 scope: civil + criminal only, FY2020-FY2024 (5 fiscal years). Appellate is included opportunistically where cheap (see sizing below) but is not the committed scope; bankruptcy is out entirely (see below).

Real measured sizing, not an estimate. FY2023 civil (293,677 rows) and criminal (218,853 rows) were parsed from the live SAS7BDAT files and actually loaded into a local Postgres 17 — raw tables, summary tables, indexes, ANALYZE — then measured with pgtotalrelation_size:

Extrapolated linearly to v1 (5 fiscal years, civil+criminal): ~550 MB — comfortably under the ~1.5 GB ceiling that would force reconsidering the store. Caveat: this extrapolates from ONE year (FY2023); case volume does vary year to year, so actual 5-year size could differ by some margin, but not by the multiples that would change the conclusion. EXPLAIN ANALYZE on both the lookup query (district+docket, indexed) and a filtered summary-table read confirmed index-scan-only, sub-millisecond, zero sequential scans — see the migration's header for the exact plans.

Bankruptcy IDB data is NOT in scope for this build. The FJC has published bankruptcy case data since 2008, but no bk##/bq##/bankr## filename (plain or _0-suffixed) returned HTTP 200 during this session's probing — it likely uses a different naming scheme or portal entirely. Needs separate research before it can be sized; not attempted further here to keep this build's scope honest rather than guess at a URL.

Store

Shortened. The full README is on GitHub.