Skip to main content
Glama
0pstech

kr.ai.vdb/vdb

by 0pstech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

Related Servers

Alternatives to kr.ai.vdb/vdb

No user-submitted related servers found.

    Related Servers

    • pkg-oracle

      julian-martin89
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that verifies npm and PyPI packages before installation, checking for existence, known vulnerabilities, OpenSSF scorecard, and typosquatting, returning an ALLOW/WARN/BLOCK verdict.
      MIT

    • freshdeps-mcp

      SolvoHQ
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that checks npm and PyPI package health, providing maintenance signals, version info, CVE counts, and alternative suggestions.
      MIT

    • VulnPilot

      arojit
      A
      license
      A
      quality
      B
      maintenance
      An MCP server that gives AI assistants the ability to check open-source packages for vulnerabilities, enrich findings with real-world exploit intelligence, and statically analyse whether vulnerable code is actually reachable in your project.
      3
      1
      Apache 2.0

    • GhostFree

      shane-js
      A
      license
      A
      quality
      B
      maintenance
      A local MCP server that scans repository dependencies for known vulnerabilities (CVEs) using OSV.dev, enriches findings with NVD and CISA KEV data, and supports triage, remediation, and accepted risk management directly from an AI coding assistant.
      6
      30 npm
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.9/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: single vs bulk package checks, lockfile scanning, vulnerability lookup vs search, MCP server vetting, slopsquatting listing, harden analysis, post-fix verification, and VEX generation. Even the two checking tools are cleanly separated by input cardinality and workflow stage. No ambiguity about which tool to select for a given task.

    Naming Consistency5/5

    All tool names follow the consistent `vdb_` prefix with snake_case verb_noun or verb patterns (e.g., check_package, scan_lockfile, harden_verify). The naming makes the action and target predictable across the entire set, with no style mixing or vague verbs.

    Tool Count5/5

    Ten tools is well within the ideal range for a vulnerability database and supply-chain security server. Each tool earns its place by covering a distinct stage—package vetting, bulk checks, lockfile analysis, lookup/search, MCP server risk, and remediation—without redundant or filler tools.

    Completeness5/5

    The tool surface provides full lifecycle coverage: check packages, scan lockfiles for transitive risk, look up and search vulnerabilities, vet MCP servers, list slopsquatting candidates, run reachability analysis, verify fixes, and generate VEX documents. There are no obvious gaps or dead ends for the stated domain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources