All servers · Security · Build & deploy
kr.ai.vdb/vdb
kr.ai.vdb/vdb · v0.2.6
Measured by MCP Station
| Last check | Reachable |
|---|---|
| Checked at | — |
| Check success 7 / 30 days | — |
| First-try success 30 days | — |
| Median response | — |
| Lookups 30 days | — |
| Authentication | No auth |
| MCP version | 2025-06-18 |
| Rank score | — |
| Declared risk | Not declared (tools carry no read/destructive hints) |
| Capabilities declared | experimental, tools |
| Tool definitions | 7 tools · with description 100% · input schema is an object 100% · read/destructive hints 0% |
Description written by the publisher, not verified
Check packages for CVEs, slopsquatting, and CISA KEV before your AI agent installs them.
Connect
streamable-http · https://vdb.ai.kr/mcp
claude mcp add --transport http vdb https://vdb.ai.kr/mcp{
"mcpServers": {
"vdb": {
"url": "https://vdb.ai.kr/mcp"
}
}
}Tools as reported by the server
vdb_check_packageBEFORE 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 undvdb_check_packagesBulk-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 corrvdb_scan_lockfileBEFORE 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 mvdb_lookupFetch a single vulnerability by ID or alias (e.g. CVE-2024-1234, GHSA-xxxx-yyyy-zzzz, VDB-SLOP-…).vdb_searchFree-text search over the VDB vulnerability corpus.vdb_check_mcp_serverBEFORE 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_list_slopsquattingList packages currently flagged as slopsquatting candidates in a given ecosystem.
Repository · Website · JSON · Text for agents · Registry updated 2026-10-02