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/delega-dev/delega-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/delega-dev/delega-mcp/delega)<a href="https://agentmods.dev/mcp/delega-dev/delega-mcp/delega"><img src="https://agentmods.dev/badge/mcp/delega-dev/delega-mcp/delega/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/delega-dev/delega-mcp/delega"><img src="https://agentmods.dev/badge/mcp/delega-dev/delega-mcp/delega.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
delega 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
{
"delega": {
"command": "npx",
"args": [
"-y",
"@delega-dev/mcp"
],
"env": {
"DELEGA_API_KEY": "",
"DELEGA_API_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 d0f5b49193b4
delega is an MCP server published in the GitHub repository delega-dev/delega-mcp (1 stars, last pushed 3d 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
plane
MCP server "plane", hosted remotely at mcp.plane.so, as configured in makeplane/plane-mcp-server.
connectwise-manage-mcp
MCP server "connectwise-manage-mcp" as configured in WYRE-AI/connectwise-manage-mcp. Runs in Docker (ghcr.io/wyre-ai/connectwise-manage-mcp:v1.9.0). Needs 8 environment variables to run.
microsoft-planner-mcp
MCP server "microsoft-planner-mcp", hosted remotely at localhost, as configured in aixolotl/microsoft-planner-mcp.
syncro-mcp
MCP server "syncro-mcp" as configured in WYRE-AI/syncro-mcp. Runs in Docker (ghcr.io/wyre-ai/syncro-mcp:v1.4.9). Needs 5 environment variables to run.
mcp-server
Project portfolio management for PMOs. Alternative to Microsoft Project Online. OAuth + PAT. Remote server at mcp.onplana.com.
onplana
MCP server "onplana", hosted remotely at mcp.onplana.com, as configured in Onplana/onplana-mcp-server.