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/malkreide/swiss-courts-mcpWrote 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/mcp/malkreide/swiss-courts-mcp/swiss-courts)<a href="https://agentmods.dev/mcp/malkreide/swiss-courts-mcp/swiss-courts"><img src="https://agentmods.dev/badge/mcp/malkreide/swiss-courts-mcp/swiss-courts/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/mcp/malkreide/swiss-courts-mcp/swiss-courts"><img src="https://agentmods.dev/badge/mcp/malkreide/swiss-courts-mcp/swiss-courts.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
swiss-courts 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
{
"swiss-courts": {
"command": "python",
"args": [
"-m",
"swiss_courts_mcp"
]
}
}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 · 9 lines scan A 54ca7855a6a9
swiss-courts is an MCP server published in the GitHub repository malkreide/swiss-courts-mcp (1 stars, last pushed 11d ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. 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 mcp servers, from other repositories
canlii-mcp
MCP for CanLII: Canadian case law and legislation metadata (federal, provincial, territorial). Remote server at canlii-mcp.vaquill.ai.
courtlistener-mcp-server
Search US court opinions, federal dockets, judges, citations, and oral arguments via CourtListener. Runs locally from the @cyanheads/courtlistener-mcp-server npm package. Needs 2 environment variables to run.
lahend-mcp
Estonian court decisions: full-text case-law search, each ruling linked to its companies. Free. Remote server at lahend.ee.
librejustice
Search French and European case law and French legal texts (codes, statutes, treaties). Remote server at librejustice.fr.
librejustice
MCP server "librejustice", hosted remotely at librejustice.fr, as configured in librejustice/librejustice.
uk-legal-mcp
UK legal research MCP server — case law, legislation, parliament, bills, votes, committees, citations, HMRC. Runs locally from the uk-legal-mcp Python package.