Skip to main content
Glama
692,740 tools. Updated 2026-10-23 19:43

"Packagist" matching MCP tools:

Matching MCP Servers

  • Identify vulnerable package versions and prioritize fixes by severity, using KEV, EPSS, and CVSS to determine the smallest upgrade that resolves all.
    MIT
  • Check the current version of a package from official registries to identify outdated dependencies. Supports npm, PyPI, Packagist, Crates.io, Maven, Go, RubyGems, NuGet, Hex, CRAN, CPAN, pub.dev, Homebrew, Conda, Clojars, Hackage, Julia, Swift PM, and Chocolatey.
    MIT
  • Retrieve the latest version of a package from its official registry. Supports npm, PyPI, crates.io, and more by using a registry prefix like 'pip:'.
    MIT
  • Scan installed packages against the live OSV database to detect known vulnerabilities and CVEs in real-time.
    MIT
  • Retrieve the current version of a package from its official registry. Prevent using outdated dependencies by checking available releases across major ecosystems.
    MIT
  • Check for outdated dependencies by listing upstream package versions newer than the current project version. Read-only queries against PyPI, npm, NuGet, crates.io, or Packagist — no version bumps applied.
    MIT
  • Look up a CVE or GHSA ID for CVSS scores, CWE types, and known-exploited status, or check any package version across npm, PyPI, Maven, and more for known vulnerabilities and fixed versions.
    MIT
  • Fetch PHP/Composer package metadata from Packagist – versions, description, maintainers, and repository details – for supply chain security audits.
    MIT
  • Update the local OSV vulnerability database for PyPI, npm, Go, or Packagist ecosystems to ensure dependency checks use current data.
    Apache 2.0
  • Retrieve the latest version of a PHP Composer package from Packagist by providing the package name in vendor/package format.
    MIT
  • Check a software package for known vulnerabilities by specifying its name and ecosystem (e.g., PyPI, npm, Maven), with an optional version filter, using data from OSV.dev.
    Apache 2.0
  • Identify known vulnerabilities in a software package by querying the OSV database for CVEs and security advisories, with optional version and ecosystem filters.
    MIT
  • Look up the known vulnerabilities affecting exact package versions in the public OSV database (npm, PyPI, Go, Maven, crates.io, RubyGems, NuGet, Packagist, Pub, Hex), 1 to 50 packages per call. Per package: every OSV advisory for that version with its id, CVE/GHSA aliases, summary, severity (database label, CVSS vectors, v3 base scores), the versions that fix it or "no fix published", published/modified dates and a link. Plus a summary: packages checked, packages vulnerable, total advisories and the highest severity. Evidence, not advice: absence from OSV does not prove safety.
    ConnectorNo auth