Unpkg Mcp

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

Package file metadata from the unpkg CDN. No key required.

VerifiedSTDIODesktop onlyDeveloper Tools

Overview

AI-generated overview

A local MCP server that gives an assistant package file metadata from the unpkg CDN, with no API key required.

What you can do
Look up file metadata for packages served by the unpkg CDN, so an assistant can inspect what a published package contains and how its files are described. It works against the public CDN and needs no key.
When to use it
Useful when you want an assistant to check details about files in npm packages hosted on unpkg without leaving the conversation or setting up credentials.
Requirements
Runs as a local process on the user's machine, installed from the npm package unpkg-mcp; requires Node.js and network access to the unpkg CDN. No environment variables, headers or accounts are declared.
Before you install
It queries a third-party public CDN, so package names and lookups are sent to unpkg. The manifest lists no tools, so verify what it actually exposes before relying on it.

Installation

In SourceWeft

  1. Open Unpkg 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.