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/gura105/operational-ontologyWrote 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/gura105/operational-ontology/orders)<a href="https://agentmods.dev/mcp/gura105/operational-ontology/orders"><img src="https://agentmods.dev/badge/mcp/gura105/operational-ontology/orders/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/gura105/operational-ontology/orders"><img src="https://agentmods.dev/badge/mcp/gura105/operational-ontology/orders.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
orders 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 10d 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
{
"orders": {
"command": "pnpm",
"args": [
"mcp"
],
"env": {
"OO_AGENT": "claude-code"
}
}
}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.
- 10d ago First seen · 11 lines scan A c804b75f9c3f
orders is an MCP server published in the GitHub repository gura105/operational-ontology (80 stars, last pushed 3d 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-30.
Other mcp servers, from other repositories
mykg
MCP server "mykg" as configured in SenolIsci/mykg. Launched with uv --directory /path/to/your/project run mykg mcp-serve.
chrome-devtools
MCP server "chrome-devtools" as configured in objectstack-ai/objectstack. Launched with chrome-devtools-mcp.
kontext_brain
MCP server "kontextbrain" as configured in hj1105/kontext-brain-ts. Runs ./server.mjs with node.
cruxible
MCP server "cruxible" as configured in cruxible-ai/cruxible. Launched with cruxible-mcp. Needs 1 environment variable to run.
2009scape-wiki
MCP server "2009scape-wiki" as configured in arsalan-anwari/2009scape-wiki-api. Runs locally from the . Python package. Needs 1 environment variable to run.
ontoloom
MCP server "ontoloom" as configured in ExtensityAI/ontoloom. Runs locally from the packages/mcp Python package.