deps.dev MCP integration
Google Open Source Insights package, dependency, license, advisory, and provenance metadata.
Sign in and add deps.dev in Apps. No deps.dev account is required.
Tools
| Name | Description |
|---|---|
get_packageGet deps.dev package information and available versions. | Get deps.dev package information and available versions. |
get_versionGet deps.dev version metadata including licenses, advisories, links, and registries. | Get deps.dev version metadata including licenses, advisories, links, and registries. |
get_requirementsGet unresolved dependency requirements declared by one package version. | Get unresolved dependency requirements declared by one package version. |
get_dependenciesGet the resolved dependency graph for one package version when deps.dev has resolution data. | Get the resolved dependency graph for one package version when deps.dev has resolution data. |
get_advisoryGet deps.dev advisory metadata for an OSV advisory ID. | Get deps.dev advisory metadata for an OSV advisory ID. |
queryQuery deps.dev by package version or artifact hash. | Query deps.dev by package version or artifact hash. |
Quick Start
import { WeavzClient } from '@weavz-io/sdk'
const weavz = new WeavzClient({ apiKey: 'wvz_...' })
const result = await weavz.actions.execute('deps-dev', 'get_package', {
workspaceId: '550e8400-e29b-41d4-a716-446655440000',
integrationAlias: 'deps-dev',
input: { /* ... */ },
})Related Integrations
Works well with
Frequently Asked Questions
Is there a deps.dev MCP server through Weavz?
Yes. Add the deps.dev integration to a Weavz workspace, enable the actions you need and connect any required account. Weavz provides the workspace MCP endpoint in Tool Mode or Code Mode. The catalog currently lists 6 deps.dev actions.
What can an AI agent do with deps.dev?
Available actions include Get Package, Get Version, Get Requirements, Get Dependencies, Get Advisory, and more. Your workspace exposes only the actions you enable. The agent also needs the intended account access and any required input values.
How do I connect deps.dev to Claude or ChatGPT?
Use a compatible remote MCP client, add the Weavz connector and choose a workspace. Add deps.dev, connect the required account and review the enabled actions. Client availability and account requirements vary; adding the connector does not authorize every app automatically.
Can I use deps.dev through an API or SDK?
Yes, supported actions can run through the Weavz REST API, TypeScript SDK or Python SDK. Configure a workspace and the required connections, use scoped access, and pass the intended end-user context when acting for a customer.
What authentication does deps.dev require?
This catalog integration does not require a stored external account connection. Provider terms, rate limits and tool-specific inputs can still apply.
How do I review sensitive deps.dev actions?
Limit enabled actions, scope credentials to the intended user and configure Human Gates for the operations that need review. A matching policy can pause a send, record change or other sensitive action for an approver before execution.
What limits or costs apply to deps.dev?
Weavz plan limits apply to the actions and resources you use. The external provider may also require an account, a paid plan, API credits or specific permissions, and may enforce its own rate limits. Check current Weavz pricing and the provider’s terms before rollout.
Connect deps.dev in minutes
Get 20,000 free action executions every month. No credit card required.