Skip to main content
Glama
DevInder1

tridentchain-mcp on PyPI

by DevInder1
OverviewSchemaSourceRelated ServersDiscussionsAdmin

Related Servers

Alternatives to tridentchain-mcp on PyPI

No user-submitted related servers found.

    Related Servers

    • deptrust by clidey

      deptrustofficial

      clidey
      A
      license
      Not graded
      quality
      A
      maintenance
      deptrust is a CLI that checks package versions for known vulnerabilities across npm, PyPI, crates.io, Go modules, RubyGems, NuGet, Maven, Packagist, pub.dev, CocoaPods, Hex.pm, Hackage, GitHub Actions, and more. It runs locally as a CLI and as an MCP server. It calls public package registry and OSV APIs directly; there is no hosted deptrust service to trust or configure.
      156 npm
      61
      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
      30 npm
      1
      MIT

    • GuardianMCP

      Kalvisan
      A
      license
      A
      quality
      C
      maintenance
      Automatically scans project dependencies (npm, Composer) for security vulnerabilities using the OSV.dev database, providing real-time alerts and detailed remediation guidance directly in your IDE.
      1
      9 npm
      1
      MIT
    • @guardbee/mcp-dependency-auditor by GuardBee

      @guardbee/mcp-dependencyofficial

      GuardBee
      A
      license
      Not graded
      quality
      F
      maintenance
      Enables auditing npm, pip, and other package dependencies for known CVEs via the OSV database, with tools to scan manifests, query individual packages, and integrate into CI/CD workflows.
      99 npm
      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.3/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: scan_project for project-only dependencies, scan_full for comprehensive coverage including system and IDE extensions, and validate_after_patch for post-patch verification. Descriptions explicitly differentiate use cases.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun snake_case pattern: scan_project, scan_full, validate_after_patch. The naming is predictable and descriptive.

    Tool Count4/5

    With 3 tools, the server is minimal but well-scoped for its vulnerability scanning and validation domain. Each tool earns its place, though the count is on the lower end.

    Completeness4/5

    The server covers the core workflow: scanning project or full system and validating fixes. Minor gaps exist, such as lacking a tool to configure output paths or list past scans, but the primary use cases are handled.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources