プロトタイプ · プレビュー版:公式レジストリのすべてのサーバーを掲載し、30分ごとに同期しています。Google でログインするとレビューを書けます。プロトタイプ · 30分ごとに更新
PopNx MCPAIを使う人のためのMCPサーバー · やさしい言葉で解説

Court Listener

作者:pipeworx-ioバージョン 0.2.1i★ 0iパソコンでもクラウドでも公式サイト ↗
レジストリ名io.github.pipeworx-io/court-listener

インストール方法

What it does

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

  • Connects パソコンでもクラウドでも
  • Account or key No key needed
  • Category 法律・行政データ

この順位の理由

一覧は利用スコア(100 点満点)で並びます。内訳は次のとおり

人気0/80GitHub スターか週間ダウンロード数。大きい方を 60、小さい方を 20 で数えます
新しさ12/1230 日以内のリリースかコード更新で満点
応答中8/8前回の確認でクラウドのエンドポイントが応答
利用スコア20/100

品質: 基本チェック 5/5 項目に合格(表示のみ、並び順には不使用) · 勢い: データなし (「急上昇」タブでのみ使用)

インストール

使っているAIアプリを選んで、設定をコピーしてください。

ひとことで AI にインストールしてもらう

Court Listener をインストールして。https://mcp.popnx.com/i/pipeworx-io-court-listener.md に従い、コマンドを見せて、私が OK するまで実行しないで。

パソコンで作業できる AI(Claude Code や Cursor など)に貼り付けます。手順を読み、コマンドを見せて、あなたの OK を待ちます。キー不要・登録不要。 · AI が読む全文を見る

チェック 5/5 合格 · 質問内容は提供元のサーバー(gateway.pipeworx.io)を通ります · ✓ コマンド確認済み 2026年11月14日

まず:どの AI を使っていますか?

使っているアプリを選ぶと、下に手順が表示されます。

Claude につなげます · 約 2 分

キー不要、インストール不要 · claude.ai かデスクトップアプリで一度設定すれば、チャットで使えます · 無料アカウントは 1 つまで · Team/Enterprise はオーナー(Owner)が追加

  1. Claude の Connectors ページを開く

    CustomizeConnectors

    CustomizeConnectors1Add2https://…3Add4
  2. 「Add」→「Custom」→「Web」を押し、この 2 つを入力

    ここからコピーして Claude の同じ名前の欄に貼り付け、Continue を押します

    Name · 名前Court Listener
    Remote MCP server URL · アドレスhttps://gateway.pipeworx.io/court-listener/mcp

    Claude が検出したサインイン設定の画面で Continue を押す · Authentication は作者の説明どおり(Sign in now・Sign in when needed・No sign in)を選び Add を押します

  3. チャットで有効にする

    +ConnectorsCourt Listener

  4. 試してみる

    Court Listener を使って、私に何ができるか教えて、1 つやってみせて

    ✓ Claude が Court Listener を使っていると言うか、回答に Court Listener のツール名が出れば接続成功です

メニュー名は 2026年11月11日 に Anthropic のヘルプページで確認 · アプリのバージョンにより画面が少し違うことがあります

ChatGPT との接続はプランしだい

フル MCP:Web 版 ChatGPT の Business・Enterprise・Edu · Pro:読み取り/取得の権限で接続、データを変えるツールは使えないことがあります · Plus:公式ドキュメントで未確認。プラグイン画面にカスタム MCP を追加する項目があれば試せます · Web のみ

  1. Web 版 ChatGPT で MCP の追加ページを開く

    Plugins+Add custom MCP server

    ChatGPTPlugins1+2https://…3Create4
  2. 名前とアドレスを入力

    名前を入れ、Connection にアドレスを貼り付け、注意事項にチェックして Create as a plugin を押します

    Name · 名前Court Listener
    Connection · アドレスhttps://gateway.pipeworx.io/court-listener/mcp
  3. チャットで Court Listener を選ぶ

    新しいチャットを開き、入力前にプラグインの一覧から Court Listener を選びます

  4. 試してみる

    Court Listener を使って、私に何ができるか教えて、1 つやってみせて

    ✓ ChatGPT が Court Listener を使っていると言うか、回答に Court Listener のツール名が出れば接続成功です

メニュー名は 2026年11月11日 に OpenAI のヘルプページで確認 · アプリのバージョンにより画面が少し違うことがあります

Claude Code につなげます · 約 2 分

キー不要、インストール不要

  1. ターミナルを開く

    Mac:Command+スペースで Terminal と入力 · Windows:PowerShell を開く

  2. このコマンドを貼り付けて Enter

    claude mcp add --transport http --scope user court-listener https://gateway.pipeworx.io/court-listener/mcp
  3. Claude Code で /mcp と入力

    Court Listener が一覧にあり、接続済みと表示されれば OK です

  4. 試してみる

    Court Listener を使って、私に何ができるか教えて、1 つやってみせて

    ✓ Claude Code が Court Listener を使っていると言うか、回答に Court Listener のツール名が出れば接続成功です

メニュー名は 2026年11月11日 に Anthropic のヘルプページで確認 · アプリのバージョンにより画面が少し違うことがあります

Cursor につなげます · 約 2 分

キー不要、インストール不要

  1. このボタンで Cursor を開く

    Cursor で開く

    Cursor がインストールの確認をするので Install を押します

  2. Cursor の AI チャットを Agent モードで開く

  3. 試してみる

    Court Listener を使って、私に何ができるか教えて、1 つやってみせて

    ✓ Cursor が Court Listener を使っていると言うか、回答に Court Listener のツール名が出れば接続成功です

メニュー名は 2026年11月11日 に Cursor のヘルプページで確認 · アプリのバージョンにより画面が少し違うことがあります

VS Code につなげます · 約 2 分

キー不要、インストール不要

  1. このボタンで VS Code を開く

    VS Code で開く

    VS Code がインストールの確認をするので Install を押します

  2. VS Code の AI チャットを Agent モードで開く

  3. 試してみる

    Court Listener を使って、私に何ができるか教えて、1 つやってみせて

    ✓ VS Code が Court Listener を使っていると言うか、回答に Court Listener のツール名が出れば接続成功です

メニュー名は 2026年11月11日 に VS Code のヘルプページで確認 · アプリのバージョンにより画面が少し違うことがあります

Windsurf、Zed、Gemini CLI など MCP を使える他のアプリは追加方法がそれぞれ違います。アプリ一覧で確認してください

MCP を使えるアプリをすべて見る →

Web 経由でつなぐアプリ用のアドレス

アドレスhttps://gateway.pipeworx.io/court-listener/mcp

JSON 設定は下の「開発者向け」にあります

つまずいたら?Court Listener を使っている人に聞いてみましょう💬 ディスカッション →
開発者向け:ターミナルのコマンドと JSON 設定

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

パソコンにインストール

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

自分で入力する値

  • PIPEWORX_API_KEY 秘密 env
    任意の Pipeworx API キー。ない場合、呼び出しは匿名となり 1 日の上限があります。無料のキーで上限が引き上げられます。
    英語の原文を見るOptional Pipeworx API key. Without it calls are anonymous and capped daily; a free key raises the cap.

説明は自動翻訳です。変数名は原文のままです。迷ったら原文を確認してください。

この設定は、作者のレジストリ登録情報から作成しています。READMEと違う場合は、READMEに従ってください。

ひと目でわかる

週あたりのダウンロードi
134/週
接続方法
パソコンでもクラウドでも
最新バージョンi
0.2.1
レジストリ公開日i
2026年10月31日
コードの最終更新i
2026年11月9日
最終確認
2026年11月17日
作者
pipeworx-io
パッケージ
npm: @pipeworx/mcp-court-listener
ウェブサイト
pipeworx.io
レジストリでの状態
有効

使えるアプリ

このサーバーのつなぎ方と、各アプリの公式ドキュメントに基づきます。2026年11月10日に確認。

インターネット経由でつなげるアプリ

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

パソコン上で動かせるアプリ

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

すべてのアプリと長所・短所 →

できること

ツールの名前と説明は、サーバーが2026年11月17日に返したそのままの内容です。書いたのは作者で、私たちではありません。プレーンテキストとして表示しています。

  • 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

基本チェックi

誰でも見られる情報をチェックしており、コードは読んでいません。当てはまらない項目は数に入れていません。 · 2026年11月20日にチェック

  • ✓ 合格

    作者とリポジトリが一致

    レジストリ名は、リポジトリを所有するGitHubアカウント pipeworx-io で確認済みです

  • ✓ 合格

    今もメンテナンスされている

    コードの最終更新:11 日前

  • ✓ 合格

    ライセンスがある

    MITを使用

  • ✓ 合格

    エンドポイントが応答する

    132ミリ秒で応答(HTTP 200)

  • – 対象外

    OAuthでサインイン

    サインイン不要

  • ✓ 合格

    ツールの説明に隠れた指示がない

    55件のツールの説明を読み、AIへの隠れた指示は見つかりませんでした

公開済みの脆弱性(OSV.dev)

OSV.dev に @pipeworx/mcp-court-listener@0.2.1 の登録はありません

このバージョンのパッケージ本体のみ確認。すべての依存関係ではありません · 確認日 2026年11月15日

確認していること → · JSON

作者の方へ:再確認の依頼・情報の誤りの報告
作者向け:README にバッジを付ける

作者の方は、このコードを README に貼れます。バッジはこのページにリンクします。

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

話し合い

質問、コツの共有、使えないことの報告ができます。「役に立った」の多い順です。

まだ投稿はありません。最初の質問や共有をどうぞ。

ここの投稿は利用者によるもので、PopNx チームのものではありません。

ログインして投稿

ユーザーレビュー

まだレビューはありません

ログインしてレビューを書く

法律・行政データのほかのサーバーとの比較i

  • このカテゴリのほかの1957件のうち0%よりスターが多い
  • このカテゴリのほかの1957件のうち61%より最近レジストリに公開
  • 基本チェックの結果が、このカテゴリのほかの1957件のうち99%と同じかそれ以上

レジストリでこのカテゴリにある有効なすべてのサーバーと比較しています。スターは、公開者がリポジトリの所有者である場合だけ数えます。

よくある質問

Court Listenerは安全ですか?

当てはまる基本チェック5項目のうち5項目に合格しました。コードは読んでいません。キーやトークンを追加する前に、サーバーがどんなアクセスを求めているかを確認し、必要な権限だけを持つキーを使ってください。

どんなキーやコードが必要ですか?

レジストリには必須のキーは載っていません。ただし、最初に使うときにサインインを求めるサーバーもあります。

パソコンで動きますか、それともクラウドですか?

どちらでも使えます。パソコンにインストールしても、クラウド版につないでもかまいません。

今もメンテナンスされていますか?

GitHubリポジトリの最終更新は11 日前、最新バージョン(0.2.1)がレジストリに届いたのは20 日前です。

どのアプリで使えますか?

Claude Desktop、Claude Code、Cursor、VS CodeなどのMCP対応アプリで使えます。URL で接続するので、リモート MCP を受け付けるアプリでも使えます。例:Web 版 ChatGPT(Business 以上はフル MCP、Pro は読み取りのみ)。

代わりに使えるものは?

同じカテゴリには:Global law, Open Legal Data (Germany), LibreJustice, InfraNode, Fedlex Connector

似た働きのほかの候補

同じカテゴリでほかの作者のもの。コマンドは確認済み。公式を先に、次にスター順。

カードの見方:↓ 週あたりのダウンロードi★ GitHubスターi3つの柱:レビュー · チェック · 利用状況i更新=最新バージョンをレジストリに公開した日i

Global law

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

作者:lexifina広く使われている★ 210510 日前更新

クラウドで動く✓ lexifina.com

LibreJustice

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

作者:librejustice初期★ 382 か月前更新

クラウドで動く✓ 提供元 · librejustice.fr

InfraNode

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

作者:street1983nk初期★ 185 か月前更新

クラウドで動く✓ 提供元 · infranode.dev
似たものと比べる
これ
Court Listener
Global lawOpen Legal Data (Germany)LibreJusticeInfraNodeFedlex Connector
動く場所クラウドでもパソコンにインストールでも使えるクラウドで動き、インストール不要クラウドで動き、インストール不要クラウドで動き、インストール不要クラウドで動き、インストール不要クラウドで動き、インストール不要
キーが必要いいえいいえいいえいいえいいえいいえ
Claude で + から追加いいえいいえいいえいいえいいえいいえ
基本チェック5/54/44/44/44/44/4
ライセンスMITNOASSERTIONMITApache-2.0Apache-2.0MIT
料金登録情報に費用の記載なし登録情報に費用の記載なし登録情報に費用の記載なし登録情報に費用の記載なし登録情報に費用の記載なし登録情報に費用の記載なし

作者のREADME

READMEを開く

作者のリポジトリから書かれたとおりにコピーしたものです。PopNx MCPは内容を確認・推奨していません。HTML、画像、スクリプトは取り除いています。リンクはこのサイトの外へ移動します。

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

冒頭だけを表示しています。続きはリポジトリで読めます