Next free-source huntWe check for new free data every weekday.
Cyber ThreatMCP serverFirst audited Nov 13, 2026

kr.ai.vdb/vdb

Check packages for CVEs, slopsquatting, and CISA KEV before your AI agent installs them.The vendor's description, from its MCP Registry listing.

Passed, with 1 warningAudited Nov 13, 2026
  • Warning: 7 of 7 tools do not say whether they can change things.

Nothing failed, but there is something to know or fix. Public audit: we connect as an AI client would, list the tools and check what they say. We do not run them. How we audit

Does it work?
YesConnected in 250 ms.
Sign-up?
None neededIt answered without any account or key.
Can it change things?
Doesn't sayIts tools do not say whether they only read, so treat them as able to change things.
Endpointhttps://vdb.ai.kr/mcp

Source code Website Streamable HTTP · protocol 2025-11-25 · server version 0.2.10

What we checked, the evidence, and the tools it offers.

What we checked

Security

  • Passed: Connections are encrypted (HTTPS).

  • Passed: No hidden instructions found in tool text.

Safety labels

  • Warning: 7 of 7 tools do not say whether they can change things.

    MCP lets a server label each tool as read-only or destructive, so clients can ask the user before risky calls. Unlabelled tools are treated as able to change things.

    • vdb_check_package
    • vdb_check_packages
    • vdb_scan_lockfile
    • vdb_lookup
    • vdb_search
    • vdb_check_mcp_server
    • vdb_list_slopsquatting

Tools

  • Passed: 7 tools listed.

  • Passed: Every tool describes its inputs with a valid schema.

Protocol

  • Passed: The MCP handshake works (Streamable HTTP).

  • Passed: Protocol version 2025-11-25 (latest).

  • Passed: Unknown requests are refused.

Connection

  • Passed: The server responds.

Tools (7)

As the server describes them. The labels are the server's own: it says whether each tool only reads or can change things.

  • 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 PROC…Doesn't say
  • vdb_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` f…Doesn't say
  • vdb_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,…Doesn't say
  • vdb_lookupFetch a single vulnerability by ID or alias (e.g. CVE-2024-1234, GHSA-xxxx-yyyy-zzzz, VDB-SLOP-…).Doesn't say
  • vdb_searchFree-text search over the VDB vulnerability corpus.Doesn't say
  • 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 e…Doesn't say
  • vdb_list_slopsquattingList packages currently flagged as slopsquatting candidates in a given ecosystem.Doesn't say

Audit history

  1. Nov 13Warnings

What we sent

Every request in this audit, with the answer and how long it took. We never send credentials and never call a tool.

RequestAnswerTime
initializeHTTP 200250 ms
initializedHTTP 202515 ms
tools/listHTTP 20084 ms
unknown-methodHTTP 20075 ms

Run this server, or disagree with the result?

Fix the issue and it shows in the next weekly audit, or email us to ask for a re-audit or to dispute a finding. Read how we audit for what each check means.