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/ofershap/mcp-server-npmWrote 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/ofershap/mcp-server-npm/npm-search)<a href="https://agentmods.dev/mcp/ofershap/mcp-server-npm/npm-search"><img src="https://agentmods.dev/badge/mcp/ofershap/mcp-server-npm/npm-search.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
npm-search 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 7d 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
{
"npm-search": {
"command": "npx",
"args": [
"-y",
"mcp-server-npm-search"
],
"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.
- 7d ago First seen · 10 lines scan A 07aa852a55e1
npm-search is an MCP server published in the GitHub repository ofershap/mcp-server-npm (0 stars, last pushed 6mo 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-31.
Other mcp servers, from other repositories
registry
The MCP server that vets MCP servers: identity, risk grade and per-tool risk before you install. Remote server at api.policylayer.com.
dependency-fitness-mcp
MCP server that returns a cross-validated dependency FITNESS verdict for npm packages: deprecated / yanked / superseded status plus an inferred safe migration target — what to move to and how confident we are — cross-checked across the npm registry, deps. Runs locally from the dependency-fitness-mcp npm package.
npm
MCP server for npm package management — publish, version, search, audit, and more. Runs locally from the @mikusnuz/npm-mcp npm package. Needs 1 environment variable to run.
npm-search-mcp
MCP server "npm-search-mcp" as configured in zcag/npm-search-mcp. Runs in Docker (ghcr.io/zcag/npm-search-mcp:1.0.0).
npm
MCP server "npm", hosted remotely at gateway.pipeworx.io, as configured in pipeworx-io/mcp-npm.
hypermnesia-mcp
Scientifically-grounded memory system based on computational neuroscience research. Runs locally from the hypermnesia-mcp Python package.