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/lirantal/ls-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/lirantal/ls-mcp/nodejs-api-docs)<a href="https://agentmods.dev/mcp/lirantal/ls-mcp/nodejs-api-docs"><img src="https://agentmods.dev/badge/mcp/lirantal/ls-mcp/nodejs-api-docs.svg" alt="Measured on agentmods" height="20"></a>- Socket warn
Grade A, and why
nodejs-api-docs 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 today.
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
{
"nodejs-api-docs": {
"command": "npx",
"args": [
"-y",
"mcp-server-nodejs-api-docs"
]
}
}What else mcp.json configures
This page is one entry in a file that holds 2. 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.
- today First seen · 9 lines scan A 69985bad822a
nodejs-api-docs is an MCP server published in the GitHub repository lirantal/ls-mcp (84 stars, last pushed today), 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-07.
Other mcp servers, from other repositories
pokeapi-mcp-server
Empower your AI with Pokédex powers! Fetch and explore Pokémon data seamlessly via PokeAPI. Runs locally from the pokeapi-mcp-server npm package.
Sanity
MCP server "Sanity", hosted remotely at mcp.sanity.io, as configured in sanity-io/agent-toolkit.
kafka-schema-registry
MCP server "kafka-schema-registry" as configured in aywengo/kafka-schema-reg-mcp. Runs kafka_schema_registry_unified_mcp.py with python. Needs 3 environment variables to run.
fast-mcp-telegram
Multi-tenant Telegram gateway for AI agents — HTTP+stdio transport, 8 agent-optimized tools, MTProto User API. Runs locally from the fast-mcp-telegram Python package. Needs 4 environment variables to run.
better-telegram-mcp
Production-grade MCP server for Telegram — dual-mode Bot API + MTProto, domain-separated tools. Runs locally from the better-telegram-mcp Python package. Needs 3 environment variables to run.
fastapi-multi-server-mcp
MCP server "fastapi-multi-server-mcp" as configured in AlwaysSany/fastapi-multi-server-mcp. Runs locally from the fastapi-multi-server-mcp Python package.