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/rinDBeans/onto-agentWrote 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/rindbeans/onto-agent/onto-agent)<a href="https://agentmods.dev/mcp/rindbeans/onto-agent/onto-agent"><img src="https://agentmods.dev/badge/mcp/rindbeans/onto-agent/onto-agent/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/rindbeans/onto-agent/onto-agent"><img src="https://agentmods.dev/badge/mcp/rindbeans/onto-agent/onto-agent.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket warn
Grade A, and why
onto-agent 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
{ "onto-agent": { "command": "uvx", "args": [ "onto-agent" ] } }
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 Changed · -1 lines 608b61416893
- 1mo ago First seen · 9 lines scan A 227bec9ba769
onto-agent is an MCP server published in the GitHub repository rinDBeans/onto-agent (0 stars, last pushed 1mo ago), licensed Apache-2.0. 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
codebase-memory-mcp
Codebase knowledge graph for AI agents — 159 languages, sub-ms queries, 99% fewer tokens. Runs locally from the codebase-memory-mcp npm package.
codestory
MCP server "codestory" as configured in TheGreenCedar/CodeStory. Runs ${workspaceFolder}/plugins/codestory/scripts/codestory-mcp.cjs with node. Needs 1 environment variable to run.
kivgraph
MCP server "kivgraph" as configured in Luqueee/kivgraph. Launched with https://github.com/Luqueee/kivgraph/releases/download/v0.9.9/kivgraph-linux-amd6.
thalamus
GNU Health Federation message and authentication server. Runs locally from the thalamus Python package.
astra-code-context
MCP server "astra-code-context" as configured in nimelkot/astra. Runs locally from the astra-code-context Python package.
codemesh
Intelligent code knowledge graph for AI coding agents — 71% cheaper, 72% faster. Runs locally from the @pyalwin/codemesh npm package. Needs 1 environment variable to run.