An astronaut overseeing a futuristic data hub

Connect Google Depsdev Security Hacker to ChatGPT and Claude

Set it up once and it works in ChatGPT, Claude, Cursor, and any other client you love. It all runs safely in the background, so you can relax and focus on what really matters. Turn your AI agent into a specialized DevSecOps auditor.

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

ChatGPTClaudeCursorPerplexityGeminiMicrosoft CopilotRaycastMeta AI

Your AI does the work. We keep it safe and sound.

No other AI tool gives you this. Your workflow runs in the client you already love, your account stays protected, and you decide what the agent can and cannot do. It is the whole reason to make the switch.

Each Connector lives inside our infrastructure, the same place where your workflow runs. The three things below are already part of it, working quietly in the background so you never have to think about them. Nothing to add, nothing to set up, nothing to worry about.

A futuristic MCP client docking bay
V8 Isolate01

Each Connector runs inside its own sealed environment.

Each Connector runs inside its own sealed V8 runtime — no access to your files, your system, or other servers. A Connector never sees past its own request.

Kill Switch02

One switch stops every agent. Instantly.

One action deactivates every Connector, revokes every token, and ends every session at once. AI Governance keeps the record.

FinOps per User03

Spending limits that pause instead of surprise.

Every user keeps their own connections and credentials, isolated from everyone else. Anything that would cross your spending limit is held for your approval, not billed.

Three controls, built into the layer your AI connects through.

Curated set · 4 capabilities

We ship only the actions that matter.

Capability set01 / 01

01-04

4 capabilities in this set.

Part of 4 available through Google Deps.dev.

  1. 01

    Analyze dependency

    This capability uses Google deps.dev to analyze an open-source package for security advisories and OSSF scorecard data. It supports npm, pypi, go, cargo, maven, and nuget.

  2. 02

    Get transitive dependencies

    This capability hunts for hidden security threats by mapping the entire transitive dependency tree of a specific package.

  3. 03

    Get vulnerability details

    This capability pulls specific exploit details, severity levels, and affected package versions for any given CVE or GitHub Security Advisory (GHSA).

  4. 04

    Analyze github repository

    This capability performs a full security and governance audit of a GitHub repository using OSSF Scorecards.

Real work

What teams actually run

01

Supply Chain Defense

Your agent maps the entire dependency tree to find malware or unpatched flaws in indirect libraries.

02

New Package Verification

Before adding a library, your agent audits the package for known CVEs and governance scores.

03

Vulnerability Response

When a new CVE is announced, your agent identifies exactly which package versions are affected.

04

Repo Health Checks

Your agent evaluates if a GitHub project follows security best practices like code reviews.

Automate a task

Put Google Deps.dev to work on one thing.

Step-by-step automations your AI runs through this Connector: the workflow, the prompts to start with, and the exact capabilities behind each move.

One connector, every AI

Google Deps.dev works with the most popular AI clients.

These are the most popular clients, each with a step-by-step guide: one link, set up once, with governance and visibility built in. And because everything runs on the MCP standard, the same connection also works in any other compatible client — nothing to rebuild.

Building your own app? The connector is yours to use.

You don't need a client to put Google Deps.dev to work: the same hosted connection plugs into your own applications and agent code, with the same governance on every request. Build with it, chat with it — one connection for both.

Observed, not estimated

991ms average. Fast in production.

Google Deps.dev is checked daily against the live service.

Daily averagePeak 1300ms
Oct 3Today
Fastest day
767ms
Slowest day
1300ms
14-day trend
Slowing+9%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 4 capabilities arrive ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of Google Deps.dev, so you can see the experience inside your AI.

It does not authenticate your account with Google Deps.dev. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

Google Deps.dev Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_8l27TKQqvxDGA8IDc4bvKGYYUzioU5v5qb8XJydr/mcp

Claude Desktop

Follow the steps below to connect in seconds.

  1. 1In Claude Desktop, open Settings → Connectors.
  2. 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
  3. 3Click Add and start a new chat — Google Deps.dev capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "google-depsdev-security-hacker-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_8l27TKQqvxDGA8IDc4bvKGYYUzioU5v5qb8XJydr/mcp"
    }
  }
}
  • Claude
  • ChatGPT
  • Cursor
  • VS Code
  • Windsurf
  • Claude Code
  • JetBrains
  • Cline

Step-by-step instructions for each client are in the guide. How to connect

Guided setup for Claude? Set up Google Deps.dev in Claude and other AIs

See all the AI clients this connector works with ↑

Who it's for

Built for the work Google Deps.dev owners hand off.

This MCP is built for engineers who need to automate security checks within their development lifecycle.

  • 01

    DevSecOps Engineer

    Hands off repetitive dependency scanning and supply chain audits to the agent.

  • 02

    Backend Developer

    Uses the agent to quickly verify if a new library is safe to add to the project.

  • 03

    Security Researcher

    Leverages the agent to pull deep technical details on specific CVEs and package impacts.

FAQ

Questions Google Deps.dev owners ask.

  • 01

    Does this MCP require an API key?

    No, this MCP does not require any authentication to use the Google deps.dev API.

  • 02

    Which package managers are supported?

    The MCP supports npm, PyPI, Cargo, Go, Maven, and NuGet.

  • 03

    Can it check GitHub repositories?

    Yes, it can perform a full security and governance audit of any GitHub repository using OSSF Scorecards.

  • 04

    What is an OSSF Scorecard?

    It is a security framework used to check if a repository enforces practices like code reviews, fuzzing, and signed releases.

  • 05

    How does it find hidden threats?

    It uses the get_transitive_dependencies capability to look past the primary package and analyze the entire tree of sub-dependencies.

  • 06

    Do I need an API key for this?

    No! The Google deps.dev API is completely free and public. Just connect the MCP and your AI agent can start auditing immediately.

Connect Google Deps.dev to Claude, Cursor, ChatGPT & more