Deps Dev
deps.dev MCP — Google's package metadata + dependency graph API.
Open the source (opens github.com) https://github.com/pipeworx-io/mcp-deps-dev
Before you use it
- Runs on someone else's server: what you send it leaves your machine.
- Runs on your computer with your permissions. Read what it can do before connecting it to an agent.
- Needs credentials: PIPEWORX_API_KEY. Use a key with the least access you can.
What it is
MCP servers from io.github.pipeworx-io.
The problem it solves and who it suits haven't been reviewed by InnerVault. The description above is the source's own.
How to get it
npm package (stdio)
@pipeworx/mcp-deps-dev@0.2.1
From the server's entry in the official MCP Registry
Remote endpoint (streamable-http)
https://gateway.pipeworx.io/deps-dev/mcp
From the server's entry in the official MCP Registry
Settings it asks for
PIPEWORX_API_KEYsecret · Optional Pipeworx API key. Without it calls are anonymous and capped daily; a free key raises the cap.
Related
-
deps-dev-mcp
MCP serversOpen source dependency metadata from Google deps.dev. No key required.
deps-dev-mcp@1.0.6 -
Google Open Source Insights (deps.dev) OpenSSF Security Scorecard & dependency tree audit.
-
devstack-mcp
MCP serversDev-registry data: npm/PyPI/Docker/VS Code packages, dep graphs, vulns, 50+ ecosystems.
-
Package Intel MCP
MCP serversPackage intelligence for AI agents across npm, PyPI, crates.io and deps.dev. No API keys.
-
Package Intel MCP
MCP serversPackage intelligence for AI agents across npm, PyPI, crates.io and deps.dev. No API keys.
-
TridentChain Security
MCP serversLocal supply-chain CVE scanner via OSV/NVD. Scans deps and IDE extensions. No upload.
tridentchain-mcp@0.1.5