MCP server exposing 2 tools for fjc-case-outcomes.
This URL is a JSON-RPC 2.0 endpoint over HTTP. Issue POST requests with a JSON-RPC body. Browsers and search crawlers land here on GET.
POST https://gateway.pipeworx.io/fjc-case-outcomes/mcp
Content-Type: application/json
{"jsonrpc":"2.0","id":1,"method":"tools/list"}fjc_case_outcome_lookup — 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.fjc_case_outcomes_summary — 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.Code samples (curl / TypeScript / one-click client install), schemas, and the live playground are on the pack page:
https://pipeworx.io/packs/fjc-case-outcomes/
Pipeworx is an open MCP gateway connecting AI agents to live data. pipeworx.io