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/SkiTemplar/ultron-control-centerWrote 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/skitemplar/ultron-control-center/ultron)<a href="https://agentmods.dev/mcp/skitemplar/ultron-control-center/ultron"><img src="https://agentmods.dev/badge/mcp/skitemplar/ultron-control-center/ultron/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/skitemplar/ultron-control-center/ultron"><img src="https://agentmods.dev/badge/mcp/skitemplar/ultron-control-center/ultron.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
ultron 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 9d 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
{ "ultron": { "command": "uvx", "args": [ "ultron" ] } }
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.
- 9d ago First seen · 8 lines scan A 36500c029016
ultron is an MCP server published in the GitHub repository SkiTemplar/ultron-control-center (1 stars, last pushed 2d 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
mcp-automem
Graph-vector memory for AI assistants using FalkorDB and Qdrant. Runs locally from the @verygoodplugins/mcp-automem npm package.
memory
MCP server for AutoMem: AI memory storage and recall. Runs locally from the @verygoodplugins/mcp-automem npm package.
gossipcat
Multi-agent orchestration for Claude Code — consensus review, adaptive dispatch, skill learning. Runs locally from the gossipcat npm package. Needs 2 environment variables to run.
agentic-task-system
MCP server giving AI agents persistent task memory across TickTick, Notion, GitHub, Linear & Beads. Runs locally from the @reneza/ats-mcp npm package. Needs 1 environment variable to run.
memory
MCP server "memory" as configured in 4DA-Systems/4DA. Runs ./mcp-memory-server/dist/index.js with node. Needs 1 environment variable to run.
bikky
Shared memory for AI coding sessions — MCP server + background daemon. Runs locally from the bikky npm package.