Skip to main content
Glama
Thezenmonster

agentscore-mcp-server

by Thezenmonster
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to agentscore-mcp-server

No user-submitted related servers found.

    Related Servers

    • MCP Trust Layer

      pst291291
      A
      license
      Not graded
      quality
      D
      maintenance
      Security scanner and trust verification layer for MCP ecosystem, enabling users to scan PyPI packages and GitHub repos for secrets, dangerous patterns, and prompt injection vectors, and compare security scores.
      MIT

    • 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

    • depguard

      mopanc
      A
      license
      A
      quality
      A
      maintenance
      MCP security server for AI coding agents. 12 tools: pre-install guardian, vulnerability audit, supply-chain attack detection via static code analysis, and CycloneDX 1.6 SBOM generation. Zero runtime dependencies.
      15
      16 npm
      15
      Apache 2.0
    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/5.0

    Scored across 8 tools

    Disambiguation4/5

    Most tools have distinct purposes: scanning, checking verdicts, monitoring, policy enforcement, etc. However, 'install_policy_gate' and 'generate_policy_gate_setup' are closely related (generate vs write workflow), which could cause misselection. Also, 'check_abuse' and 'get_verdict' both return trust-related info but from different sources, which is fine.

    Naming Consistency4/5

    Tools use a consistent verb_noun pattern: check_abuse, check_exposure, generate_policy_gate_setup, etc. The only minor inconsistency is 'install_policy_gate' where 'install' could be seen as more specific than 'generate', but still follows the pattern. No mixing of camelCase or other styles.

    Tool Count5/5

    8 tools is appropriate for an MCP package security server. Each tool covers a core function: scanning, verdict, monitoring, abuse check, exposure analysis, repo check, and policy gate generation/installation. Neither too few nor too many.

    Completeness4/5

    The tool set covers key lifecycle operations: scan, get verdict, monitor, check abuse, check exposure, and policy enforcement (generate+install). Missing tools could include updating a verdict or removing a policy gate, but the core workflow is well-covered.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources