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.
npx agentmods add mcp/asachs01/float-mcp/task-master-aigit clone --depth 1 https://github.com/asachs01/float-mcpGrade 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 2d 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.
This is a copy
92% identical to task-master-ai — 1 line differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{
"task-master-ai": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"--package=task-master-ai",
"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.
- 2d ago First seen · 22 lines scan A df11bb11b19d
task-master-ai is an MCP server published in the GitHub repository asachs01/float-mcp (2 stars, last pushed 6mo 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. It is 92% identical to task-master-ai, differing in 1 line, and is treated as a copy.
Other mcp servers, from other repositories
kaneo
Official MCP server for Kaneo: manage tasks, projects, and labels from Claude and other MCP clients. Runs locally from the @kaneo/mcp npm package. Needs 2 environment variables to run.
astravue-mcp
Manage projects, tasks, time tracking, and team collaboration through natural language. Remote server at api.astravue.com.
astravue
MCP server "astravue", hosted remotely at api.astravue.com, as configured in AstravueOrg/astravue-mcp-server.
openproject-mcp-server
MCP server for OpenProject: 87 tools for work packages, attachments, git activity, time tracking, meetings and reporting over the API v3. Runs locally from the openproject-mcp-server Python package. Needs 5 environment variables to run.
taiga-mcp-server
MCP server connecting Claude, Cursor, Windsurf, and other AI assistants to Taiga (Cloud and self-hosted) — projects, epics, user stories, tasks, issues, sprints, wiki, and more. Runs locally from the @madebyclowd/taiga-mcp-server npm package.
stellary-project-management
Connect AI assistants to Stellary projects, boards, documents, and governed agent workflows. Remote server at api.stellary.co.