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/mjunaidca/taskforceWrote 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/mjunaidca/taskforce/next-devtools)<a href="https://agentmods.dev/mcp/mjunaidca/taskforce/next-devtools"><img src="https://agentmods.dev/badge/mcp/mjunaidca/taskforce/next-devtools/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/mjunaidca/taskforce/next-devtools"><img src="https://agentmods.dev/badge/mcp/mjunaidca/taskforce/next-devtools.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
next-devtools 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 2mo 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
What else .mcp.json configures
This page is one entry in a file that holds 6. 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.
- 2mo ago First seen · 10 lines scan A 5610893e8e8a
next-devtools is an MCP server published in the GitHub repository mjunaidca/taskforce (10 stars, last pushed 9mo ago), with no licence file. 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
mcp-react-toolkit
9 MCP servers for React/TypeScript — dep auditing, a11y, test gen, and TypeScript enforcement. Runs locally from the mcp-react-toolkit npm package.
cloud-command
MCP server "cloud-command", hosted remotely at 127.0.0.1, as configured in Androsh7/cloudcommand.
mern-mcp
Scaffolds MERN CRUD resources into existing Express and React codebases. Runs locally from the mern-mcp npm package. Needs 1 environment variable to run.
local-component-mcp
AST-powered MCP server for Vue/React component analysis — eliminates AI hallucinations on local business components. Runs locally from the @wllcyg001/local-component-mcp npm package.
svgr-mcp
MCP server for converting SVG to React components using SVGR. Runs locally from the svgr-mcp npm package.
mcp-component-harvester
MCP server "mcp-component-harvester" as configured in dazeb/mcp-react-component-harvester. Runs locally from the mcp-component-harvester npm package.