@pipeworx/deps-dev

Connect: https://pipeworx.io/mcp — every tool in the catalog, including @pipeworx/deps-dev’s. Install: one-click buttons

No MCP client? Skip the connection: POST https://gateway.pipeworx.io/v1/tools/search_packs {"query":"..."} to find a tool below, GET /v1/tools/<name> for its schema, POST the same URL with arguments for the data — see For AI agents.

Tools: 5

deps.dev MCP — Google’s package metadata API: versions, dependencies, dependents, security advisories, project signals. Keyless.

Tools

• project(project_type, project_key) — project metadata (github | gitlab | bitbucket)
• system(system_) — package metadata across all systems (npm, PyPI, Go, Maven, NuGet, crates.io, RubyGems, Cargo)
• package(system_, name) — package metadata
• version(system_, name, version) — single version (deps, advisories, license)
• dependencies(system_, name, version) — resolved dependency graph
• query(query) — query packages/versions by hash, repo url, etc.

Data source

https://api.deps.dev/v3/

Tools

• project — Fetch deps.dev project metadata for a GitHub, GitLab, or Bitbucket repository (e.g. project_key=“facebook/react”), returning scorecard scores, version count, and linked package references.
• package — Fetch deps.dev metadata for an open-source package by ecosystem (NPM/PYPI/GO/MAVEN/NUGET/CARGO/RUBYGEMS) and name, returning version list, latest version, and linked source repository.
• version — Security advisories, license and dependency metadata for ONE specific published release of a package. Requires an exact version that this package actually shipped — if you do not already have one, cal
• dependencies — The fully resolved dependency graph of one published release — every transitive package it pulls in. Same requirement as version: the version must be one this package actually shipped, so call `pack
• query — Query packages/versions (by hash, repo URL, etc).