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/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/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/orygnscode/opa-mcp-server/opa-mcp"><img src="https://agentmods.dev/badge/mcp/orygnscode/opa-mcp-server/opa-mcp.svg" alt="Reviewed on agentmods" width="80" 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 1mo 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.
- 1mo ago First seen · 18 lines scan A 2e3bfae971ac
opa-mcp is an MCP server published in the GitHub repository OrygnsCode/opa-mcp-server (8 stars, last pushed 14d 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
chrome-mcp-server
MCP server "chrome-mcp-server", hosted remotely at 127.0.0.1, as configured in iloveitaly/llm-ide-rules.
context7
Context7's hosted MCP server: up-to-date library documentation and code examples on demand. Remote server at mcp.context7.com.
stripe
Stripe's hosted MCP server: lets the agent work with customers, products, prices and payment links. Remote server at mcp.stripe.com.
greedy-token
MCP server "greedy-token" as configured in svasenkov/greedy-token. Launched with greedy-token-mcp. Needs 1 environment variable to run.
github
Lets the agent work with GitHub: search code, read and create issues and pull requests, and manage repositories through the GitHub API. Runs locally from the @modelcontextprotocol/server-github npm package.
chronicle-mcp
Local MCP server to sync, clean, and index AI chat logs locally. Saves up to 40% context tokens. Runs locally from the chronicle-mcp-server Python package.