Skip to main content
Glama
goklab

guardvibe

by goklab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to guardvibe

No user-submitted related servers found.

    Related Servers

    • MCP Shield

      rob925
      A
      license
      C
      quality
      B
      maintenance
      Security scanner and MCP server that catches dangerous patterns in MCP servers and AI agent projects, such as leaked secrets, shell execution, and prompt-injection text. Runs as both a CLI and MCP server with CI-friendly severity gates.
      2
      1
      MIT

    • supership-scan

      andysalvo
      A
      license
      Not graded
      quality
      F
      maintenance
      Predeploy security scanner for AI-generated code. 80+ vulnerability patterns across secrets, auth, injection, config, Supabase, and logging. Runs locally, code never leaves your machine. Optional x402 witnessed attestation.
      44 npm
      Apache 2.0

    • mcp-heimdall

      caglarbozkurt
      A
      license
      Not graded
      quality
      A
      maintenance
      Security scanner for MCP servers — vet an MCP before you wire it into an agent. Detects prompt-injection, credential exfiltration (via taint analysis), RCE, and supply-chain risks, and catches cross-server exfil chains no single server reveals. Zero-dependency local CLI, SARIF output, CI-gateable, no account.
      42 npm
      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.
      14
      19 npm
      16
      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.2/5.0

    Scored across 21 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose, with descriptions that effectively differentiate between scanning inline code, files, directories, git history, prompts, configs, and MCP-specific configs. Overlaps are minimal and clarified (e.g., check_code vs scan_file).

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern (e.g., audit_config, scan_file, fix_code, verify_remediation). Naming is predictable and logical, with no mixing of conventions like camelCase or snake_case.

    Tool Count4/5

    21 tools is on the higher end but appropriate given the broad domain of security auditing. Each tool addresses a specific need (e.g., pre-code, config, dependencies, git history), and none feel redundant. Slightly heavy but justified.

    Completeness5/5

    The tool set covers the full security lifecycle: pre-code analysis (secure_prompt), runtime checks (check_command, scan_staged), scanning (scan_directory, scan_file, scan_secrets_history), fixing (fix_code, secure_this), verification (verify_fix, verify_remediation), compliance, and workflow guidance. No obvious gaps are present.

    Maintenance

    ActivitySlowing
    ResponsivenessUnresponsive

    Resources