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/Star4future/aceachievers-mcp-serverWrote 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/star4future/aceachievers-mcp-server/aceachievers-mcp)<a href="https://agentmods.dev/mcp/star4future/aceachievers-mcp-server/aceachievers-mcp"><img src="https://agentmods.dev/badge/mcp/star4future/aceachievers-mcp-server/aceachievers-mcp/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/star4future/aceachievers-mcp-server/aceachievers-mcp"><img src="https://agentmods.dev/badge/mcp/star4future/aceachievers-mcp-server/aceachievers-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
aceachievers-mcp 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 8d 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
{ "aceachievers-mcp": { "command": "uvx", "args": [ "aceachievers-mcp" ] } }
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.
- 8d ago First seen · 8 lines scan A 89bed16a7c85
aceachievers-mcp is an MCP server published in the GitHub repository Star4future/aceachievers-mcp-server (0 stars, last pushed 1mo 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
qa-mcp
QA-MCP: Test Standardization & Orchestration Server - MCP server for test case generation, quality control, and Xray integration. Runs locally from the qa-mcp Python package.
kafka-sentinel-mcp
Read-only Kafka observability MCP server: cluster health, consumer lag, and replay-readiness for AI agents that must never touch production. Runs locally from the kafka-sentinel-mcp Python package. Needs 6 environment variables to run.
kafka-sentinel
MCP server "kafka-sentinel" as configured in sanjay-amu/kafka-sentinel-mcp. Launched with kafka-sentinel-mcp. Needs 1 environment variable to run.
quotez
MCP server "quotez" as configured in PNX89/QUOTEZ. Runs locally from the quotez Python package.
linear-mcp-lean
Self-hosted MCP server wrapping Linear's GraphQL API with response-shape control — lean reads, minimal write acks, drop-in tool names. Runs locally from the linear-mcp-lean npm package.
desktop-mcp
Windows desktop-control MCP server: screenshot, window mgmt, mouse/keyboard input, and screen-recording. Config-gated tool groups (observe/window/input/record) -- input disabled by default. Local-only, single-machine. Runs locally from the desktop-mcp Python package.