Prototyp · Vorschau: alle Server aus der offiziellen Registry, alle 30 Minuten synchronisiert. Mit Google anmelden, um Bewertungen zu schreiben.Prototyp · alle 30 Min. aktualisiert
PopNx MCPMCP-Server für alle, die KI nutzen · in einfachen Worten erklärt

Fjc Case Outcomes

von pipeworx-ioVersion 0.2.1i★ 0iComputer oder CloudOffizielle Website ↗
Name in der Registryio.github.pipeworx-io/fjc-case-outcomes

So installierst du es

What it does

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

  • Connects Computer oder Cloud
  • Account or key No key needed
  • Category Datenbanken & Datensätze

Zusammen nutzen mit

Skills, die der KI diese Art Arbeit beibringen; sie funktionieren zusammen mit diesem

timesfm

TimesFM (Time Series Foundation Model) is a pretrained time-series foundation model developed by Google Research for time-series forecasting.

von google-research★ 35.6381 Skills

Skill · Anleitung

Shadowbroker

Open-source intelligence for the global theater. Track everything from the corporate/private jets of the wealthy, and spy satellites, to seismic events in one unified interface. Hook an AI agent up to have it parse through data and find previously unseen correlations. The knowledge is available to…

von BigBodyCobain★ 11.6051 Skills

Skill · Anleitung

google-maps-scraper

scrape data from Google Maps. Extracts data such as the name, address, phone number, website URL, rating, reviews number, latitude and longitude, reviews,email and more for each place

von gosom★ 8.2361 Skills

Skill · Anleitung

Warum es hier steht

Listen sind nach einem Nutzungswert (von 100) aus diesen Teilen sortiert

Beliebtheit0/80GitHub-Sterne oder wöchentliche Downloads: der größere Wert zählt 60, der kleinere 20
Aktualität12/12Volle Punkte für Release oder Codeänderung in 30 Tagen
Antwortet noch8/8Der Cloud-Endpoint antwortete bei der letzten Prüfung
Nutzungswert20/100

Qualität: 5/5 Basisprüfungen bestanden (angezeigt, nicht zur Sortierung) · Schwung: Noch keine Daten (Nur im Tab Im Trend verwendet)

Installation

Wähle die KI-App, die du nutzt, und kopiere die Einstellungen.

Mit einem Satz von deiner KI installieren lassen

Installiere bitte Fjc Case Outcomes. Folge https://mcp.popnx.com/i/pipeworx-io-fjc-case-outcomes.md, zeig mir die Befehle und warte auf mein OK, bevor du sie ausführst.

Füge ihn in eine KI ein, die auf deinem Rechner arbeitet (z. B. Claude Code oder Cursor). Sie liest unsere Schritte, zeigt dir die Befehle und wartet auf dein OK. Kein Schlüssel, keine Anmeldung. · Vollständigen Text ansehen

5/5 Prüfungen bestanden · Was du fragst, läuft über den Server des Anbieters (gateway.pipeworx.io) · ✓ Befehle geprüft am 14. Nov. 2026

Zuerst: Welche KI nutzt du?

Wähle deine App, dann erscheinen die Schritte unten.

Klappt mit Claude · etwa 2 Min.

Kein Schlüssel, nichts zu installieren · Einmal auf claude.ai oder in der Desktop-App einrichten, dann im Chat nutzen · kostenlose Konten können 1 hinzufügen · bei Team/Enterprise fügt ein Owner ihn hinzu

  1. Öffne die Connectors-Seite von Claude

    CustomizeConnectors

    CustomizeConnectors1Add2https://…3Add4
  2. Klicke „Add“ → „Custom“ → „Web“ und fülle diese 2 Felder aus

    Kopiere jeden Wert in das gleichnamige Feld in Claude und klicke Continue

    Name · NameFjc Case Outcomes
    Remote MCP server URL · Adressehttps://gateway.pipeworx.io/fjc-case-outcomes/mcp

    Klicke auf der von Claude erkannten Anmelde-Seite auf Continue · wähle bei Authentication, was der Anbieter angibt (Sign in now, Sign in when needed oder No sign in), dann Add

  3. Im Chat einschalten

    +ConnectorsFjc Case Outcomes

  4. Ausprobieren

    Nutze Fjc Case Outcomes und sag mir, was du für mich tun kannst; zeig mir dann eine Sache

    ✓ Wenn Claude sagt, dass es Fjc Case Outcomes nutzt, oder ein Werkzeug von Fjc Case Outcomes in der Antwort zeigt, bist du verbunden

Menünamen am 11. Nov. 2026 mit der Hilfe von Anthropic abgeglichen · dein Bildschirm kann je nach App-Version leicht abweichen

Klappt mit ChatGPT je nach Tarif

Volles MCP: ChatGPT Business, Enterprise oder Edu im Web · Pro: verbindet mit Lese-/Abrufrechten, Werkzeuge, die Daten ändern, gehen evtl. nicht · Plus: in der Doku nicht bestätigt; siehst du auf der Plugins-Seite eine Option für eigene MCP-Server, kannst du es versuchen · nur Web

  1. In ChatGPT im Web die Seite zum Hinzufügen von MCP öffnen

    Plugins+Add custom MCP server

    ChatGPTPlugins1+2https://…3Create4
  2. Name und Adresse eintragen

    Namen eingeben, Adresse unter Connection einfügen, Risikohinweis abhaken und Create as a plugin klicken

    Name · NameFjc Case Outcomes
    Connection · Adressehttps://gateway.pipeworx.io/fjc-case-outcomes/mcp
  3. Fjc Case Outcomes im Chat auswählen

    Neuen Chat öffnen und vor dem Tippen Fjc Case Outcomes aus deinen Plugins wählen

  4. Ausprobieren

    Nutze Fjc Case Outcomes und sag mir, was du für mich tun kannst; zeig mir dann eine Sache

    ✓ Wenn ChatGPT sagt, dass es Fjc Case Outcomes nutzt, oder ein Werkzeug von Fjc Case Outcomes in der Antwort zeigt, bist du verbunden

Menünamen am 11. Nov. 2026 mit der Hilfe von OpenAI abgeglichen · dein Bildschirm kann je nach App-Version leicht abweichen

Klappt mit Claude Code · etwa 2 Min.

Kein Schlüssel, nichts zu installieren

  1. Terminal öffnen

    Mac: Command+Leertaste drücken und Terminal tippen · Windows: PowerShell öffnen

  2. Diesen Befehl einfügen und Enter drücken

    claude mcp add --transport http --scope user fjc-case-outcomes https://gateway.pipeworx.io/fjc-case-outcomes/mcp
  3. /mcp in Claude Code eingeben

    Fjc Case Outcomes sollte in der Liste als verbunden erscheinen

  4. Ausprobieren

    Nutze Fjc Case Outcomes und sag mir, was du für mich tun kannst; zeig mir dann eine Sache

    ✓ Wenn Claude Code sagt, dass es Fjc Case Outcomes nutzt, oder ein Werkzeug von Fjc Case Outcomes in der Antwort zeigt, bist du verbunden

Menünamen am 11. Nov. 2026 mit der Hilfe von Anthropic abgeglichen · dein Bildschirm kann je nach App-Version leicht abweichen

Klappt mit Cursor · etwa 2 Min.

Kein Schlüssel, nichts zu installieren

  1. Mit diesem Button Cursor öffnen

    In Cursor öffnen

    Cursor fragt nach einer Bestätigung; klicke Install

  2. KI-Chat in Cursor im Agent-Modus öffnen

  3. Ausprobieren

    Nutze Fjc Case Outcomes und sag mir, was du für mich tun kannst; zeig mir dann eine Sache

    ✓ Wenn Cursor sagt, dass es Fjc Case Outcomes nutzt, oder ein Werkzeug von Fjc Case Outcomes in der Antwort zeigt, bist du verbunden

Menünamen am 11. Nov. 2026 mit der Hilfe von Cursor abgeglichen · dein Bildschirm kann je nach App-Version leicht abweichen

Klappt mit VS Code · etwa 2 Min.

Kein Schlüssel, nichts zu installieren

  1. Mit diesem Button VS Code öffnen

    In VS Code öffnen

    VS Code fragt nach einer Bestätigung; klicke Install

  2. KI-Chat in VS Code im Agent-Modus öffnen

  3. Ausprobieren

    Nutze Fjc Case Outcomes und sag mir, was du für mich tun kannst; zeig mir dann eine Sache

    ✓ Wenn VS Code sagt, dass es Fjc Case Outcomes nutzt, oder ein Werkzeug von Fjc Case Outcomes in der Antwort zeigt, bist du verbunden

Menünamen am 11. Nov. 2026 mit der Hilfe von VS Code abgeglichen · dein Bildschirm kann je nach App-Version leicht abweichen

Andere Apps mit MCP, etwa Windsurf, Zed oder Gemini CLI, fügen Server unterschiedlich hinzu. Sieh in der App-Liste nach

Alle Apps mit MCP ansehen →

Adresse für Apps, die über das Web verbinden

Adressehttps://gateway.pipeworx.io/fjc-case-outcomes/mcp

JSON-Einstellungen stehen unten unter „Für Entwickler“

Hängst du fest? Frag Leute, die Fjc Case Outcomes nutzen💬 Diskussion →
Für Entwickler: Terminal-Befehle und JSON-Einstellungen

Über das Web

Claude Code

claude mcp add --transport http --scope user fjc-case-outcomes https://gateway.pipeworx.io/fjc-case-outcomes/mcp

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "fjc-case-outcomes": {
      "url": "https://gateway.pipeworx.io/fjc-case-outcomes/mcp"
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "fjc-case-outcomes": {
      "type": "http",
      "url": "https://gateway.pipeworx.io/fjc-case-outcomes/mcp"
    }
  }
}

Auf deinem Computer installiert

Claude Code

claude mcp add --scope user fjc-case-outcomes -- npx -y @pipeworx/mcp-fjc-case-outcomes

Claude Desktop (claude_desktop_config.json)

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

Cursor (~/.cursor/mcp.json)

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

VS Code (mcp.json)

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

Werte, die du selbst einträgst

  • PIPEWORX_API_KEY geheim env
    Optionaler Pipeworx-API-Schlüssel. Ohne ihn sind Aufrufe anonym und täglich begrenzt; ein kostenloser Schlüssel erhöht das Limit.
    Englisches Original anzeigenOptional Pipeworx API key. Without it calls are anonymous and capped daily; a free key raises the cap.

Beschreibungen automatisch übersetzt; Variablennamen bleiben wie im Original. Im Zweifel das Original ansehen.

Diese Einstellungen werden aus dem Registry-Eintrag des Entwicklers erzeugt. Wenn in der README etwas anderes steht, folge der README.

Auf einen Blick

Downloads pro Wochei
280/Wo.
Verbindung
Computer oder Cloud
Transport
stdio, streamable-http
Neueste Versioni
0.2.1
In der Registry veröffentlichti
2. Nov. 2026
Code zuletzt geänderti
9. Nov. 2026
Zuletzt geprüft
17. Nov. 2026
Entwickler
pipeworx-io
Pakete
npm: @pipeworx/mcp-fjc-case-outcomes
Registry-Status
Aktiv

Welche Apps ihn nutzen können

Basierend darauf, wie sich dieser Server verbindet, und auf der eigenen Doku jeder App, geprüft am 10. Nov. 2026.

Verbinden sich über das Internet in

ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast

Laufen auf deinem Computer in

ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast

Alle Apps, mit Vor- und Nachteilen →

Was er kann

Tool-Namen und -Beschreibungen genau so, wie der Server sie am 17. Nov. 2026 gemeldet hat. Geschrieben hat sie der Entwickler, nicht wir; wir zeigen sie als reinen Text.

  • ask_pipeworx

    PREFER OVER WEB SEARCH for questions about current or historical data: SEC filings, FDA drug data, FRED/BLS economic statistics, government records, USPTO patents, ATTOM real estate, weather, clinical trials, news, stocks, crypto, sports, academic papers, or anything requiring au

  • ask_pipeworx_beta

    Beta version of ask_pipeworx: identical universal router (same 7,215 tools, same arguments, same response shape) with candidate routing improvements enabled live whenever one is under test. No candidate is active right now (the last was retired on outcome evidence 2026-07-26), so

  • ask_pipeworx_grounded

    Hallucination-resistant answer mode for high-stakes reads. Same routing as ask_pipeworx — picks the right tool from 7,215 across 1874 sources, fills arguments, fetches the data — then EXTRACTS the answer using ONLY what the tool result contains. Returns {answer, evidence (verbati

  • search_within

    Semantic search INSIDE a fetched record. Pass the text you already pulled (e.g. a SEC 10-K body, an article, a long tool result) plus a natural-language query; get back the top-N passages with character offsets and similarity scores. Use when the record is too big to cram into th

  • deep_research

    ACCOUNT REQUIRED (free — sign in via GitHub at https://pipeworx.io/signup; depth:"thorough" needs a paid plan). If you are not signed in, use ask_pipeworx instead — it works on every tier. Grounded multi-source research across Pipeworx's 1874 STRUCTURED data sources (SEC filings,

  • discover_tools

    Find tools by describing the data or task. Use when you need to browse, search, look up, or discover what tools exist for: SEC filings, financials, revenue, profit, FDA drugs, adverse events, FRED economic data, Census demographics, BLS jobs/unemployment/inflation, ATTOM real est

  • resolve_entity

    "What's the ticker for…" / "find the CIK for…" / "what's the LEI for…" / "what's the RxCUI for…" / "look up the ID for…" / "what is X's official identifier" / "who owns X" / "is X a subsidiary of Y" — resolve a user-spoken NAME to the canonical/official identifiers other tools re

  • compare_entities

    "Compare X and Y" / "X vs Y" / "X versus Y" / "which is bigger / better / larger / more profitable" / "rank these companies" / "head to head" — side-by-side comparison of 2–5 companies or drugs in ONE parallel call. ALWAYS PREFER over sequential single-pack lookups when comparing

  • subscribe

    Create a proactive monitoring subscription to a live-data event stream. Returns the new subscription id. Requires a Pipeworx OAuth account (anonymous + BYO cannot persist subscriptions). Supported types: "sec_8k" (8-K filings matching ticker + item codes — e.g. items:["5.02"] = o

  • unsubscribe

    Cancel a subscription by id. Ownership is enforced — you can only cancel your own subscriptions. The row is deactivated (not deleted) so its historical events stay available via recent_alerts.

  • list_subscriptions

    List the caller's active subscriptions. Returns id, type, params, created_at, last_fired_at, fire_count for each. Use this to review what you're monitoring before adding more or to find an id to cancel.

  • recent_alerts

    Pull fired events from your subscription feed. Returns the most recent alerts the evaluator has written to your persisted feed — each carries source, citation_uri (pipeworx:// when available), and the raw event payload. Filter by type (e.g. "sec_8k") and/or since (ISO timestamp).

  • entity_profile

    "Tell me about X" / "research Acme" / "brief me on Tesla" / "what does Apple do" / "company profile for Microsoft" / "give me the rundown on NVDA" / "everything you know about $TICKER" — full cross-source profile of a US public company in ONE parallel call. ALWAYS PREFER over cha

  • recent_changes

    "What's new with X" / "latest on Y" / "what happened to Z this week / month / quarter" / "updates on Acme" / "news on Tesla recently" / "what's happening with Apple" — change feed for a company in the last N days/weeks/months in ONE parallel call. Fans out to SEC EDGAR (filings s

  • validate_claim

    "Is it true that…" / "fact check" / "verify the claim that…" / "did X really…" / "was Y actually…" / "confirm or refute" / "true or false" — natural-language claim verification against authoritative sources. Use whenever the agent needs to check whether something a user said is f

  • company_facts

    TYPED, DETERMINISTIC financial facts for a US public company for an EXPLICITLY NAMED reporting period — "Apple revenue for fiscal 2023", "Walmart net income FY2026 Q3", "Microsoft cash at the end of fiscal 2024". PREFER OVER entity_profile / get_company_financials whenever the pe

  • company_register_search

    Search the NATIONAL BUSINESS REGISTERS by company name and get the register's own id back — a Companies House number, a Norwegian organisasjonsnummer, a Finnish business id, a SIREN, a Japanese corporate number, an Estonian registry code, a CNPJ, or an LEI. Use this when you want

  • scan_dependency

    Composite "should I add this npm package to my project" check in ONE call — fans out across deps.dev (license + advisories + version history) and bundlephobia (gzipped/minified bundle size, dependency count, ESM/tree-shake support). Use whenever an agent asks "is X safe / popular

  • bet_research

    Research a Polymarket bet by pulling the relevant Pipeworx data for it in one call. Pass a market slug ("will-kristi-noem-win-the-2028-republican-presidential-nomination"), a polymarket.com URL, or a question text. A dated slug ("...-by-june-30-2026") still resolves after it sett

  • polymarket_arbitrage

    Find arbitrage opportunities on Polymarket via monotonicity violations + partition-sum checks. Call with NO args for a `trending_scan` of the top ~200 markets by weekly volume; pass `event` for the strongest per-event partition_check, or `topic` for a themed cross-event scan. `ev

  • polymarket_edges

    Scan top Polymarket markets and return opportunities where Pipeworx data disagrees with market price. Built for "what should I bet on today" — agents discover opportunities without paging hundreds of markets. FIVE MODEL FAMILIES grouped into three response segments under by_segme

  • polymarket_kalshi_spread

    Cross-venue spread between Kalshi and Polymarket for the same resolving question. The two venues sometimes price the same outcome 2-25pp apart because their participant pools differ — when the bet shapes are equivalent that delta is a real signal, when they aren't the tool says s

  • polymarket_fill_risk

    Realizable-vs-theoretical edge check against live CLOB order-book depth — AND Polymarket's own taker fee, which is never zero and is folded in rather than left for you to add (fleet #3446: r/PredictionsMarkets flagged a "clean" fill that quietly omitted it as optimistic in the di

  • polymarket_edge_tracker

    Edge persistence and decay telemetry built from daily polymarket_edges snapshots. Answers "how long has this edge existed and is it shrinking?" — a fresh wide edge and a 3-week-old wide edge are different trades (the latter is wide for a reason nobody is willing to take). Args: d

  • kalshi_weather_edge

    Prices Kalshi daily high-temperature markets against the NWS forecast for the market's OWN settlement station, and measures whether that forecast actually beats the market. Two modes. LIVE (default): returns the full strike ladder for one city and settlement date with market_prob

  • resolution_audit

    Extract the settlement clause of a single Polymarket (.com or .us) or Kalshi market: who publishes the settling number (source), the clock time + timezone it is taken at (falling back to the market TITLE when the clause itself says "the time range specified in the title" — e.g. P

  • resolution_diff

    Field-by-field diff of TWO markets' settlement clauses (one from each of `a` and `b`; either can be Polymarket .com, Polymarket US, or Kalshi) — runs resolution_audit on both sides and compares source, settle time, precision, comparison_basis, and evidence standard. Returns `equi

  • release_calendar_markets

    JOIN of the official release calendar (econ data, the FOMC, FDA decisions, SEC rules) against LIVE Polymarket/Kalshi markets — which scheduled releases land in the next N hours, and which live markets resolve on them. This is a POSITIONING tool, not a speed product: results are c

  • prediction_calibration

    REALIZED win rate by shown price and minutes elapsed for short-horizon crypto up/down markets, net of taker fee — read from our own settled-outcomes archive, not from live prices. Answers the one question no venue will: "a side shown at 82 with five minutes left, how often did it

  • updown_venue_compare

    The same 15-minute crypto "up or down" window priced on polymarket.com, Polymarket US and Kalshi, side by side, with whether each pair is actually the same contract. Pass asset (btc | eth | sol | xrp | bnb) and window ("current" default, "next", "previous", or the window START as

  • updown_divergence_rate

    How often two venues settled the SAME 15-minute crypto window differently, over every settled window on record. Compares polymarket.com (Chainlink TWAP) with Kalshi and with Polymarket US (both CF Benchmarks BRTI), and Kalshi with Polymarket US as the same-feed control. Per pair:

  • archive_evidence

    What did a web page say on a given date? Finds the archived capture of a URL nearest that date across the Internet Archive Wayback Machine, Common Crawl and Arquivo.pt, reads it, and returns the readable text (HTML stripped) with the capture timestamp, a link to the archived copy

  • archive_compare

    What changed on a web page between two dates? Resolves the archived capture nearest each date (Internet Archive Wayback Machine, Common Crawl, Arquivo.pt), extracts the readable text of both, and returns a text-level diff: the segments removed and added, a similarity score, and b

  • research_row

    Claygent-style per-row research: answer ONE question about ONE company and return a JSON object matching your output_schema, with every field wrapped in its own evidence — {value, evidence_url, quote, status}. status is NEVER self-reported by the model: "found" means this code in

  • classify_row

    Cheap categorization: given a company and a list of candidate labels, decide which labels apply — the most common GTM/AI usage shape (tagging a list by industry, ICP fit, etc.), one small model call. Same evidence contract as research_row: each label comes back {label, applies, e

  • pipeworx_trending

    What other AI agents are calling on Pipeworx right now. Returns the top tools, top packs, and total call volume over a recent window (24h, 7d, or 30d). Useful for: (1) discovering what data sources are hot for current events, (2) confirming a popular tool is the canonical choice

  • suggest_questions

    What can I ask Pipeworx? / what is Pipeworx good for? / what can you do? / give me ideas / show me examples / getting started / what data do you have? — the onboarding entry point for an agent that just connected and wants to know what is worth asking. Returns category-bucketed e

  • generate_llms_txt

    Generate a production-ready llms.txt file for any URL so AI crawlers (ChatGPT, Claude, Perplexity) can index the site cleanly. Fetches the page, extracts title/description/key links, and emits the standard llms.txt markdown format. Output is a single text blob ready to drop at si

  • ai_visibility_check

    Probe one or more LLMs for what they know about a business / brand / product / topic and score visibility (0-100) per model. Default model is Workers AI Llama-3.3-70b (free); pass `_apiKey` to also probe Anthropic (BYO key — you pay Anthropic directly for those calls). Returns pe

  • scan_competitor_ai_presence

    Compare AI visibility across multiple entities side-by-side. Probes each entity (your brand + N competitors) with ai_visibility_check, ranks by score, surfaces which is most/least recognized. Useful for competitive AI-marketing audits: "does Claude know about us as well as our co

  • pipeworx_feedback

    Tell the Pipeworx team something is broken, missing, or needs to exist. Use when a tool returns wrong/stale data (bug), when a tool you wish existed isn't in the catalog (feature/data_gap), or when something worked surprisingly well (praise). ONLY for tools served by this Pipewor

  • remember

    Save data the agent will need to reuse later — across this conversation or across sessions. Use when you discover something worth carrying forward (a resolved ticker, a target address, a user preference, a research subject) so you don't have to look it up again. Stored as a key-v

  • recall

    Retrieve a value previously saved via remember, or list all saved keys (omit the key argument). Use to look up context the agent stored earlier — the user's target ticker, an address, prior research notes — without re-deriving it from scratch. Scoped to your identifier (anonymous

  • forget

    Delete a previously stored memory by key. Use when context is stale, the task is done, or you want to clear sensitive data the agent saved earlier. Pair with remember and recall.

  • 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 ci

  • 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 groupe

Basischecksi

Wir prüfen Informationen, die jeder sehen kann; den Code haben wir nicht gelesen. Checks, die nicht zutreffen, werden nicht mitgezählt. · Geprüft am 19. Nov. 2026

  • ✓ Bestanden

    Entwickler passt zum Repo

    Der Registry-Name wurde mit dem GitHub-Konto pipeworx-io bestätigt, dem das Repo gehört

  • ✓ Bestanden

    Wird noch gepflegt

    Code zuletzt geändert: vor 10 Tagen

  • ✓ Bestanden

    Hat eine Lizenz

    Nutzt MIT

  • ✓ Bestanden

    Endpunkt antwortet

    Antwort in 187 ms (HTTP 200)

  • – Nicht zutreffend

    Anmeldung mit OAuth

    Keine Anmeldung nötig

  • ✓ Bestanden

    Keine versteckten Anweisungen in Tool-Beschreibungen

    Wir haben 46 Tool-Beschreibungen gelesen und keine versteckten Anweisungen an die KI gefunden

Veröffentlichte Schwachstellen (OSV.dev)

Keine Einträge auf OSV.dev für @pipeworx/mcp-fjc-case-outcomes@0.2.1

Prüft nur diese Paketversion, nicht alle Abhängigkeiten · geprüft 15. Nov. 2026

Was wir prüfen → · JSON

Entwickler: neue Prüfung anfordern oder falsche Angaben melden
Für Anbieter: Badge ins README

Wenn du das gebaut hast, füge diesen Code in dein README ein. Das Badge verlinkt auf diese Seite.

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/pipeworx-io-fjc-case-outcomes.svg)](https://mcp.popnx.com/en/servers/pipeworx-io-fjc-case-outcomes)

Diskussion

Fragen, Tipps teilen oder melden, dass etwas nicht geht. Sortiert nach „hilfreich“.

Noch keine Beiträge. Stell die erste Frage oder teile einen Tipp.

Beiträge hier stammen von Nutzern, nicht vom PopNx-Team.

Anmelden, um zu posten

Nutzerbewertungen

Noch keine Bewertungen

Anmelden, um eine Bewertung zu schreiben

Im Vergleich mit anderen in Datenbanken & Datensätzei

  • Mehr Sterne als 0 % der anderen 1235 Server in dieser Kategorie
  • Neuer in der Registry veröffentlicht als 72 % der anderen 1235 Server in dieser Kategorie
  • Basischecks gleich gut wie oder besser als bei 99 % der anderen 1235 Server in dieser Kategorie

Verglichen mit allen aktiven Servern dieser Kategorie in der Registry. Sterne zählen nur, wenn dem Herausgeber das Repo gehört.

Häufige Fragen

Ist Fjc Case Outcomes sicher?

Er hat 5 von 5 zutreffenden Basischecks bestanden. Den Code haben wir nicht gelesen. Bevor du einen Schlüssel oder Token hinzufügst, sieh nach, welche Zugriffe der Server verlangt, und nutze einen Schlüssel, der nur die Berechtigungen hat, die du brauchst.

Welche Schlüssel oder Codes braucht er?

Die Registry nennt keinen erforderlichen Schlüssel, manche Server bitten dich aber bei der ersten Nutzung, dich anzumelden.

Läuft er auf meinem Computer oder in der Cloud?

Beides geht: Installiere ihn auf deinem Computer oder verbinde dich mit der Cloud-Version.

Wird er noch gepflegt?

Das GitHub-Repo wurde zuletzt vor 10 Tagen geändert, und die neueste Version (0.2.1) kam vor 17 Tagen in die Registry.

Welche Apps können ihn nutzen?

Apps, die MCP unterstützen, etwa Claude Desktop, Claude Code, Cursor und VS Code. Er verbindet sich per URL und funktioniert daher auch in Apps mit Remote-MCP, etwa ChatGPT im Web (volles MCP ab Business; Pro nur lesend).

Was kann ich stattdessen nutzen?

In derselben Kategorie: QueryWeaver, Supabase, Neon, DBCode, Keboola MCP

Ähnliche Alternativen

Gleiche Kategorie, andere Entwickler, Befehle bereits geprüft. Offizielle zuerst, dann nach Sternen.

So liest du eine Karte:↓ Downloads pro Wochei★ GitHub-SterneiDrei Säulen: Bewertungen · Checks · NutzungiAktualisiert = neueste Version in der Registry veröffentlichti

QueryWeaver

An MCP server for Text2SQL: transforms natural language into SQL using graph schema understanding.

von FalkorDBWachsend★ 1096Aktualisiert vor 14 Monaten

Läuft auf deinem Computer✓ falkordb.com

Supabase

MCP server for interacting with the Supabase platform

von supabaseWeit verbreitet↓ 245.530/Wo.★ 3018 Sterne des ganzen ReposAktualisiert gestern

Computer oder Cloud✓ vom Dienst · supabase.com

Neon

Official Neon MCP server for managing Neon projects and Lakebase Postgres databases.

von neondatabaseWachsend★ 666Aktualisiert vor 13 Tagen

Läuft in der Cloud✓ vom Dienst · neon.com

DBCode

Query and explore 100+ databases through your DBCode connections.

von dbcodeioAm Anfang↓ 118/Wo.★ 368 Sterne des ganzen ReposAktualisiert vor 2 Monaten

Läuft auf deinem Computer✓ vom Dienst · dbcode.io

Keboola MCP

Connect your AI assistants to Keboola and expose your data, transformations, SQL queries, ...

von keboolaWachsend↓ 1421/Wo.★ 84Aktualisiert vor 3 Tagen

Computer oder Cloud✓ vom Dienst · keboola.com
Im Vergleich mit ähnlichen
Dieser
Fjc Case Outcomes
QueryWeaverSupabaseNeonDBCodeKeboola MCP
Läuft woIn der Cloud oder auf deinem RechnerWird auf deinem Rechner installiertIn der Cloud oder auf deinem RechnerLäuft in der Cloud, keine InstallationWird auf deinem Rechner installiertIn der Cloud oder auf deinem Rechner
Braucht SchlüsselNeinNeinJaNeinNeinNein
Mit + in Claude hinzufügenNeinNeinJaJaNeinNein
Basisprüfungen5/53/35/55/52/35/5
LizenzMITAGPL-3.0Apache-2.0MITNOASSERTIONMIT
PreisKeine Kosten im RegisterKeine Kosten im RegisterKeine Kosten im RegisterKeine Kosten im RegisterKeine Kosten im RegisterKeine Kosten im Register

README vom Entwickler

README öffnen

Unverändert aus dem Repo des Entwicklers übernommen. PopNx MCP hat den Inhalt weder geprüft noch empfiehlt es ihn. HTML, Bilder und Skripte wurden entfernt. Links führen von dieser Website weg.

@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 1864+ 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 pg_total_relation_size:

TableTable sizeIndexesTotal
fjc_idb_civil44 MB21 MB65 MB
fjc_idb_criminal27 MB14 MB41 MB
fjc_idb_civil_summary1.4 MB1.6 MB2.9 MB
fjc_idb_criminal_summary0.7 MB0.9 MB1.6 MB
One fiscal year, total110 MB

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

Supabase (structured relational data, aggregation-heavy queries), not R2/FTS5 — this is tabular caseload statistics with GROUP BY-shaped questions (counts by district/year/nature-of-suit/disposition), not text search. Confirmed viable by the real-load sizing above, not assumed.

Three raw tables (fjc_idb_civil, fjc_idb_criminal, fjc_idb_appellate) carry only the fields the tools here actually use — no raw jsonb catch-all column (an earlier draft had one; dropped on review, since every byte paid for in a real Postgres table even when unused is exactly the cost this revision is supposed to be honest about).

Aggregates are PRECOMPUTED SUMMARY TABLES, not views. A plain GROUP BY view over the raw tables looked cheap in the first draft of this migration, but PostgREST runs under an ~8s statement_timeout, and the uspto-maintenance-fees pack (27.5M rows) timed out on every call under exactly that shape until count=exact and full scans were removed. fjc_idb_*_summary is built ONCE PER FISCAL-YEAR LOAD by scripts/ingest-fjc-idb.mjs (it has no direct SQL connection — only the same PostgREST credential every other pack's ingest uses — so the GROUP BY runs in Node over the already-parsed rows, not in SQL) and reinserted on every full-fiscal-year refresh. The aggregate tool reads ONLY these summary tables, never the raw per-case tables. See the migration's own header comment for the full design rationale.

Refresh

Full fiscal-year replace, not a row upsert — for both the raw table and its summary table. The IDB's own quarterly update model only revises records within a fiscal year still open for reporting (FJC Research Guide); once a year closes, its file stops changing. A scheduled refresh therefore only needs to re-pull the current (and, defensively, prior) fiscal year's files, delete every previously-loaded row for that (table, fiscal_year) — raw AND summary — and reinsert — scripts/ingest-fjc-idb.mjs --case-type all --years , . A full v1 backfill across FY2020-FY2024 is a separate, one-time run of the same script with a wider --years list. ANALYZE is not run from the script (no direct SQL access); Postgres autovacuum picks it up after a full-year replace touches the whole year's rows — the one-time initial backfill should have a human run a manual ANALYZE via psql as its last step rather than wait on it.

fjc-idb-refresh.yml is live at .github/workflows/fjc-idb-refresh.yml (applied by the config-applier, since .github/workflows/** is push-blocked) and has already run once successfully for the data load (run 39288114956); its smoke step is what will pass once tool-examples.json exists (see "Status" above).

Remaining before this fully ships

  1. Someone with the backing database's URL and service-role credential runs node scripts/add-pack.mjs fjc-case-outcomes --from 3 — this smoke-tests both tools for real against the loaded data, writes tool-examples.json FROM those calls, and carries through the rest of the add-pack checklist (npm-release-status confirmation, deliverable entry).
  2. Re-probe both tools through the live gateway after the next deploy.
  3. fleet_close on #3271 with the smoke_payloads / live_probes / etc. artifacts the task's acceptance checklist requires.

Tools

  • fjc_case_outcome_lookup(case_type, district_or_circuit, docket, fiscal_year?, defendant_number?) — one case's/defendant's outcome by docket number + district (or circuit for appellate).
  • fjc_case_outcomes_summary(case_type, fiscal_year?, district_or_circuit?, nature_of_suit_code?, offense_code?, disposition_code?, group_by?, limit?) — aggregate counts, total first, broken down by whichever dimensions are requested (nature of suit / offense code / disposition / year / district or circuit).

Data sources

  • Federal Judicial Center, Integrated Database — civil case, criminal defendant, bankruptcy and appellate case filings and terminations in the federal courts, reported quarterly by the Administrative Office of the U.S. Courts. US federal government data, public domain. Continuous back to 1970 (civil/criminal), 1971 (appellate). No query API — bulk files only; this pack mirrors a scoped year range into Supabase.

Traps

Per-year filename suffix is inconsistent and undocumented. cv23.sas7bdat (civil) needs no suffix; cr23_0.sas7bdat (criminal) does; ap23.sas7bdat (appellate) needs none. The ingest script probes both forms per year/case-type rather than hardcoding one pattern.

`pandas.read_sas` returns `NaT` for missing dates, which is NOT caught by a plain `isinstance(v, float) and math.isnan(v)` check and fails json.dumps with TypeError: Object of type NaTType is not JSON serializable — hit live on the civil file's TRANSDAT column (all-NaT for the vast majority of cases, which were never transferred to another district). Fixed by checking pd.isna(v) first, which covers None, float NaN, and NaT in one call.

Criminal defendant names are already redacted by the FJC itself (verified empirically: the NAME column is 100% null across all 218,853 FY2023 criminal rows), per 1995/2003 Judicial Conference policy — there is nothing to carry, so the criminal table has no name field at all. Civil party names (PLT/DEF) ARE populated and published; stored as-is.

Fiscal-year boundaries changed in 1992. Statistical years SY70-SY91 run July-June; FY1993 onward runs the federal government's October-September fiscal year; the 1992 file covers a 15-month transition span. A caller asking for "year 1991" and "year 1993" is asking about non-comparable 12-month windows unless this is accounted for — not yet surfaced in the tool responses; a documented gap for the promotion step to address.

Codes are raw FJC codes (nature of suit, disposition, offense, district, circuit), not yet labelled with human-readable names. See the migration header for why a crosswalk was not guessed at, and the planned follow-up (a small reference table sourced from the FJC's own published codebooks, e.g. https://www.fjc.gov/sites/default/files/idb/codebooks/).

`(fiscal_year, district, office, docket)` is NOT unique — found loading the real FY2023 civil file, not assumed. 293,677 rows resolve to only 290,139 distinct triples (~1.2% collide). The one pair inspected has the same disposition and nature-of-suit but a different filedate (2017 vs. 2023) — likely a reopened or renumbered proceeding; the IDB has no case-level version column to disambiguate. Criminal hit the same shape (collision even including defendant_number). The raw tables therefore have plain indexes, not unique constraints, on this tuple — the ingest script loads every row the FJC publishes rather than deduplicating, and fjc_case_outcome_lookup returns every matching row for a docket.

`fjc_case_outcomes_summary` requires `fiscal_year` and/or `district_or_circuit`. The summary tables are pre-aggregated but an unfiltered, multi-year query could still carry more distinct groups than PostgREST's row cap — a real FY2023-only measurement already has 26,067 distinct civil groups. The tool fetches the full matching set at the summary table's fine grain and re-aggregates client-side to whatever coarser group_by the caller asked for (PostgREST cannot re-GROUP BY a table via a plain select=); if the fetch hits the safety cap the response carries total_may_be_incomplete: true rather than a silently wrong total.

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{

"mcpServers": { "fjc-case-outcomes": { "url": "https://gateway.pipeworx.io/fjc-case-outcomes/mcp" } } }

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/fjc-case-outcomes/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — ask_pipeworx, discover_tools, search_within, remember/recall and the rest of the gateway-wide set

Nur der Anfang wird gezeigt; den Rest findest du im Repo