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/StuMason/coolify-mcpWrote 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/stumason/coolify-mcp/coolify)<a href="https://agentmods.dev/mcp/stumason/coolify-mcp/coolify"><img src="https://agentmods.dev/badge/mcp/stumason/coolify-mcp/coolify/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/stumason/coolify-mcp/coolify"><img src="https://agentmods.dev/badge/mcp/stumason/coolify-mcp/coolify.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
coolify 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
{
"coolify": {
"command": "npx",
"args": [
"-y",
"@masonator/coolify-mcp"
],
"env": {
"COOLIFY_ACCESS_TOKEN": "",
"COOLIFY_BASE_URL": ""
}
}
}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 First seen · 13 lines scan A cf12984125c8
coolify is an MCP server published in the GitHub repository StuMason/coolify-mcp (611 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-30.
Other mcp servers, from other repositories
XcodeBuildMCP
XcodeBuildMCP provides tools for Xcode project management, simulator management, and app utilities. Runs locally from the xcodebuildmcp npm package. Needs 4 environment variables to run.
sentry
Sentry's hosted MCP server: lets the agent search and read issues, errors and traces. Remote server at mcp.sentry.dev.
graphpilot
Structural memory for coding agents: callers, callees, blast radius and symbols over MCP. Runs locally from the @graphpilot-oss/graphpilot npm package. Needs 1 environment variable to run.
wireshark
MCP server "wireshark" as configured in khuynh22/mcp-wireshark. Launched with mcp-wireshark.
debug-recorder-mcp
MCP server for recording debug sessions — query your debugging history with natural language. Runs locally from the debug-recorder-mcp npm package. Needs 1 environment variable to run.
codeindex
Structural code intelligence for AI coding agents over MCP: find a definition, read one function, see what calls a symbol, trace imports and judge a change's blast radius across 40+ languages — in tens of tokens instead of the 1,563 a file read costs. Runs locally from the @munhq/codeindex npm package.