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/AmadeusITGroup/otterWrote 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/amadeusitgroup/otter/o3r-local)<a href="https://agentmods.dev/mcp/amadeusitgroup/otter/o3r-local"><img src="https://agentmods.dev/badge/mcp/amadeusitgroup/otter/o3r-local/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/amadeusitgroup/otter/o3r-local"><img src="https://agentmods.dev/badge/mcp/amadeusitgroup/otter/o3r-local.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
o3r-local 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 yesterday.
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
{
"o3r-local": {
"command": "yarn",
"args": [
"node",
"./mcps/@o3r/mcp/dist/src/cli/index.js"
]
}
}What else mcp.json configures
This page is one entry in a file that holds 5. 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.
- yesterday First seen · 9 lines scan A f4b732b5aa5a
o3r-local is an MCP server published in the GitHub repository AmadeusITGroup/otter (58 stars, last pushed today), licensed BSD-3-Clause. 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-09-07.
Other mcp servers, from other repositories
angular-cli
CLI tool for Angular. Runs locally from the @angular/cli npm package.
performance_profiler
MCP server "performanceprofiler" as configured in probelabs/visor. Runs ./tools/performance-analyzer.js with node. Needs 2 environment variables to run.
code_analyzer
MCP server "codeanalyzer" as configured in probelabs/visor. Runs ./mcp/analyzer.py with python3. Needs 1 environment variable to run.
security_scanner
MCP server "securityscanner" as configured in probelabs/visor. Runs ./mcp/security.js with node. Needs 2 environment variables to run.
dependency_checker
Check for outdated, incorrect, and unused dependencies. Runs locally from the npm-check npm package. Needs 1 environment variable to run.
angular-cli
CLI tool for Angular. Runs locally from the @angular/cli npm package.