npm (Unofficial)
Server Details
Unofficial npm MCP — wraps the npm Registry API (free, no auth)
The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Uptime
- 0.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- pipeworx-io/mcp-npm
- GitHub Stars
- 0
- Server Listing
- mcp-npm
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 49 tools
The set contains several overlapping clusters: ask_pipeworx / ask_pipeworx_beta / ask_pipeworx_grounded / deep_research all answer questions via the same router, entity_profile / company_facts / compare_entities / recent_changes / validate_claim all research companies, and polymarket_edges / polymarket_arbitrage / polymarket_kalshi_spread / polymarket_fill_risk / polymarket_edge_tracker all analyze prediction-market edge. The very long descriptions do explicitly steer callers ("prefer over", "use this instead when"), which keeps it workable, but an agent must read carefully to avoid misselection. There are also unrelated tools (npm package lookups, memory, subscriptions) with no stated relation to the rest.
Most names are snake_case, but conventions are mixed: verb-first (search_packages, get_package, resolve_entity, scan_dependency) alongside noun-first phrases (company_facts, entity_profile, prediction_calibration, recent_changes, resolution_audit) and prefix-inconsistent families (ai_visibility_check vs scan_competitor_ai_presence). The _beta suffix on ask_pipeworx_beta is a versioning outlier rather than a verb_noun pattern. It is readable throughout, but there is no single predictable scheme.
49 tools is far beyond a well-scoped surface, and the server is presented as 'Npm' while the bulk of the catalog is SEC research, prediction-market analytics, memory, and subscription management. Many of the tools are heavyweight composite meta-tools whose individual schemas are enormous, making the set hard to hold in context. A tighter npm/registry surface of a handful of tools plus a few meta-tools would be appropriate.
For the nominal npm domain the read surface is decent (search, get_package, get_version_info, list_versions, get_downloads, scan_dependency), but there is no publish/write path and no scoped-owner or tarball-download operation. Memory (remember/recall/forget) and subscriptions (subscribe/list/unsubscribe/recent_alerts) are complete lifecycles, yet several descriptions reference tools that are not exposed here (fetch_url, polymarket_market, kalshi_market, fred_release_dates), creating dead ends when an agent follows the instructions.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Unofficial PyPI MCP — wraps the Python Package Index (PyPI) JSON API (free, no auth).
Crates.io MCP — wraps the crates.io REST API v1 (free, no auth)
Unofficial RubyGems MCP — wraps the RubyGems.org public API (free, no auth)
Unofficial Docker Hub MCP — wraps the Docker Hub v2 API (free, no auth required for public data)
Related MCP Servers
- AlicenseBqualityBmaintenanceMCP server for npm package management — publish, install, audit, search, security & dependency health4266 npm1MIT
- AlicenseBqualityDmaintenanceMCP server for npm — search packages, check bundle sizes, scan vulnerabilities, compare downloads, inspect dependencies.860 npm1MIT
- AlicenseCqualityDmaintenanceMCP server for searching npm packages1227 npm16MIT
- AlicenseAqualityDmaintenanceMCP server to search npm packages, view details, compare, check downloads, and inspect dependencies.645 npmMIT
Glama MCP Gateway
Add one secure layer between your agents and this server.