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/vercel/next-devtools-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/vercel/next-devtools-mcp/next-devtools)<a href="https://agentmods.dev/mcp/vercel/next-devtools-mcp/next-devtools"><img src="https://agentmods.dev/badge/mcp/vercel/next-devtools-mcp/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/vercel/next-devtools-mcp/next-devtools"><img src="https://agentmods.dev/badge/mcp/vercel/next-devtools-mcp/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.
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 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 · 8 lines scan A eda387fb1382
next-devtools is an MCP server published in the GitHub repository vercel/next-devtools-mcp (829 stars, last pushed 1mo 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-30.
Other mcp servers, from other repositories
dvalincode
Deterministic security scanning, no model or API key, plus offline-verifiable proof a fix worked. Runs locally from the dvalincode npm package.
dvalin
Open security engineering for code written by humans and AI agents — every repair carries its own offline-verifiable proof. Runs locally from the dvalincode npm package.
vidin
Turn a screen recording into agent-readable annotated keyframes. MCP server + CLI on ffmpeg. Runs locally from the @teunlao/vidin npm package.
kontrol
MCP server "kontrol" as configured in B-A-M-N/Kontrol. Runs locally from the @b-a-m-n/kontrol npm package.
inspectrum
Automatic Codex plan review in Claude Code; on-demand in local MCP hosts; human approval stays yours. Runs locally from the inspectrum npm package.
inspectrum
Review coding-agent plans on demand with peer models, attributed findings, and a structured verdict. Runs locally from the inspectrum npm package.