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.
npx agentmods add mcp/hellosverre/brreg-mcp/brreggit clone --depth 1 https://github.com/hellosverre/brreg-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/hellosverre/brreg-mcp/brreg)<a href="https://agentmods.dev/mcp/hellosverre/brreg-mcp/brreg"><img src="https://agentmods.dev/badge/mcp/hellosverre/brreg-mcp/brreg.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
brreg 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 3d 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
{
"brreg": {
"command": "npx",
"args": [
"-y",
"brreg-mcp"
],
"env": {}
}
}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.
- 3d ago First seen · 10 lines scan A 949d9f07093b
brreg is an MCP server published in the GitHub repository hellosverre/brreg-mcp (1 stars, last pushed 4mo 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
mcp-brreg
MCP server "mcp-brreg" as configured in DimaVasilenko-Intune/mcp-brreg. Runs locally from the mcp-brreg npm package.
taiwan-legal-db
MCP server "taiwan-legal-db" as configured in lawchat-oss/mcp-taiwan-legal-db. Runs mcp_server.server with .venv/bin/python.
nordic-registry-mcp-server
MCP server "nordic-registry-mcp-server" as configured in olgasafonova/nordic-registry-mcp-server. Runs in Docker (ghcr.io/olgasafonova/nordic-registry-mcp-server:1.0.2). Needs 2 environment variables to run.
mcp-sudact
Thin MCP client for Russian court practice (Sudact) hosted API: full-text case search + full decision text. Engine is hosted; this package only talks to the atomno-mcp backend. Runs locally from the atomno-mcp-sudact Python package. Needs 1 environment variable to run.
contract-review-ai-mcp
MCP server for contract review ai. Features analyze contract, extract clauses, identify risks. From MEOK AI Labs. Runs locally from the contract-review-ai-mcp Python package.
causallayer-mcp
Deterministic AI-liability attribution: signed, Bitcoin-anchored vendor/deployer/user fault split. Remote server at causallayer-mcp-demo.zykm9qkk7j.workers.dev.