Skip to content
Weavz
Menu
OSV.dev

OSV.dev MCP integration

Open Source Vulnerabilities API for querying package, commit, and vulnerability records.

Sign in and add OSV.dev in Apps. No OSV.dev account is required.

4 tools
Use withChatGPTClaudeClaude CodeCursorCodexMCP clientsSetup guide

Tools

Name
query_package_version

Query OSV vulnerabilities for a package name and optional version.

query_commit

Query OSV vulnerabilities for a source commit hash.

query_batch

Query OSV vulnerabilities for multiple package versions or commits. Provide the official querybatch JSON body.

get_vulnerability

Get one OSV vulnerability record by OSV ID.

Quick Start

TypeScript
import { WeavzClient } from '@weavz-io/sdk'

const weavz = new WeavzClient({ apiKey: 'wvz_...' })

const result = await weavz.actions.execute('osv-dev', 'query_package_version', {
  workspaceId: '550e8400-e29b-41d4-a716-446655440000',
  integrationAlias: 'osv-dev',
  input: { /* ... */ },
})

Related Integrations

Works well with

Frequently Asked Questions

Is there a OSV.dev MCP server through Weavz?

Yes. Add the OSV.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 4 OSV.dev actions.

What can an AI agent do with OSV.dev?

Available actions include Query Package Version, Query Commit, Query Batch, Get Vulnerability. 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 OSV.dev to Claude or ChatGPT?

Use a compatible remote MCP client, add the Weavz connector and choose a workspace. Add OSV.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 OSV.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 OSV.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 OSV.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 OSV.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 OSV.dev in minutes

Get 20,000 free action executions every month. No credit card required.