mcpbeat Sign in

Courtlistener MCP Server

by courtlistener Your server? Claim it
answering

Courtlistener is answering right now. Last checked 1 min ago.

Uptime history 91 days of history · worst day 98%
91 days agonow
98.9%
Uptime 24h
91 of 92 checks
—
Tools
hidden behind auth
523 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Courtlistener does not always answer

Over the last week it answered 99.2% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 1 min ago.

run in your terminal
claude mcp add mcp --transport http https://mcp.courtlistener.com/
Settings → Connectors → Add custom connector, then paste this address
https://mcp.courtlistener.com/
~/.codex/config.toml
[mcp_servers.mcp]
url = "https://mcp.courtlistener.com/"
.cursor/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.courtlistener.com/"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "mcp": {
      "type": "http",
      "url": "https://mcp.courtlistener.com/"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://mcp.courtlistener.com/ streamable-http sign-in 568 ms 1 min ago

Alternatives to Courtlistener

same job, measured the same way
Court Listener
by pipeworx-io

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

551 installs/wk 55 tools answering
Courtroom5
by courtroom5
3 tools answering
Court Records MCP
by nexlab

Search US federal and state court records through CourtListener and the RECAP archive

answering
Courtlistener MCP
by mrfentmen

Keyless MCP server for CourtListener: search court opinions and federal dockets (RECAP), case...

146 installs/wk local only
Courtlistener MCP Server
by cyanheads

Search US court opinions, federal dockets, judges, citations, and oral arguments via CourtListener.

303 installs/wk 14 tools answering
Indiana Court Rules
by pipeworx-io

Indiana court rules.

700 installs/wk 47 tools answering
CourtListener
by vaquill-ai

MCP for CourtListener: US federal and state opinions, dockets, judges, plus eCFR regulations.

34 tools answering
Listenbrainz
by pipeworx-io

ListenBrainz MCP.

456 installs/wk 48 tools answering

Courtlistener — questions

Answers built from our own checks of this server.

Why is there no tool list for Courtlistener?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 98.9% of checks in the last 24 hours got a reply.
Is Courtlistener working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 92 checks got a reply (98.9%), average response time 523 ms. The bar chart above shows every period we have measured.
How do I connect Courtlistener?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to Courtlistener?
No API key is involved. Courtlistener answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is Courtlistener?
It answers our handshake in 523 ms on average, which is faster than 23% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.