Bot Essentials
SupportSign in

MCP connector · Developer

PkgIntel

Check package versions, advisories and licences.

Featured

  • 10 tools
  • 51 tests passing
  • MIT licence
  • Free and open

InstallStar on GitHubSupport the project

See it work

Example. A real tool and its real input. No live data is shown here.

You ask
“Does lodash 4.17.21 have known vulnerabilities?”
Your bot calls
check_vulnerabilities with ecosystem, name and version
It gets back
OSV advisories for that exact version. No API key needed.

Install

git clone https://github.com/si-essence/pkgintel-mcp.git && cd pkgintel-mcp && npm install && npm run build

Needs Node.js. Then add the built server to your MCP client. Install guide

Facts

Tools
10
Tests
51 passing
Licence
MIT
Source
github.com/si-essence/pkgintel-mcp
Listing updated
31 October 2026
Last code push
23 October 2026
Maintained by
Bot Essentials

Tests were run on 27 October 2026 in a clean copy of each connector. You bring your own keys for any service it talks to.

Details and limits

PkgIntel is a keyless, read-only MCP server for package intelligence. The package name is pkgintel-mcp. You run it over stdio, or over stateless Streamable HTTP on 127.0.0.1.

It reads public metadata from deps.dev v3, OSV.dev, the npm registry, the PyPI JSON API, the crates.io API, and the OpenSSF Scorecard API. Every tool is read-only.

A package record carries a normalized ecosystem and name, versions, latest and default version, SPDX licence strings, links, deprecation, advisories, and SLSA or provenance when deps.dev provides them. Names are normalized per ecosystem. PyPI follows PEP 503. One failed upstream does not drop the others.

Set PKGINTEL_CONTACT to an address you control. It is the User-Agent mailto. The image default is contact@example.com. Do not bake a personal address into an image.

Lockfile formats are package-lock.json v2/v3, pinned requirements.txt (name==version only), Cargo.lock, and go.sum. Text cap 2,000,000 characters. Package cap 1,500.

npms.io is excluded because the service was not verified as maintained. Semantic Scholar is not a source here.

The inbound window defaults to 60 calls a minute. A cache hit does not spend it. Each source has a waiting scheduler so this process keeps the published gap instead of bursting.

The connector code is MIT. The data licences of the upstream APIs are separate. None of these providers endorse this project.

Tools

10 tools. Every tool is read-only.

  • get_package

    Look up a package across seven ecosystems. Versions, latest, licences, links, deprecation.

  • get_version

    One exact package version. Licences, advisories, links, SLSA when present.

  • get_dependencies

    Depth-limited resolved graph from deps.dev. Default depth 2, max 4.

  • check_vulnerabilities

    OSV advisories for one package@version or a batch of 1 to 50.

  • audit_lockfile

    Parse a lockfile from text or a local path. OSV hits and licence counts.

  • compare_packages

    Side-by-side latest, licences, and deprecation for 2 to 5 packages.

  • get_scorecard

    OpenSSF Scorecard for a GitHub repo, or resolve the repo from a package.

  • search_packages

    Search npm or crates.io. PyPI has no search API.

  • license_check

    Evaluate an SPDX 2.x expression against an allow-list.

  • list_sources

    Sources, rates, terms links, and whether PKGINTEL_CONTACT is set. Values are never returned.