{
  "markdown": "# mcp-npm\n\nnpm MCP — wraps the npm Registry API (free, no auth)\n\nPart of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 1476+ live data sources.\n\n## Tools\n\n| Tool | Description |\n|------|-------------|\n| `search_packages` | Search npm for packages by keyword. Returns package names, descriptions, latest versions, publish dates, and publishers. Use when discovering libraries for a task. |\n| `get_package` | Get full details for a specific package: version, description, dependencies, homepage, repository, and license. Use after search_packages to evaluate a candidate package. |\n| `get_downloads` | Fetch npm download counts for a package over a named period (last-day, last-week, last-month, last-year) or a custom date range like \"2024-01-01:2024-06-30\". Returns total downloads, start date, and end date. |\n| `list_versions` | List published versions of an npm package with publish dates, dist-tags (latest/next/beta), and deprecation notices — answers \"what versions of <pkg> exist\", \"when was <pkg> last published\", \"is the latest version deprecated\". Returns versions newest-first, plus the package created/last-modified timestamps. |\n| `get_version_info` | Get metadata for a SPECIFIC version (or dist-tag) of an npm package: dependencies, dev/peer dependencies, engines, license, tarball + integrity hash + unpacked size, and any deprecation notice. Use for \"dependencies of <pkg>@<version>\", pinned-version audits, or inspecting a particular release. Version accepts an exact version (e.g. \"4.18.2\"), a dist-tag (e.g. \"latest\", \"next\"), or omit for the latest. |\n\n## Quick Start\n\nAdd to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):\n\n```json\n{\n  \"mcpServers\": {\n    \"npm\": {\n      \"url\": \"https://gateway.pipeworx.io/npm/mcp\"\n    }\n  }\n}\n```\n\n### What this endpoint actually serves\n\n`tools/list` at `https://gateway.pipeworx.io/npm/mcp` returns the tools in the table\nabove **plus the shared Pipeworx meta-tools** — `ask_pipeworx`,\n`discover_tools`, `search_within`, `remember`/`recall` and the rest of the\ngateway-wide set. So the tool count you see is larger than this table: a\nsingle-pack endpoint currently lists roughly 30 shared tools alongside the\npack's own. The connection's `initialize` response states its exact scope, and\nis the authoritative answer for a given day.\n\nThis is deliberate, not multiplexing by accident. The meta-tools are what let a\nscoped connection answer a question this pack does not cover — via\n`ask_pipeworx`, which routes across the whole catalog — without you adding a\nsecond MCP server. There is currently no way to mount a pack endpoint without\nthem; if the extra schemas cost you more context than the routing is worth,\nconnect to the full gateway once rather than to several pack endpoints.\n\nOr connect to the full Pipeworx gateway to get every pack's tools listed\ndirectly, instead of just this one's:\n\n```json\n{\n  \"mcpServers\": {\n    \"pipeworx\": {\n      \"url\": \"https://gateway.pipeworx.io/mcp\"\n    }\n  }\n}\n```\n\nBoth URLs reach the same gateway and the same 1476+ data sources. The\nonly difference is which pack's tools are listed **directly**; `ask_pipeworx`\nreaches all of them from either one.\n\n## Using with ask_pipeworx\n\nInstead of calling tools directly, you can ask questions in plain English —\nthis works on the pack endpoint above as well as on the full gateway:\n\n```\nask_pipeworx({ question: \"your question about Npm data\" })\n```\n\nThe gateway picks the right tool and fills the arguments automatically.\n\n## More\n\n- [Docs and guides](https://pipeworx.io/docs)\n- [pipeworx.io](https://pipeworx.io)\n\n## License\n\nMIT\n",
  "bytes": 3613,
  "sha": "40943a63a7c798cf36c9f25959052e477660a24a82369ca2ccf047eec89e1215",
  "repo_slug": "pipeworx-io/mcp-npm",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_pipeworx_io_npm_080c5cdb/readme"
}