Npm Search Mcp

io.github.mrfentmenPublished by GitHub account mrfentmenv1.0.0Updated Oct 25, 2026

Search npm packages and inspect package metadata from the public registry. No key required.

VerifiedSTDIODesktop onlyDeveloper Tools

Overview

AI-generated overview

A local MCP server that lets an assistant search npm packages and inspect their metadata from the public npm registry, with no API key needed.

What you can do
Search the public npm registry for packages by name or keyword, and inspect metadata for a given package. No tools are listed in the manifest, so the exact tool set is not documented beyond search and metadata lookup. It runs locally over stdio and requires no key.
When to use it
Useful when you want an assistant to look up npm packages, compare options, or check package details while working on JavaScript or Node.js projects, without leaving the conversation to browse the registry.
Requirements
Runs as a local process on the user's machine, installed from the npm package npm-search-mcp over stdio. Node.js and npm are needed to install and run it. No API key, environment variables or headers are declared. Network access to the public npm registry is required.
Before you install
Queries go to the public npm registry, so search terms and package names are sent to that third party. The server is read-only per the description; no credentials or payments are involved. Desktop only, with no web executable.

Installation

In SourceWeft

  1. Open Npm Search Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.0LatestSep 22, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.