vdb

Ingested from the official MCP Registry

FastDrop pulled this entry from the official MCP Registry as kr.ai.vdb/vdb and probed the endpoint. The maker did not submit it, so the outbound link is not endorsed and the description is not theirs.

If this is your server, claim the listing to edit it and take ownership. The registry index lists everything else still awaiting a probe.

Tools this endpoint exposes

Read directly from the endpoint on 27 Oct 2026. Not supplied by the maker.

• vdb_check_package

  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 PROCE

• vdb_check_packages

  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` fo

• vdb_scan_lockfile

  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, r

• vdb_lookup

  Fetch a single vulnerability by ID or alias (e.g. CVE-2024-1234, GHSA-xxxx-yyyy-zzzz, VDB-SLOP-…).

• vdb_search

  Free-text search over the VDB vulnerability corpus.

• vdb_check_mcp_server

  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 ev

• vdb_list_slopsquatting

  List packages currently flagged as slopsquatting candidates in a given ecosystem.