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/orygnscode/opa-mcp-server/opa-mcpgit clone --depth 1 https://github.com/OrygnsCode/opa-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/mcp/orygnscode/opa-mcp-server/opa-mcp)<a href="https://agentmods.dev/mcp/orygnscode/opa-mcp-server/opa-mcp"><img src="https://agentmods.dev/badge/mcp/orygnscode/opa-mcp-server/opa-mcp.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
opa-mcp 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 4d 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
{
"opa-mcp": {
"command": "npx",
"args": [
"-y",
"@orygn/opa-mcp"
],
"env": {
"OPA_URL": "http://localhost:8181",
"OPA_TOKEN": "",
"OPA_BINARY": "opa",
"REGAL_BINARY": "regal",
"CONFTEST_BINARY": "conftest",
"OPA_MCP_ALLOWED_PATHS": "",
"GITHUB_TOKEN": ""
}
}
}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.
- 4d ago First seen · 18 lines scan A 2e3bfae971ac
opa-mcp is an MCP server published in the GitHub repository OrygnsCode/opa-mcp-server (7 stars, last pushed today), 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
greedy-token
MCP server "greedy-token" as configured in svasenkov/greedy-token. Launched with greedy-token-mcp. Needs 1 environment variable to run.
toolradar
MCP server for Toolradar — search, compare, and get pricing for 8,600+ software tools. Works with Claude Desktop, Claude Code, Cursor, and any MCP-compatible AI assistant. Runs locally from the toolradar-mcp npm package. Needs 1 environment variable to run.
qobrix-crm-mcp
MCP server "qobrix-crm-mcp" as configured in gca-ltd/qobrix-crm-mcp. Runs locally from the qobrix-crm-mcp npm package.
github-actions
GitHub Actions MCP — view runs, read logs, re-run jobs, and manage CI/CD. Runs locally from the mcp-server-github-actions npm package.
nightmarquee
Cinematic website prompts with live previews, inside your editor. MCP server for Claude Code, Claude Desktop and Cursor. Runs locally from the nightmarquee npm package.
page2ai-remote
MCP server "page2ai-remote", hosted remotely at page2ai-mcp-remote.vercel.app, as configured in igorsaevets/page2ai-mcp.