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/sherpa-sh/Sherpa-ActionWrote 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/sherpa-sh/sherpa-action/next-devtools)<a href="https://agentmods.dev/mcp/sherpa-sh/sherpa-action/next-devtools"><img src="https://agentmods.dev/badge/mcp/sherpa-sh/sherpa-action/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/sherpa-sh/sherpa-action/next-devtools"><img src="https://agentmods.dev/badge/mcp/sherpa-sh/sherpa-action/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 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 next-devtools — 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
{
"next-devtools": {
"command": "npx",
"args": [
"-y",
"next-devtools-mcp@latest"
]
}
}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 · 9 lines scan A c81a8ba90c8a
next-devtools is an MCP server published in the GitHub repository sherpa-sh/Sherpa-Action (22 stars, last pushed 8mo ago), 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. It is 100% identical to next-devtools, differing in 0 lines, and is treated as a copy.
Other mcp servers, from other repositories
k8s-mcp-server
MCP server "k8s-mcp-server" as configured in VersusControl/devops-ai-guidelines. Launched with ${workspaceFolder}/code/04/bin/k8s-mcp-server.
mcp-server
Unified MCP server for Ignite UI — documentation, API, and CLI scaffolding. Runs locally from the @igniteui/mcp-server npm package.
repowire-remote
MCP server "repowire-remote", hosted remotely at relay.repowire.io, as configured in prassanna-ravishankar/repowire.
terraform
MCP server "terraform" as configured in aws-samples/sample-agentic-chatbot-accelerator. Runs in Docker (hashicorp/terraform-mcp-server:0.5.2).
storybook-mcp
MCP server "storybook-mcp", hosted remotely at localhost, as configured in yannbf/mealdrop.
aws-auth
MCP server "aws-auth" as configured in N0mansky/aws-auth. Runs locally from the aws-auth Python package.