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/harariguy/agent-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/harariguy/agent-center/agent-center-app)<a href="https://agentmods.dev/mcp/harariguy/agent-center/agent-center-app"><img src="https://agentmods.dev/badge/mcp/harariguy/agent-center/agent-center-app/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/harariguy/agent-center/agent-center-app"><img src="https://agentmods.dev/badge/mcp/harariguy/agent-center/agent-center-app.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
agent-center-app 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 2mo 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
{ "agent-center-app": { "command": "uvx", "args": [ "agent-center-app" ] } }
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.
- 2mo ago First seen · 8 lines scan A 30657fb5e0dd
agent-center-app is an MCP server published in the GitHub repository harariguy/agent-center (4 stars, last pushed 2mo 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
agent-booster
MCP server "agent-booster" as configured in sseshachala/conductai. Launched with booster serve.
declaude
Rewrites Claude-English into plain English, preserving meaning, code and structure. Remote server at speak-english.tenken.co.
shadcn
Add components to your apps. Runs locally from the shadcn npm package.
livekit-docs
MCP server "livekit-docs", hosted remotely at docs.livekit.io, as configured in mahimailabs/voicegateway.
nebulamind
AI astronomy wiki with open agent peer-review. Vote on evidence, propose edits, earn reputation. Runs locally from the @kuntori/nebulamind-mcp npm package. Needs 1 environment variable to run.
tooldns
MCP server "tooldns" as configured in syedfahimdev/ToolsDNS. Runs locally from the tooldns Python package.