Package registry
Compare npm MCP servers by package target, launch command, quality score, version metadata, and setup requirements.
NPM is one of the most common distribution channels for MCP servers because many developer-tool integrations are written in JavaScript or TypeScript and can be launched directly with package-manager commands. For users, npm-based servers are often easy to test because the package identifier maps directly to an install or run command.
A strong npm MCP listing should show the package name, published version, transport type, launch command, required environment variables, and any server-specific arguments. Those fields are more useful than a generic description because they tell an MCP client operator how the package becomes a running server.
This Wardn Hub page groups published MCP servers that declare npm package metadata. Use the tables to compare install targets, quality scores, update freshness, and configuration requirements before deciding which package belongs in a local or team MCP setup.
These are the practical checks to run before adding a matching MCP server to a client or team workflow.
| Criterion | What to verify |
|---|---|
| Registry | npm |
| Best fit | JavaScript and TypeScript MCP servers distributed through npm |
| Configuration focus | Package identifier, version, npx/npm command, args, and environment variables |
This table is generated from published Wardn Hub registry records and sampled version details for the current page topic.
| Server | Package or endpoint | Transport | Score | Updated |
|---|---|---|---|---|
| dossierai.imboard/dossier | @ai-dossier/mcp-servernpx | stdio | 90/100 | Jul 27, 2026 |
| Anki MCP Serverai.ankimcp/anki-mcp-server | @ankimcp/anki-mcp-servernpx -y @ankimcp/anki-mcp-server --stdio | stdio | 89/100 | Jul 3, 2026 |
| Perplexity API Platform MCP Serverai.perplexity/mcp-server | @perplexity-ai/mcp-servernpx -y @perplexity-ai/mcp-server | stdio | 80/100 | Jul 17, 2026 |
| Dynamic Feedai.dynamicfeed/dynamic-feed | dynamicfeed-mcpnpx -y dynamicfeed-mcp | stdio | 79/100 | Jul 17, 2026 |
| creationloop-mcpai.creationloop/creationloop | mcp-remotenpx https://creationloop.ai/api/mcp | stdio | 74/100 | Jul 26, 2026 |
| CreativeScope — Mobile Game Ad Creative Intelligenceai.creativescope/creative-intelligence | mcp-remotenpx https://mcp.creativescope.ai/mcp --header Authorization: Bearer cs_live_YOUR_KEY | stdio | 74/100 | Jul 25, 2026 |
Registry metadata is most useful when it exposes launch requirements before installation.
Common variables in sampled matching records include ANKI_CONNECT_URL, ANKI_CONNECT_API_VERSION, ANKI_CONNECT_API_KEY, ANKI_CONNECT_TIMEOUT, READ_ONLY, LOG_LEVEL, MEDIA_ALLOWED_TYPES and MEDIA_IMPORT_DIR. Verify secrets and token scopes upstream before use.
Published package arguments include --stdio, --tunnel, --login, --logout, --port, --host, --anki-connect and --ngrok. Check defaults and required values before pasting commands into an MCP client.
Compare Wardn Score, update date, package target, repository ownership, and upstream documentation. Treat registry data as a shortlist, not final approval.
The best npm MCP servers are the matching published entries with clear package or endpoint metadata, recent updates, strong Wardn scores, and documented configuration requirements.
Start with the 6 matching Wardn Hub records on this page, compare score and update freshness, then inspect the individual server page for package commands, environment variables, and upstream documentation.
No. Wardn Hub is a registry and discovery product. Always verify upstream documentation, required secrets, permissions, and client compatibility before installing or connecting a server.
