Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Installing this writes the configuration, not the program: `node` runs a file from the repository, so clone it first and make the path in the command match where you put it.
Wrote 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/rohasnagpal/legal-ai-skills/legal-ai-skills-legal-research)<a href="https://agentmods.dev/mcp/rohasnagpal/legal-ai-skills/legal-ai-skills-legal-research"><img src="https://agentmods.dev/badge/mcp/rohasnagpal/legal-ai-skills/legal-ai-skills-legal-research/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/rohasnagpal/legal-ai-skills/legal-ai-skills-legal-research"><img src="https://agentmods.dev/badge/mcp/rohasnagpal/legal-ai-skills/legal-ai-skills-legal-research.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
legal-research 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 7d 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.
This is a copy
100% identical to legal-research — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{
"legal-research": {
"command": "node",
"args": [
"${CLAUDE_PLUGIN_ROOT}/mcp/legal-research-server.mjs"
],
"env": {
"REGULATIONS_GOV_API_KEY": "${REGULATIONS_GOV_API_KEY:-}"
}
}
}What else .mcp.json configures
This page is one entry in a file that holds 7. Installing the file brings all of them; each is measured and scanned on its own page.
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.
- 7d ago First seen · 11 lines scan A 2d97845f2508
legal-research is an MCP server published in the GitHub repository rohasnagpal/legal-ai-skills (183 stars, last pushed 6d 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. It is 100% identical to legal-research, differing in 0 lines, and is treated as a copy.
Other mcp servers, from other repositories
gb-eli-mcp
MCP server for UK legislation (legislation.gov.uk), case law (Find Case Law) and GOV.UK tribunal decisions, HMRC manuals and CMA cases — with persistent identifiers and verifiable citations. Runs locally from the gb-eli-mcp Python package.
hu-eli-mcp
MCP server for Hungarian national legislation (Nemzeti Jogszabalytar, njt.jog.gov.hu) — fetch legislation by native ELI with verifiable citations. Runs locally from the hu-eli-mcp Python package.
mozaia-laws-mcp
MCP server — programmatic access to the Mozambican law library (Mozaia). Runs locally from the mozaia-laws-mcp Python package.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.
component-explorer
MCP server "component-explorer" as configured in microsoft/vscode. Launched with npm exec --no -- component-explorer mcp -p ./test/componentFixtures/component-ex.
vscode-automation-mcp
MCP server "vscode-automation-mcp" as configured in microsoft/vscode. Launched with npm --prefix test/mcp run start-stdio.