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/toolprint/cco-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/toolprint/cco-mcp/task-master)<a href="https://agentmods.dev/mcp/toolprint/cco-mcp/task-master"><img src="https://agentmods.dev/badge/mcp/toolprint/cco-mcp/task-master/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/toolprint/cco-mcp/task-master"><img src="https://agentmods.dev/badge/mcp/toolprint/cco-mcp/task-master.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
task-master 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- task-master — 100% identical, 0 lines differ
What it actually says
{
"task-master": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"--package=task-master-ai",
"task-master-ai"
],
"env": {}
}
}What else .mcp.json configures
This page is one entry in a file that holds 5. Installing the file brings all of them; each is measured and scanned on its own page.
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 · 12 lines scan A a54205d1ea84
task-master is an MCP server published in the GitHub repository toolprint/cco-mcp (19 stars, last pushed 1y 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
usrcp
Encrypted local ledger of structured user state, shared across every MCP-aware AI tool. Runs locally from the usrcp npm package. Needs 1 environment variable to run.
reflect-mcp
Reflection's autonomous runtime — wake, read prior state, do useful work, write back, sleep. Runs locally from the reflect-mcp Python package.
capsule
Compact, source-linked context packs that reduce token waste for coding agents. Runs locally from the capsulectx npm package.
petstore
MCP server "petstore", hosted remotely at 127.0.0.1, as configured in gujord/OpenAPI-MCP.
jira-mcp
Jira MCP for controlling Jira through Jira Command Line. Runs locally from the jira-tools-mcp Python package. Needs 2 environment variables to run.
rea
Reverse engineer anything from your terminal or agent with one CLI and MCP server. Runs locally from the rea-agents npm package.