Skip to main content
Glama
novadyne-hq

VulnFeed

by novadyne-hq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to VulnFeed

No user-submitted related servers found.

    Related Servers

    • 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

    • locklens

      BARMPlus
      A
      license
      B
      quality
      D
      maintenance
      Audits package lockfiles for vulnerabilities, supporting npm, yarn, and pnpm. Runs via CLI or as an MCP server over stdio.
      1
      1 npm
      83
      MIT

    • 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
      26 npm
      1
      MIT

    • tooltrust-mcp

      AgentSafe-AI
      A
      license
      Not graded
      quality
      A
      maintenance
      Scans MCP servers for prompt injection, supply chain attacks, excessive permissions, and code execution risks. Includes an offline blacklist that catches known-compromised packages like LiteLLM 1.82.7/1.82.8 and Trivy with zero latency.
      19
      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

    A4.1/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: scanning lockfiles vs. whole projects, looking up packages vs. CVEs, and monitoring lifecycle actions like register, update, check, list, and unmonitor. Even the scanning tools are clearly separated by scope (single lockfile vs. project directory).

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern: scan_lockfile, scan_project, check_package, lookup_cve, monitor_project, update_deps, check_alerts, list_monitored, unmonitor_project. The pattern makes the set predictable and easy to navigate.

    Tool Count5/5

    Nine tools is well-scoped for a vulnerability scanning and monitoring server. Each tool earns its place, covering scanning, lookup, registration, alerting, updating, listing, and removal without unnecessary duplication.

    Completeness4/5

    The tool surface covers the core lifecycle well: scan, lookup, monitor, update baselines, check alerts, list, and unmonitor. A minor gap is the lack of a direct way to retrieve the full stored vulnerability baseline for a monitored project, though scanning again or check_alerts can work around it.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources