Home / MCP registry index / io.github.cyanheads/courtlistener-mcp-server

io.github.cyanheads/courtlistener-mcp-server

io.github.cyanheads/courtlistener-mcp-server in the official MCP registry. Endpoint https://courtlistener.caseyjhand.com/mcp. Source: github.com/cyanheads/courtlistener-mcp-server.

The registry describes it as: Search US court opinions, federal dockets, judges, citations, and oral arguments via CourtListener.

We read its 14 tools on 2026-10-29. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http courtlistener-mcp-server https://courtlistener.caseyjhand.com/mcp

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "courtlistener-mcp-server": {
      "url": "https://courtlistener.caseyjhand.com/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"courtlistener-mcp-server","type":"http","url":"https://courtlistener.caseyjhand.com/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which. The free lazaretto-guard plugin reads a server's tools the moment Claude Code adds it and asks you if one of our rules matches.

Tools it advertises

courtlistener_search_opinions courtlistener_get_opinion courtlistener_get_citations courtlistener_lookup_citation courtlistener_search_dockets courtlistener_get_docket courtlistener_get_parties courtlistener_search_judges courtlistener_get_judge courtlistener_lookup_courts courtlistener_search_oral_arguments courtlistener_get_oral_argument courtlistener_search_financial_disclosures courtlistener_get_financial_disclosure

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-cyanheads-courtlistener-mcp-server/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-cyanheads-courtlistener-mcp-server)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.