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/FlorianBruniaux/node-dep-scopeWrote 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/florianbruniaux/node-dep-scope/dep-scope)<a href="https://agentmods.dev/mcp/florianbruniaux/node-dep-scope/dep-scope"><img src="https://agentmods.dev/badge/mcp/florianbruniaux/node-dep-scope/dep-scope/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/florianbruniaux/node-dep-scope/dep-scope"><img src="https://agentmods.dev/badge/mcp/florianbruniaux/node-dep-scope/dep-scope.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
dep-scope 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.
What it actually says
{
"dep-scope": {
"command": "npx",
"args": [
"-y",
"@florianbruniaux/dep-scope",
"@florianbruniaux/dep-scope",
"dep-scope-mcp"
],
"env": {}
}
}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 cded0f16ad67
dep-scope is an MCP server published in the GitHub repository FlorianBruniaux/node-dep-scope (19 stars, last pushed 1mo 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. 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
wechat-devtools
A Model Context Protocol (MCP) server for controlling WeChat Developer Tools. Runs locally from the wechat-dev-mcp npm package.
json-diff
MCP server "json-diff" as configured in lukascivil/json-difference. Runs ./tools/mcp-json-diff/bin/src/index.js with node.
signalint
Local stdio MCP server for cached, loop-aware JS/TypeScript diagnostics (Oxlint, tsc, Biome). Runs locally from the signalint-mcp npm package.
tglider
Semantic TypeScript and JavaScript MCP server for code navigation, workspace intelligence, dependency topology, diagnostics, and refactoring. Runs locally from the tglider npm package.
weavatrix-refactor-js
Transactional refactoring MCP with 11 evidence-backed tools, hash-bound previews, and rollback. Runs locally from the weavatrix-refactor-js npm package. Needs 3 environment variables to run.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.