Remote MCP · Endpoint

CourtListener MCP server

No. CourtListener answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://courtlistener-mcp.vaquill.ai/mcp/

The last check completed an MCP handshake.

Registry name
io.github.Vaquill-AI/courtlistener-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
546 ms
Tools exposed
34 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
MCP for CourtListener: US federal and state opinions, dockets, judges, plus eCFR regulations.
Listing
From the official MCP registry (active).
Recent checks of CourtListener
CheckedResultHandshake
1 hour agoHandshake completed546 ms
1 day agoHandshake completed593 ms
2 days agoHandshake completed170 ms
3 days agoHandshake completed175 ms
4 days agoHandshake completed586 ms
5 days agoHandshake completed550 ms
6 days agoHandshake completed543 ms
9 days agoHandshake completed597 ms
11 days agoHandshake completed547 ms
14 days agoHandshake completed520 ms
16 days agoHandshake completed542 ms
18 days agoHandshake completed549 ms
20 days agoHandshake completed597 ms
22 days agoHandshake completed189 ms
24 days agoHandshake completed533 ms
26 days agoHandshake completed528 ms
27 days agoHandshake completed549 ms
29 days agoHandshake completed529 ms

The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 29 responding of 29.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with CourtListener and makes no claim about it beyond what these checks measured.