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/WYRE-AI/autotask-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/wyre-ai/autotask-mcp/task-master-ai)<a href="https://agentmods.dev/mcp/wyre-ai/autotask-mcp/task-master-ai"><img src="https://agentmods.dev/badge/mcp/wyre-ai/autotask-mcp/task-master-ai/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/wyre-ai/autotask-mcp/task-master-ai"><img src="https://agentmods.dev/badge/mcp/wyre-ai/autotask-mcp/task-master-ai.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
task-master-ai 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.
Copies of this mod
8 near-identical copies found in the catalogue:
- task-master-ai — 100% identical, 0 lines differ
- task-master-ai — 100% identical, 0 lines differ
- task-master-ai — 100% identical, 0 lines differ
- task-master-ai — 100% identical, 0 lines differ
- task-master-ai — 97% identical, 1 lines differ
- task-master-ai — 92% identical, 1 lines differ
- task-master-ai — 92% identical, 1 lines differ
- task-master-ai — 92% identical, 1 lines differ
What it actually says
{
"task-master-ai": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"task-master-ai"
],
"env": {
"ANTHROPIC_API_KEY": "YOUR_ANTHROPIC_API_KEY_HERE",
"PERPLEXITY_API_KEY": "YOUR_PERPLEXITY_API_KEY_HERE",
"OPENAI_API_KEY": "YOUR_OPENAI_KEY_HERE",
"GOOGLE_API_KEY": "YOUR_GOOGLE_KEY_HERE",
"XAI_API_KEY": "YOUR_XAI_KEY_HERE",
"OPENROUTER_API_KEY": "YOUR_OPENROUTER_KEY_HERE",
"MISTRAL_API_KEY": "YOUR_MISTRAL_KEY_HERE",
"AZURE_OPENAI_API_KEY": "YOUR_AZURE_KEY_HERE",
"OLLAMA_API_KEY": "YOUR_OLLAMA_API_KEY_HERE"
}
}
}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 · 21 lines scan A 79c1ddc8d119
task-master-ai is an MCP server published in the GitHub repository WYRE-AI/autotask-mcp (50 stars, last pushed today), licensed Apache-2.0. 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
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.8.8). Needs 8 environment variables to run.
astravue-mcp
Manage projects, tasks, time tracking, and team collaboration through natural language. Remote server at api.astravue.com.
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.
halopsa-mcp
MCP server "halopsa-mcp" as configured in WYRE-AI/halopsa-mcp. Runs in Docker (ghcr.io/wyre-ai/halopsa-mcp:v1.7.13). Needs 7 environment variables to run.
clickup-mcp
Lightweight ClickUp MCP server - 37 tools, token-optimized (95% smaller responses). Runs locally from the @cavort-it-systems/clickup-mcp npm package. Needs 1 environment variable to run.
planka
MCP server for PLANKA kanban boards. Full CRUD for cards, tasks, comments, and labels. Runs locally from the @gogogadgetbytes/planka-mcp npm package. Needs 3 environment variables to run.