Prototipo · Versión preliminar: todos los servidores del registro oficial, sincronizados cada 30 minutos. Inicia sesión con Google para escribir reseñas.Prototipo · se actualiza cada 30 min
PopNx MCPServidores MCP para quienes usan IA · en palabras sencillas

Fjc Case Outcomes

de pipeworx-ioversión 0.2.1i★ 0iComputadora o nubeSitio oficial ↗
Nombre en el registroio.github.pipeworx-io/fjc-case-outcomes

Cómo instalar

What it does

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

  • Connects Computadora o nube
  • Account or key No key needed
  • Category Bases de datos y conjuntos de datos

Úsalo junto con

Skills que enseñan a la IA este tipo de trabajo; funcionan junto a este

timesfm

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

de google-research★ 35.6381 skills

Skill · Guía de trabajo

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…

de BigBodyCobain★ 11.6051 skills

Skill · Guía de trabajo

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

de gosom★ 82361 skills

Skill · Guía de trabajo

Por qué está en este puesto

Las listas se ordenan por una puntuación de uso (sobre 100) con estas partes

Popularidad0/80Estrellas de GitHub o descargas semanales: la mayor cuenta 60, la menor 20
Actualidad12/12Puntuación completa con una versión o cambio de código en 30 días
Sigue respondiendo8/8El endpoint en la nube respondió en la última revisión
Puntuación de uso20/100

Calidad: Pasó 5/5 revisiones básicas (se muestra, no ordena) · Impulso: Sin datos aún (Solo se usa en la pestaña En auge)

Instalación

Elige la app de IA que usas y copia la configuración.

Que tu IA lo instale con una frase

Instala Fjc Case Outcomes. Sigue https://mcp.popnx.com/i/pipeworx-io-fjc-case-outcomes.md, enséñame los comandos y espera mi OK antes de ejecutarlos.

Pégala en una IA que trabaje en tu equipo (como Claude Code o Cursor). Lee nuestros pasos, te muestra los comandos y espera tu OK. Sin clave ni registro. · Ver el texto completo que lee tu IA

Pasó 5/5 revisiones · Lo que preguntas pasa por el servidor del autor (gateway.pipeworx.io) · ✓ Comandos revisados el 14 nov 2026

Primero: ¿qué IA usas?

Elige tu app y los pasos aparecen abajo.

Funciona con Claude · unos 2 min

Sin clave y sin instalar nada · Configúralo una vez en claude.ai o en la app de escritorio y úsalo en el chat · las cuentas gratis pueden añadir 1 · en Team/Enterprise lo añade un Owner

  1. Abre la página Connectors de Claude

    CustomizeConnectors

    CustomizeConnectors1Add2https://…3Add4
  2. Pulsa “Add” → “Custom” → “Web” y completa estos 2 campos

    Copia cada valor al campo con el mismo nombre en Claude y pulsa Continue

    Name · NombreFjc Case Outcomes
    Remote MCP server URL · Direcciónhttps://gateway.pipeworx.io/fjc-case-outcomes/mcp

    Pulsa Continue en la pantalla de inicio de sesión que detectó Claude · en Authentication elige lo que indique el autor (Sign in now, Sign in when needed o No sign in) y pulsa Add

  3. Actívalo en un chat

    +ConnectorsFjc Case Outcomes

  4. Pruébalo

    Usa Fjc Case Outcomes y dime qué puedes hacer por mí; luego muéstrame una cosa

    ✓ Si Claude dice que está usando Fjc Case Outcomes o muestra una herramienta de Fjc Case Outcomes en la respuesta, ya está conectado

Nombres de menú comprobados con la ayuda de Anthropic el 11 nov 2026 · tu pantalla puede variar un poco según la versión

Funciona con ChatGPT según tu plan

MCP completo: ChatGPT Business, Enterprise o Edu en la web · Pro: conecta con permisos de lectura/obtención, así que las herramientas que cambian datos pueden no funcionar · Plus: no confirmado en la documentación; si ves una opción para añadir MCP propio en la página de plugins puedes probar · solo web

  1. Abre la página para añadir MCP en ChatGPT web

    Plugins+Add custom MCP server

    ChatGPTPlugins1+2https://…3Create4
  2. Escribe el nombre y la dirección

    Pon un nombre, pega la dirección en Connection, marca el aviso de riesgo y pulsa Create as a plugin

    Name · NombreFjc Case Outcomes
    Connection · Direcciónhttps://gateway.pipeworx.io/fjc-case-outcomes/mcp
  3. Elige Fjc Case Outcomes en un chat

    Abre un chat nuevo y elige Fjc Case Outcomes en tus plugins antes de escribir

  4. Pruébalo

    Usa Fjc Case Outcomes y dime qué puedes hacer por mí; luego muéstrame una cosa

    ✓ Si ChatGPT dice que está usando Fjc Case Outcomes o muestra una herramienta de Fjc Case Outcomes en la respuesta, ya está conectado

Nombres de menú comprobados con la ayuda de OpenAI el 11 nov 2026 · tu pantalla puede variar un poco según la versión

Funciona con Claude Code · unos 2 min

Sin clave y sin instalar nada

  1. Abre la Terminal

    Mac: pulsa Command+Espacio y escribe Terminal · Windows: abre PowerShell

  2. Pega este comando y pulsa Enter

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

    Deberías ver Fjc Case Outcomes en la lista como conectado

  4. Pruébalo

    Usa Fjc Case Outcomes y dime qué puedes hacer por mí; luego muéstrame una cosa

    ✓ Si Claude Code dice que está usando Fjc Case Outcomes o muestra una herramienta de Fjc Case Outcomes en la respuesta, ya está conectado

Nombres de menú comprobados con la ayuda de Anthropic el 11 nov 2026 · tu pantalla puede variar un poco según la versión

Funciona con Cursor · unos 2 min

Sin clave y sin instalar nada

  1. Pulsa este botón para abrir Cursor

    Abrir en Cursor

    Cursor te pedirá confirmar; pulsa Install

  2. Abre el chat de IA de Cursor en modo Agent

  3. Pruébalo

    Usa Fjc Case Outcomes y dime qué puedes hacer por mí; luego muéstrame una cosa

    ✓ Si Cursor dice que está usando Fjc Case Outcomes o muestra una herramienta de Fjc Case Outcomes en la respuesta, ya está conectado

Nombres de menú comprobados con la ayuda de Cursor el 11 nov 2026 · tu pantalla puede variar un poco según la versión

Funciona con VS Code · unos 2 min

Sin clave y sin instalar nada

  1. Pulsa este botón para abrir VS Code

    Abrir en VS Code

    VS Code te pedirá confirmar; pulsa Install

  2. Abre el chat de IA de VS Code en modo Agent

  3. Pruébalo

    Usa Fjc Case Outcomes y dime qué puedes hacer por mí; luego muéstrame una cosa

    ✓ Si VS Code dice que está usando Fjc Case Outcomes o muestra una herramienta de Fjc Case Outcomes en la respuesta, ya está conectado

Nombres de menú comprobados con la ayuda de VS Code el 11 nov 2026 · tu pantalla puede variar un poco según la versión

Otras apps que usan MCP, como Windsurf, Zed o Gemini CLI, añaden servidores de forma distinta. Míralo en la lista de apps

Ver todas las apps que usan MCP →

Dirección para apps que se conectan por la web

Direcciónhttps://gateway.pipeworx.io/fjc-case-outcomes/mcp

La configuración JSON está en “Para desarrolladores”, abajo

¿Te atascaste? Pregunta a quien usa Fjc Case Outcomes💬 Conversación →
Para desarrolladores: comandos de Terminal y configuración JSON

Por la 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"
    }
  }
}

Instalado en tu computadora

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"
      ]
    }
  }
}

Valores que debes completar

  • PIPEWORX_API_KEY secreto env
    Clave de API de Pipeworx opcional. Sin ella, las llamadas son anónimas y tienen un límite diario; una clave gratuita aumenta ese límite.
    Ver original en inglésOptional Pipeworx API key. Without it calls are anonymous and capped daily; a free key raises the cap.

Descripciones traducidas automáticamente; los nombres de variables quedan como en el original. Si dudas, mira el original.

Esta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.

De un vistazo

Descargas por semanai
280/sem
Conexión
Computadora o nube
Transporte
stdio, streamable-http
Última versióni
0.2.1
Publicado en el registroi
2 nov 2026
Último cambio de códigoi
9 nov 2026
Última revisión
17 nov 2026
Creador
pipeworx-io
Paquetes
npm: @pipeworx/mcp-fjc-case-outcomes
Sitio web
pipeworx.io
Estado en el registro
Activo

Qué apps pueden usarlo

Según cómo se conecta este servidor y la documentación de cada app, comprobado el 10 nov 2026.

Se conectan por internet en

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

Se ejecutan en tu computadora en

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

Todas las apps, con ventajas y desventajas →

Qué puede hacer

Nombres y descripciones de las herramientas tal como los informó el servidor el 17 nov 2026. Los escribió el creador, no nosotros; los mostramos como texto sin formato.

  • 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

Revisiones básicasi

Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 19 nov 2026

  • ✓ Superada

    El creador coincide con el repo

    El nombre en el registro se verificó con la cuenta de GitHub pipeworx-io, dueña del repo

  • ✓ Superada

    Sigue en mantenimiento

    Último cambio de código: hace 10 días

  • ✓ Superada

    Tiene licencia

    Usa MIT

  • ✓ Superada

    El endpoint responde

    Respondió en 187 ms (HTTP 200)

  • – No aplica

    Inicio de sesión con OAuth

    No hace falta iniciar sesión

  • ✓ Superada

    Sin instrucciones ocultas en las descripciones de herramientas

    Leímos 46 descripciones de herramientas y no encontramos instrucciones ocultas para la IA

Vulnerabilidades publicadas (OSV.dev)

Sin entradas en OSV.dev para @pipeworx/mcp-fjc-case-outcomes@0.2.1

Solo revisa esta versión del paquete, no todas sus dependencias · revisado 15 nov 2026

Qué revisamos → · JSON

Creadores: pedir otra revisión o avisar de un dato erróneo
Para autores: añade una insignia a tu README

Si lo creaste tú, pega este código en tu README. La insignia enlaza a esta página.

[![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)

Conversación

Pregunta, comparte un consejo o avisa de que no funciona. Ordenado por lo que la gente marcó como útil.

Aún no hay publicaciones. Sé la primera persona en preguntar o compartir.

Lo publicado aquí lo escriben usuarios, no el equipo de PopNx.

Inicia sesión para publicar

Reseñas de usuarios

Aún no hay reseñas

Inicia sesión para escribir una reseña

Comparado con otros en Bases de datos y conjuntos de datosi

  • Más estrellas que el 0% de los otros 1237 servidores de esta categoría
  • Publicado en el registro más recientemente que el 71% de los otros 1237 servidores de esta categoría
  • Revisiones básicas iguales o mejores que el 99% de los otros 1237 servidores de esta categoría

Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.

Preguntas frecuentes

¿Es seguro Fjc Case Outcomes?

Superó 5 de 5 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.

¿Qué claves o códigos necesita?

El registro no indica ninguna clave obligatoria, aunque algunos servidores te piden iniciar sesión la primera vez que los usas.

¿Se ejecuta en mi computadora o en la nube?

Funciona de las dos formas: instálalo en tu computadora o conéctate a la versión en la nube.

¿Sigue en mantenimiento?

El repo de GitHub cambió por última vez hace 10 días, y la última versión (0.2.1) llegó al registro hace 17 días.

¿Qué apps pueden usarlo?

Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. Se conecta por URL, así que también sirve en apps que aceptan MCP remoto, como ChatGPT en la web (MCP completo en Business y superiores; Pro solo lectura).

¿Qué puedo usar en su lugar?

En la misma categoría: QueryWeaver, Supabase, Neon, DBCode, Keboola MCP

Alternativas parecidas

Misma categoría, otros creadores, comandos ya revisados. Primero los oficiales, luego por estrellas.

Cómo leer una tarjeta:↓ Descargas por semanai★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi

QueryWeaver

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

de FalkorDBEn crecimiento★ 1,1 milActualizado hace 14 meses

Se ejecuta en tu computadora✓ falkordb.com

Supabase

MCP server for interacting with the Supabase platform

de supabaseMuy usado↓ 245,5 mil/sem★ 3 mil Estrellas de todo el repositorioActualizado ayer

Computadora o nube✓ del servicio · supabase.com

Neon

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

de neondatabaseEn crecimiento★ 666Actualizado hace 13 días

Se ejecuta en la nube✓ del servicio · neon.com

DBCode

Query and explore 100+ databases through your DBCode connections.

de dbcodeioInicial↓ 118/sem★ 368 Estrellas de todo el repositorioActualizado hace 2 meses

Se ejecuta en tu computadora✓ del servicio · dbcode.io

Keboola MCP

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

de keboolaEn crecimiento↓ 1,4 mil/sem★ 84Actualizado hace 3 días

Computadora o nube✓ del servicio · keboola.com
Comparado con otros parecidos
Este
Fjc Case Outcomes
QueryWeaverSupabaseNeonDBCodeKeboola MCP
Dónde se ejecutaEn la nube o instalado en tu equipoSe instala en tu equipoEn la nube o instalado en tu equipoFunciona en la nube, sin instalar nadaSe instala en tu equipoEn la nube o instalado en tu equipo
Necesita claveNoNoSíNoNoNo
Se añade con + en ClaudeNoNoSíSíNoNo
Revisiones básicas5/53/35/55/52/35/5
LicenciaMITAGPL-3.0Apache-2.0MITNOASSERTIONMIT
PrecioSin coste en el registroSin coste en el registroSin coste en el registroSin coste en el registroSin coste en el registroSin coste en el registro

README del creador

Abrir el README

Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.

@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

Solo se muestra el principio; lee el resto en el repo