Skip to content

kr.ai.vdb/vdb

by vdb.ai.kr · remote · local (pypi) · no sign-in to list tools · v0.2.6 · published by kr.ai.vdb

Check packages for CVEs, slopsquatting, and CISA KEV before your AI agent installs them.

Changes · 4
CompareRegistry entry

7 tools: 4 change things and 3 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http vdb https://vdb.ai.kr/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

7 tools

Changes things 4Claude Code: ask
  • vdb_check_mcp_serverBEFORE recommending a community/unofficial MCP server, check it here.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    BEFORE recommending a community/unofficial MCP server, check it here. Scope risk is evaluated independently of advisory risk — an unvetted publisher asking for shell or filesystem access is refused even with a clean record. Follow the returned `agent_action`.
  • vdb_check_packageBEFORE recommending or installing any package, check it here.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    BEFORE recommending or installing any package, check it here. The response carries `agent_action`: REFUSE (do not add it — relay the `because` text to the user), CONFIRM (ask the user first), or PROCEED. A failed or rate-limited call also answers REFUSE; never proceed unchecked. Also returns the underlying advisories, slop risk, and KEV status as supporting data.
  • vdb_check_packagesBulk-check several packages in one call — always prefer this over repeated vdb_check_package.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Bulk-check several packages in one call — always prefer this over repeated vdb_check_package. Each result carries its own `agent_action` (REFUSE / CONFIRM / PROCEED) plus a top-level `agent_action` for the batch. Follow them; relay `because` when refusing. Send names EXACTLY as written — do not correct a typo first, the call is the typo test.
  • vdb_scan_lockfileBEFORE merging, scan the resolved lockfile.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    BEFORE merging, scan the resolved lockfile. Checking the packages someone chose misses the transitive ones nobody did — which is usually where the risk is. Pass the file contents (package-lock.json, requirements.txt, uv.lock, go.sum, Cargo.lock, a CycloneDX SBOM, …). Returns `agent_action`: REFUSE means do not merge.
Only reads 3Claude Code: allow
  • vdb_list_slopsquattingList packages currently flagged as slopsquatting candidates in a given ecosystem.No findings

    Why it is in this group

    • The name "vdb_list_slopsquatting" says "list": a word for reading.
    Description, as the server wrote it
    List packages currently flagged as slopsquatting candidates in a given ecosystem.
  • vdb_lookupFetch a single vulnerability by ID or alias (e.g.No findings

    Why it is in this group

    • The name "vdb_lookup" says "lookup": a word for reading.
    Description, as the server wrote it
    Fetch a single vulnerability by ID or alias (e.g. CVE-2024-1234, GHSA-xxxx-yyyy-zzzz, VDB-SLOP-…).

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 0.2.6. Values in angle brackets are yours to fill in.

claude mcp add --transport http vdb https://vdb.ai.kr/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__vdb__vdb_lookup",
      "mcp__vdb__vdb_search",
      "mcp__vdb__vdb_list_slopsquatting"
    ],
    "ask": [
      "mcp__vdb__vdb_check_package",
      "mcp__vdb__vdb_check_packages",
      "mcp__vdb__vdb_scan_lockfile",
      "mcp__vdb__vdb_check_mcp_server"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as vdb. Review it before you use it.