npm Package Metadata — Versions, Licenses & Counts MCP Server

by kriton-dev Your server? Claim it

answering

npm Package Metadata — Versions, Licenses & Counts is answering right now. Last checked 10 min ago.

Read latest npm package versions, license tokens and dependency counts

Uptime history 5 days of history

5 days agonow

100.0%

Uptime 24h

91 of 91 checks

—

Tools

hidden behind auth

355 ms

Response time

average over 24h

API key

Access

streamable-http

Nothing serious here today

Today is the operative word: we check npm Package Metadata — Versions, Licenses & Counts every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 10 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add npm-package-metadata --transport http 'https://mcp.apify.com/?tools=hermeskd/npm-package-metadata'

Settings → Connectors → Add custom connector, then paste this address

https://mcp.apify.com/?tools=hermeskd/npm-package-metadata

~/.codex/config.toml

[mcp_servers.npm-package-metadata]
url = "https://mcp.apify.com/?tools=hermeskd/npm-package-metadata"

.cursor/mcp.json

{
  "mcpServers": {
    "npm-package-metadata": {
      "url": "https://mcp.apify.com/?tools=hermeskd/npm-package-metadata"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "npm-package-metadata": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=hermeskd/npm-package-metadata"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, but you need an API key from its owner to call it.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.apify.com/?tools=hermeskd/npm-package-metadata	streamable-http	needs key	331 ms	10 min ago

Alternatives to npm Package Metadata — Versions, Licenses & Counts

same job, measured the same way

Package Version Check MCP

by mshekow

Returns the latest package / dependency / tool versions for Python, NPM, Go, Docker, Helm, etc.

825 installs/wk local only

NuGet API Inspector

by dimonsmart

Inspect NuGet package APIs, dependencies, metadata, and breaking changes across versions.

local only

Package Registry MCP

by mrfentmen

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

51 installs/wk local only

ScrapeMole Pkgs

by pages-scrapemole

Pay-per-call x402 npm and PyPI package metadata, versions, search, download counts.

6 tools answering

npx-vibe

by devrajsinh-jhala

Read-only npm package and project dependency preflight tools for AI applications.

77 installs/wk local only

Dependency check

by ladanyin

Check a package version for known vulnerabilities and Packagist release facts.

2 tools answering

Packcompare

by cloudcorprecords

Diff two versions of a package: files, dependencies, size, and exports.

283 installs/wk local only

Cairn Commons (read-only)

by cairncommons

Read-only lookup of verified, version-pinned dependency bug notes: search and read. No account.

3 tools answering

npm Package Metadata — Versions, Licenses & Counts — questions

Answers built from our own checks of this server.

Why is there no tool list for npm Package Metadata — Versions, Licenses & Counts?

The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.

Is npm Package Metadata — Versions, Licenses & Counts working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 355 ms. The bar chart above shows every period we have measured.

How do I connect npm Package Metadata — Versions, Licenses & Counts?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own key: it refuses anonymous clients.

Does npm Package Metadata — Versions, Licenses & Counts need an API key?

Yes. Every time we knock, npm Package Metadata — Versions, Licenses & Counts answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.

How fast is npm Package Metadata — Versions, Licenses & Counts?

It answers our handshake in 355 ms on average, which is faster than 38% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.