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

Court Listener

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

So installierst du es

What it does

CourtListener MCP — Free Law Project's CourtListener API (v4).

  • Connects Computer oder Cloud
  • Account or key No key needed
  • Category Recht & Behördendaten

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 Court Listener. Folge https://mcp.popnx.com/i/pipeworx-io-court-listener.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 · NameCourt Listener
    Remote MCP server URL · Adressehttps://gateway.pipeworx.io/court-listener/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

    +ConnectorsCourt Listener

  4. Ausprobieren

    Nutze Court Listener und sag mir, was du für mich tun kannst; zeig mir dann eine Sache

    ✓ Wenn Claude sagt, dass es Court Listener nutzt, oder ein Werkzeug von Court Listener 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 · NameCourt Listener
    Connection · Adressehttps://gateway.pipeworx.io/court-listener/mcp
  3. Court Listener im Chat auswählen

    Neuen Chat öffnen und vor dem Tippen Court Listener aus deinen Plugins wählen

  4. Ausprobieren

    Nutze Court Listener und sag mir, was du für mich tun kannst; zeig mir dann eine Sache

    ✓ Wenn ChatGPT sagt, dass es Court Listener nutzt, oder ein Werkzeug von Court Listener 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 court-listener https://gateway.pipeworx.io/court-listener/mcp
  3. /mcp in Claude Code eingeben

    Court Listener sollte in der Liste als verbunden erscheinen

  4. Ausprobieren

    Nutze Court Listener und sag mir, was du für mich tun kannst; zeig mir dann eine Sache

    ✓ Wenn Claude Code sagt, dass es Court Listener nutzt, oder ein Werkzeug von Court Listener 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 Court Listener und sag mir, was du für mich tun kannst; zeig mir dann eine Sache

    ✓ Wenn Cursor sagt, dass es Court Listener nutzt, oder ein Werkzeug von Court Listener 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 Court Listener und sag mir, was du für mich tun kannst; zeig mir dann eine Sache

    ✓ Wenn VS Code sagt, dass es Court Listener nutzt, oder ein Werkzeug von Court Listener 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/court-listener/mcp

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

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

Über das Web

Claude Code

claude mcp add --transport http --scope user court-listener https://gateway.pipeworx.io/court-listener/mcp

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "court-listener": {
      "url": "https://gateway.pipeworx.io/court-listener/mcp"
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "court-listener": {
      "type": "http",
      "url": "https://gateway.pipeworx.io/court-listener/mcp"
    }
  }
}

Auf deinem Computer installiert

Claude Code

claude mcp add --scope user court-listener -- npx -y @pipeworx/mcp-court-listener

Claude Desktop (claude_desktop_config.json)

{
  "mcpServers": {
    "court-listener": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-court-listener"
      ]
    }
  }
}

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "court-listener": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-court-listener"
      ]
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "court-listener": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-court-listener"
      ]
    }
  }
}

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
134/Wo.
Verbindung
Computer oder Cloud
Transport
stdio, streamable-http
Neueste Versioni
0.2.1
In der Registry veröffentlichti
31. Okt. 2026
Code zuletzt geänderti
9. Nov. 2026
Zuletzt geprüft
17. Nov. 2026
Entwickler
pipeworx-io
Pakete
npm: @pipeworx/mcp-court-listener
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,551 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,551 across 2011 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 2011 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 CRO number, a CNPJ, a US state entity n

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

  • search_opinions

    Search US court opinions from CourtListener — 8.3 million of them, with no API key and no rate limit. Covers the UNITED STATES SUPREME COURT (SCOTUS), the federal circuit courts of appeals, the federal district courts, and the state courts (71% of the corpus is state case law). T

  • court_listener_search_dockets

    Search US court dockets by keyword. Covers PACER and RECAP archives. Each result carries docket_id, case name, court, filing and termination dates, docket number, nature of suit, the cause of action, the assigned judge, and the PACER case id.

  • search_case_law

    Search the FULL TEXT of US court opinions by subject matter — "qualified immunity for police dogs", "securities fraud scienter pleading standard". Searches the full text of CourtListener opinions with no API key and no rate limit, and returns the most relevant opinion ids, a rele

  • find_case

    Find a US court case BY NAME and get its citations, filing date, judges and how often it has been cited. Searches 8.3 million opinions across 3,361 courts — no API key, no rate limit. Ranked by citation count, so the leading case for a name comes first. Use this when you know wha

  • lookup_citation

    Resolve a US reporter citation such as "410 U.S. 113" or "347 U.S. 483" to the case it refers to, with name, filing date, judges and citation count. No API key, no rate limit. Use when a brief, opinion or article cites a case by reporter and you need to know which case that is.

  • list_case_opinions

    List every opinion filed in one case (cluster) — majority, concurrences and dissents — with the opinion_id needed to read each one via get_opinion. No API key, no rate limit. Use after find_case or lookup_citation to get from a case to its readable text.

  • get_opinion

    Get the FULL TEXT of a US court opinion by its CourtListener opinion ID (the opinion_id returned by search_opinions). Covers 8.3 million opinions, 71% state case law — no API key needed. Returns the opinion text, the case name, the real filing date, author, citation count, whethe

  • list_docket_filings

    List the filings on a US FEDERAL district or bankruptcy court docket — every complaint, motion, order and exhibit RECAP has recorded for that case, in filing order, with the document id, entry number, filing date, page count and a link to the PDF. This is the docket sheet: what w

  • get_docket_filing

    Get one filing from a US federal court docket by its document id — the entry description as the clerk wrote it, the filing date, page count, the docket_id it belongs to, a text excerpt where the document has been scanned, and a direct PDF link. Use after list_docket_filings or se

  • search_court_filings

    Search the TEXT of US federal court filings — complaints, motions, briefs, orders and exhibits from PACER as archived in RECAP, roughly 9.7 million documents. Use this to find what was actually argued or ordered in litigation ("trade secret misappropriation", a company named as a

  • find_case_patents

    Patent litigation cross-reference: a named US district-court case to its docket, its asserted patent NUMBERS, and its defendants. Pass a case name (e.g. "TurboCode LLC v. Quectel Wireless Solutions") or a docket_id already known from search_dockets. Patent numbers come ONLY from

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 132 ms (HTTP 200)

  • – Nicht zutreffend

    Anmeldung mit OAuth

    Keine Anmeldung nötig

  • ✓ Bestanden

    Keine versteckten Anweisungen in Tool-Beschreibungen

    Wir haben 55 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-court-listener@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-court-listener.svg)](https://mcp.popnx.com/en/servers/pipeworx-io-court-listener)

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 Recht & Behördendateni

  • Mehr Sterne als 0 % der anderen 1951 Server in dieser Kategorie
  • Neuer in der Registry veröffentlicht als 61 % der anderen 1951 Server in dieser Kategorie
  • Basischecks gleich gut wie oder besser als bei 99 % der anderen 1951 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 Court Listener 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 19 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: Global law, Open Legal Data (Germany), LibreJustice, InfraNode, Fedlex Connector

Ä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

Global law

The law of nearly every country on earth, any date: read it, see what changed it, check citations.

von lexifinaWeit verbreitet★ 2105Aktualisiert vor 9 Tagen

Läuft in der Cloud✓ lexifina.com

LibreJustice

Search French-language and European case law and French legal texts (codes, statutes, treaties).

von librejusticeAm Anfang★ 36Aktualisiert vor 2 Monaten

Läuft in der Cloud✓ vom Dienst · librejustice.fr

InfraNode

Keyless open data for 84 German cities: 12 lean read-only MCP tools covering 67 data types.

von street1983nkAm Anfang★ 18Aktualisiert vor 5 Monaten

Läuft in der Cloud✓ vom Dienst · infranode.dev

Fedlex Connector

Search Swiss federal legislation: laws, articles, amendments via the Fedlex SPARQL endpoint.

von JayTheSkierAm Anfang★ 8Aktualisiert vor 7 Monaten

Läuft in der Cloud✓ vom Dienst · fedlex-connector.ch
Im Vergleich mit ähnlichen
Dieser
Court Listener
Global lawOpen Legal Data (Germany)LibreJusticeInfraNodeFedlex Connector
Läuft woIn der Cloud oder auf deinem RechnerLäuft in der Cloud, keine InstallationLäuft in der Cloud, keine InstallationLäuft in der Cloud, keine InstallationLäuft in der Cloud, keine InstallationLäuft in der Cloud, keine Installation
Braucht SchlüsselNeinNeinNeinNeinNeinNein
Mit + in Claude hinzufügenNeinNeinNeinNeinNeinNein
Basisprüfungen5/54/44/44/44/44/4
LizenzMITNOASSERTIONMITApache-2.0Apache-2.0MIT
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.

CourtListener — US case law

US court opinions from Free Law Project's CourtListener: 8.3 million opinions across 3,361 courts, going back to 1761. The largest free, structured database of American case law.

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

Most of it is state law. That surprises people, and it is the point:

OpinionsShare
State (supreme, appellate, trial)6,219,86971%
Federal (incl. SCOTUS 498,145)2,440,85628%
Territorial, military, tribal86,6911%

Federal appellate law is easy to find elsewhere. Six million state opinions, assembled and addressable, are not.

Auth

None for case lookup and opinion text — no key, no signup, no rate limit.

search_opinions and search_dockets search upstream by topic and are subject to CourtListener's throttling. A free token from Free Law Project lifts it.

find_case_patents optionally uses a USPTO Open Data Portal platform key (the same one the patents pack uses) to attach patent metadata — it returns the asserted patent numbers either way, just without titles/dates when no key is configured.

Tools

ToolUse it when
find_caseYou know what the case is called — "Roe v. Wade", or just "Sullivan"
lookup_citationYou have a reporter citation — "410 U.S. 113"
list_case_opinionsYou have a case and want its majority, concurrences and dissents
get_opinionYou have an opinion id and want the full text
search_opinionsCase search by name, judge or category (mirror-first; a specific court code searches live)
search_docketsDocket-level search, upstream
list_docket_filingsYou have a docket_id and want the docket sheet — what was filed, when
get_docket_filingYou have a document_id and want that one filing + its PDF
search_court_filingsYou want the text of filings — motions, briefs, orders — not opinions
find_case_patentsPatent case → its asserted patent numbers (with USPTO metadata) → its defendants, in one call

For litigation documents the path is search_dockets → list_docket_filings → get_docket_filing. Every filing tool is keyed by docket_id, and only search_dockets produces one — a PACER case number will not resolve.

find_case_patents — patent litigation cross-reference

Joins a RECAP docket (Free Law Project / CourtListener) to patent metadata (U.S. Patent and Trademark Office, Open Data Portal). Pass a case_name (optionally with court) or a docket_id already known from search_dockets:

{"case_name": "TurboCode LLC v. Quectel Wireless Solutions", "court": "txed"}

returns the docket, the plaintiff(s) and defendant(s) read off the case caption, and every patent number that appears in the docket's own filing text, each one naming the filing it was found in and the exact label that preceded it (e.g. "United States Patent No."). When a USPTO platform key is configured (the same PLATFORM_USPTO_KEY the patents pack uses), each number carries title, status, grant date and first inventor; without one the number is still returned, with metadata_unavailable_reason saying why.

Thin cross-reference, by design — this never buys a PACER document. Patent numbers come only from text RECAP already indexes: the clerk's own docket-entry descriptions (an exhibit filed as *"United States Patent No. 6,813,742"* reads straight off the entry, no purchase needed) and the text excerpt of any document someone else has already bought from PACER. A patent asserted only inside an unpurchased complaint PDF will not surface — the response says how many filings it scanned and that a pdf_available document was never fetched, rather than claiming completeness.

Extraction is conservative on purpose: a number only counts as an asserted patent when the literal word "Patent" immediately precedes "No./Nos./Number(s)" in the source text — a filing fee, a receipt number, a PageID or an attachment index sitting nearby never matches just because it is a number near a number. Defendants come from the case caption CourtListener indexed (not an authenticated PACER party table), split on ";" / " and " only — never a bare comma, since a corporate suffix ("Co., Ltd", "Inc.,") routinely contains one and splitting on it would cut a single defendant's name in two. An "et al." caption is reported as defendants_truncated: true rather than silently dropped.

Opinions and filings answer different questions: an opinion is what a court decided, a filing is what the parties filed.

search_opinions returns one cases shape whichever path served it (mirror or live), and the most-cited case inlines an excerpt of its lead opinion — the opening, its holding language, and the query match — so "what did the court hold" is answerable from the search result alone; get_opinion reads the full text.

The usual path is find_case → list_case_opinions → get_opinion. Results from find_case and lookup_citation are ranked by citation count, because among cases sharing a name the one later courts actually cite is nearly always the one being asked about — "roe wade" returns the 1973 Supreme Court decision (5,581 citations) ahead of the 1970 district case (53).

Abbreviated and copy-pasted case names

Name matching is AND over every token, so one token the corpus does not carry sinks the whole lookup. That used to mean find_case returned nothing for Bell Atl. Corp. v. Twombly — the corpus stores "Bell Atlantic Corp.", and atl does not stem to atlant — and nothing for a name pasted out of a brief with its scaffold attached (TABLE OF AUTHORITIES Bowers v. Hardwick).

When the name as given matches nothing, find_case now retries once with Bluebook abbreviations, citation scaffold and corporate suffixes dropped (never expanded or guessed — under AND semantics dropping a token can only widen). A result found that way is labelled:

{ "matched": "relaxed", "matched_query": "Bell v Twombly", "note": "…" }

Treat a matched: "relaxed" hit as a best-effort resolution of a messy citation and check the returned case_name is the case you meant. An exact match never carries the field, and a name that matches on the first pass still costs exactly one query.

Coverage

Keyless: opinion full text, case names, filing dates, judges, precedential status, citation counts, reporter citations.

Upstream, throttled: full-text *topic* search, and all three filing tools. Finding a case by topic can fail in a way that finding it by name or citation cannot.

RECAP filings (PACER documents) — keyless, via search only. ~9.7 million documents. The REST endpoints you would reach for, /recap-documents/ and /docket-entries/, both answer *"Authentication credentials were not provided"*; /search/?type=rd needs no token and is the path the filing tools use. Scoping goes through the q field query (q=docket_id:71886217) — passing ?docket_id= as a parameter is silently ignored and returns the whole 61.7M-document corpus rather than an error.

Caveats worth passing to a user

  • A filing without a PDF is still a real filing. RECAP holds docket *text* for far more entries than it holds documents, because a PDF only exists once somebody has paid PACER for it. Each filing reports pdf_available; on a typical docket most entries are metadata-only. Read a missing PDF as "nobody has bought this one", never as "this was not filed".
  • Filing tools spend a scarce budget. They go upstream to CourtListener's /search/, throttled to roughly 125 requests a day without a token — the same throttle the opinion mirror exists to avoid. There is no mirror for RECAP. When it is exhausted the tools say so explicitly rather than returning an empty docket; opinion tools are unaffected.
  • Recency. Responses carry a snapshot_date; opinions filed after it fall through to upstream search.
  • 14.2% of the corpus is OCR of scanned volumes and reads accordingly. Responses set extracted_by_ocr so garbled text is attributable to the scan rather than to us.
  • `date_created` is not a filing date. It is when the record entered CourtListener — a 1946 opinion can read 2020. date_filed, joined from the cluster, is when the court actually ruled.
  • Citation counts are within CourtListener's corpus, not a universal measure of importance.

Attribution

Data is CourtListener / Free Law Project, published under the Public Domain Mark. Free Law Project funds and maintains the corpus. If this pack is useful to you, https://free.law/donate/ is where that goes.

find_case_patents' patent metadata is the U.S. Patent and Trademark Office's Open Data Portal — a US government work, public domain.

Quick Start

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

{

"mcpServers": { "court-listener": { "url": "https://gateway.pipeworx.io/court-listener/mcp" } } }

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/court-listener/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. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:

{

"mcpServers": { "pipeworx": { "url": "https://gateway.pipeworx.io/mcp" } } }

Both URLs reach the same gateway and the same 1863+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

No MCP client? Call it over HTTP

curl -X POST https://gateway.pipeworx.io/v1/tools/search_opinions \

-H 'Content-Type: application/json' \ -d '{"query":"Air France v. Saks"}'

No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/search_opinions. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.

Run it from npm

@pipeworx/mcp-court-listener is a local stdio bridge to the Pipeworx gateway: your MCP client starts it with npx, and it forwards every call to the same https://gateway.pipeworx.io/court-listener/mcp endpoint shown above. It needs network access; there is no offline mode.

{

"mcpServers": { "court-listener": { "command": "npx", "args": ["-y", "@pipeworx/mcp-court-listener"] } } }

Without a key it calls anonymously, capped at 50 calls a day. A free account raises that to 200 a day: get a key at https://pipeworx.io/signup and add "env": { "PIPEWORX_API_KEY": " " } to the server entry. The key is sent as a Bearer token, the same way a hosted connection sends it, so calls are metered and billed exactly as they are there.

It

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