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.
npx agentmods add mcp/chayan-1906/claude-lens-next.js/next-devtoolsgit clone --depth 1 https://github.com/chayan-1906/Claude-Lens-Next.jsWrote 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/chayan-1906/claude-lens-next.js/next-devtools)<a href="https://agentmods.dev/mcp/chayan-1906/claude-lens-next.js/next-devtools"><img src="https://agentmods.dev/badge/mcp/chayan-1906/claude-lens-next.js/next-devtools.svg" alt="Measured on agentmods" 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 6d 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
80% identical to next-devtools — 2 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 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.
- 6d ago First seen · 9 lines scan A c81a8ba90c8a
next-devtools is an MCP server published in the GitHub repository chayan-1906/Claude-Lens-Next.js (2 stars, last pushed 2mo 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 80% identical to next-devtools, differing in 2 lines, and is treated as a copy.
Other mcp servers, from other repositories
jsx-notation
JSXN encoder/decoder — compact notation for React/Next.js files, optimized for LLMs. Runs locally from the jsx-notation npm package.
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.
heroui-react
MCP server for HeroUI component documentation via Model Context Protocol. Runs locally from the @heroui/react-mcp npm package.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.
reference-langchain
MCP server "reference-langchain", hosted remotely at reference.langchain.com, as configured in langchain-ai/langchain.
mcp-search
MCP server "mcp-search" as configured in thedotmack/claude-mem. Runs const f=require('fs'),p=require('path'),o=require('os'),c=require('child_process');const h=o.homedir();const C=process.env.CLAUDE_CONFIG_DIR||p.join(h,'.claude');const E=process.env.CLAUDE_PLUGIN_ROOT||process.env.PLUGIN_ROOT||'';const…