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/extensityai/ontoloom/claude-plugin-ontoloomgit clone --depth 1 https://github.com/ExtensityAI/ontoloomWrote 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/extensityai/ontoloom/claude-plugin-ontoloom)<a href="https://agentmods.dev/mcp/extensityai/ontoloom/claude-plugin-ontoloom"><img src="https://agentmods.dev/badge/mcp/extensityai/ontoloom/claude-plugin-ontoloom.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
ontoloom 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 5d 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
{
"ontoloom": {
"type": "stdio",
"command": "uv",
"args": [
"run",
"--project",
"packages/mcp",
"python",
"-m",
"ontoloom_mcp.server"
]
}
}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.
- 5d ago First seen · 14 lines scan A 33bcd26e2fcc
ontoloom is an MCP server published in the GitHub repository ExtensityAI/ontoloom (21 stars, last pushed 3mo ago), 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-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.
chrome-devtools
Lets the agent inspect and automate a live Chrome instance through the DevTools protocol: performance traces, network, console. Runs locally from the chrome-devtools-mcp npm package.
ontology-atlas
MCP server "ontology-atlas" as configured in wlsdks/ontology-atlas. Runs ./mcp/src/index.js with node. Needs 2 environment variables to run.
orders
MCP server "orders" as configured in gura105/operational-ontology. Launched with pnpm mcp. Needs 1 environment variable to run.
kontext_brain
MCP server "kontextbrain" as configured in hj1105/kontext-brain-ts. Runs ./server.mjs with node.