Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/cyanheads/courtlistener-mcp-serverWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/plugins/cyanheads/courtlistener-mcp-server/courtlistener-mcp-server)<a href="https://agentmods.dev/plugins/cyanheads/courtlistener-mcp-server/courtlistener-mcp-server"><img src="https://agentmods.dev/badge/plugins/cyanheads/courtlistener-mcp-server/courtlistener-mcp-server/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/plugins/cyanheads/courtlistener-mcp-server/courtlistener-mcp-server"><img src="https://agentmods.dev/badge/plugins/cyanheads/courtlistener-mcp-server/courtlistener-mcp-server.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
courtlistener-mcp-server scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"name": "courtlistener-mcp-server",
"version": "0.7.1",
"description": "Search and retrieve US court opinions, federal dockets, judge records, citation networks, and oral arguments from CourtListener's 9M+ opinion corpus via MCP. STDIO or Streamable HTTP.",
"author": {
"name": "cyanheads"
},
"homepage": "https://github.com/cyanheads/courtlistener-mcp-server#readme",
"repository": "https://github.com/cyanheads/courtlistener-mcp-server",
"license": "Apache-2.0",
"mcpServers": {
"courtlistener-mcp-server": {
"command": "npx",
"args": ["-y", "@cyanheads/courtlistener-mcp-server"],
"env": {
"MCP_TRANSPORT_TYPE": "stdio",
"COURTLISTENER_API_TOKEN": "your-api-token"
}
}
}
}
What it installs
The manifest is a name and a version. 32 skills, 1 MCP server travel with it, and installing the plugin installs all of them — 2,220 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill design-mcp-server A 62 tokens
- Skill add-tool A 35 tokens
- Skill api-context A 79 tokens
- Skill api-linter A 86 tokens
- Skill api-canvas A 85 tokens
- Skill api-errors A 54 tokens
- Skill api-testing A 46 tokens
- Skill field-test A 76 tokens
- Skill api-config A 43 tokens
- Skill api-telemetry A 85 tokens
- Skill maintenance A 75 tokens
- Skill orchestrations A 159 tokens
- Skill security-pass A 118 tokens
- Skill add-service A 38 tokens
- Skill add-test A 41 tokens
- Skill api-workers A 51 tokens
- Skill git-wrapup A 82 tokens
- Skill polish-docs-meta A 54 tokens
- Skill tool-defs-analysis A 177 tokens
- Skill add-app-tool A 41 tokens
- Skill add-resource A 32 tokens
- Skill release-and-publish A 112 tokens
- Skill report-issue-framework A 52 tokens
- Skill report-issue-local A 44 tokens
- Skill setup A 58 tokens
- Skill api-auth A 58 tokens
- Skill api-mirror A 68 tokens
- Skill add-prompt A 37 tokens
- Skill api-utils A 37 tokens
- Skill code-simplifier A 124 tokens
- Skill techniques A 79 tokens
- Skill api-services A 32 tokens
- MCP server courtlistener-mcp-server A not measured
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 12d ago First seen · 22 lines scan A fe8dc52c4821
courtlistener-mcp-server is a plugin published in the GitHub repository cyanheads/courtlistener-mcp-server (2 stars, last pushed 18d ago), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other plugins, from other repositories
librejustice
Free and open source, LibreJustice gives your agent 3.7 million French and European decisions and 3.6 million legal articles as they stood on any date: five MCP tools over OAuth, no API key, and two research skills.
eur-lex-mcp-server
Search EU legislation, CJEU case law, and treaties; traverse the CELLAR relationship graph; resolve EuroVoc concepts via MCP. STDIO or Streamable HTTP.
federal-court-rules
Look up and search federal procedural and evidence rules plus selected district local and ECF rules using a verified local corpus downloaded on first use.
fl-laws
Look up and search Florida Statutes, the Florida Constitution, and statewide Florida court rules using a verified local corpus downloaded on first use.
il-laws
Look up and search Illinois Compiled Statutes and Illinois Supreme Court Rules using a verified local corpus downloaded on first use.
in-laws
Look up and search the Indiana Code and Indiana Constitution using a verified local corpus downloaded on first use.