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/mcping-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/mcping-mcp/task-master)<a href="https://agentmods.dev/mcp/toolprint/mcping-mcp/task-master"><img src="https://agentmods.dev/badge/mcp/toolprint/mcping-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/mcping-mcp/task-master"><img src="https://agentmods.dev/badge/mcp/toolprint/mcping-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.
This is a copy
100% identical to task-master — 0 lines 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": {
"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 4. 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/mcping-mcp (1 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. It is 100% identical to task-master, differing in 0 lines, and is treated as a copy.
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.
halopsa-mcp
MCP server "halopsa-mcp" as configured in WYRE-AI/halopsa-mcp. Runs in Docker (ghcr.io/wyre-ai/halopsa-mcp:v1.7.15). Needs 7 environment variables to run.