Skip to main content
Glama
qpulce-dev

salesforce-deployment-guard

by qpulce-dev

Related Servers

Alternatives to salesforce-deployment-guard

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables local security scanning and compliance gap analysis for code and text, detecting secrets, PII, and OWASP vulnerabilities, and assessing readiness across major frameworks like NCA, ISO 27001, NIST CSF, and SOC 2.
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables safe, local DevOps inspection through a JSON-lines server with schema validation, path isolation, and redaction, supporting read-only Git operations, Kubernetes YAML validation, Terraform plan summaries, and sanitized log analysis.
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables security review of code diffs and files in Cursor/VS Code using local rule-based analysis with the same rule IDs as CI, no cloud required.
      -
    • A
      license
      A
      quality
      A
      maintenance
      Enables AI clients to assess infrastructure-as-code deployment risk, generate incident response runbooks, review CI/CD delivery readiness, and calculate SLO error budgets through structured advisory tools. Runs locally over stdio without cloud credentials or external API calls, returning guidance for platform work, pull request review, and production readiness checks.
      12
      533 npm
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables local SOC 2 compliance work by scanning Infrastructure-as-Code, mapping findings to SOC 2 Trust Services Criteria, explaining risks in plain English, and drafting audit-ready documents without uploading files.
      16
      1
      MIT

    TDQS

    A4/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct role in the deployment-guard workflow: analyzing logs, validating manifests, reviewing permissions, and generating remediation plans. There is no overlap or ambiguity between them.

    Naming Consistency5/5

    All tool names follow the same verb_noun pattern (analyze_, validate_, assess_, build_), creating a predictable and consistent naming convention that makes it easy for an agent to infer each tool's purpose.

    Tool Count5/5

    Four tools is well-scoped for a deployment guard server. The set covers the essential phases—diagnosis, validation, risk assessment, and remediation—without unnecessary bloat or missing core functionality.

    Completeness4/5

    The four tools form a coherent pipeline from failure analysis through remediation planning. Minor gaps exist, such as no direct tool for retrieving raw deployment logs or applying fixes, but these are likely outside the server's declared guard purpose.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues