Package Intel MCP

io.github.selflabbsPublished by GitHub account selflabbsv1.0.0Updated Oct 24, 2026

Package intelligence for AI agents across npm, PyPI, crates.io and deps.dev. No API keys.

VerifiedStreamable HTTPWeb executableDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Remote MCP server giving assistants package intelligence for npm, PyPI and crates.io: metadata, versions, downloads, dependencies and health signals.

What you can do
  • Look up package metadata such as description, latest version, license and repo links
  • List full version history with release dates
  • Report download counts and popularity signals
  • Fetch direct dependencies for a given version and health signals like OpenSSF Scorecard, stars and dependents
  • Search packages by keyword across npm, PyPI or crates
When to use it
Useful when an assistant helps choose, vet or upgrade dependencies and should check maintenance, popularity and dependency footprint before adding a package. Handy for quick supply-chain sanity checks mid-task without leaving the conversation.
Requirements
A remote MCP endpoint reached over streamable HTTP; no API keys, signup or environment variables are needed. Network access to the hosted service is required.
Before you install
Read-only lookups, but queries and package names go to a third-party hosted service. Data is drawn from public registry APIs and deps.dev and is informational, so verify licensing and security findings before relying on them.

Installation

In SourceWeft

  1. Open Package Intel MCP in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.selflabbs%2Fpackage-intel-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "package-intel": {
      "type": "http",
      "url": "https://package.selflabbs.com/mcp"
    }
  }
}

README

Package Intel MCP — by Datakoot

Software supply-chain intelligence for AI agents — as MCP tools your agent can call mid-task, so it can vet a dependency before it installs it. Covers npm, PyPI and crates.io. No API keys.

Tools

ToolWhat it doesSource
package_infoMetadata for a package: description, latest version, license, homepage & repo linksnpm / PyPI / crates.io
package_versionsFull version history with release datesnpm / PyPI / crates.io
package_downloadsDownload counts and popularity signalnpm / PyPI / crates.io
package_dependenciesDirect dependencies for a given versiondeps.dev
package_healthHealth signals: OpenSSF Scorecard, stars, dependentsdeps.dev
package_searchSearch for packages by keywordnpm / PyPI / crates.io

Every tool accepts an ecosystem of npm, pypi, or crates. No API keys required.

Quick start

claude mcp add --transport http package-intel https://package.datakoot.com/mcp

Or point any MCP client at https://package.datakoot.com/mcp.

Try it in 10 seconds — no key, no signup

Paste this into a terminal:

bash
curl -s https://package.datakoot.com/mcp \  -H 'content-type: application/json' \  -H 'accept: application/json, text/event-stream' \  -d '{"jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": {"name": "package_health", "arguments": {"ecosystem": "npm", "name": "express"}}}'

You get a supply-chain health snapshot for the npm package express — versions, downloads, dependencies, maintenance signals — no API key, nothing to sign up for.

Or point any MCP client at the URL and just ask your agent, in plain language:

  • "How healthy is the npm package express?"
  • "Before I add left-pad, is it actively maintained and widely used?"

Data & attribution

Data comes from the public registry APIs for npm, PyPI and crates.io, plus deps.dev (Google Open Source Insights, CC-BY 4.0) for dependency graphs and OpenSSF Scorecard health signals. Package data is served from official public APIs and is informational.

Part of Datakoot — keyless intelligence APIs for AI agents.

Source: README.md at commit 02a68c5

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

50% 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 daysRequired25 pts

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

  • Auth declaredRequired10 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
  • License10 pts