Package Registry Mcp

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

Look up npm and PyPI packages: versions, descriptions, and metadata. No key required.

VerifiedSTDIODesktop onlyWeb Search & ScrapingDeveloper Tools

Overview

AI-generated overview

Lets an assistant look up npm and PyPI packages to retrieve versions, descriptions, and metadata.

What you can do
This local MCP server exposes tools for querying public package registries. An assistant can look up npm and PyPI packages and retrieve details such as available versions, package descriptions, and other metadata. It is a read-only lookup helper for package information rather than a build or install tool.
When to use it
Useful when you want an assistant to check the latest version of a dependency, confirm a package exists, or pull registry metadata while working on code or documentation. It fits developer workflows that need quick package facts without leaving the conversation.
Requirements
Runs as a local process over stdio, installed from the npm package @mrfentmen/package-registry-mcp, so Node.js and npm are needed. No API key, environment variables, or headers are declared. Network access to the npm and PyPI registries is implied by the lookup function.
Before you install
No credentials are requested and no write actions are described. Queries are sent to public npm and PyPI registry services, so package names you look up leave your machine. Treat returned package metadata as third-party content.

Installation

In SourceWeft

  1. Open Package Registry 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.