Skip to main content
Glama
AIops-tools

compliance-aiops

Related Servers

Alternatives to compliance-aiops

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to sign decisions with post-quantum cryptographic proofs and maintain secure audit trails for compliance. It provides tools for stamping events, verifying chain integrity, and exporting audit data across industries like finance and healthcare.
      4
      31 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Integrates authoritative security compliance frameworks (ISO 27001, NIST 800-53, OWASP ASVS, NIST SSDF) into AI-assisted development, offering control lookups, cross-framework mappings, build-time guardrails, and automated audit evidence generation.
      152 npm
      3
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Provides cryptographic signing and verification for AI decisions to generate verifiable, Ed25519-signed receipts for compliance and auditing. It automatically maps AI actions to regulatory frameworks like HIPAA and SOX with high-performance, sub-3ms signing.
      4
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      An MCP-powered compliance copilot for SaaS stacks, enabling structured audit workflows including stack detection, module wiremapping, implementation directives, code verification, and security/infrastructure/legal readiness gates.
      -
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables authorized compliance verification and security auditing through natural language, bridging AI assistants with industry-standard security tools for enterprise audits.
      24
      -

    TDQS

    A3.6/5.0

    Scored across 19 tools

    Disambiguation4/5

    Most tools have clearly distinct resources and actions, especially in the bundle lifecycle (generate, list, verify, sign, export). The main ambiguity risk is the cluster of framework readouts—coverage_summary, gap_analysis, control_evidence—and the overlap between exceptions_report, approval_report, and query_audit_events, but the descriptions make the intended use clear.

    Naming Consistency3/5

    All names are snake_case and readable, with a clear list_* group and verb_noun actions. However, report-style tools use noun phrases like coverage_summary, exceptions_report, gap_analysis, and oscal_assessment_results, so the set mixes conventions rather than following one predictable verb_noun pattern.

    Tool Count3/5

    With 19 tools, the surface is on the heavy side of the typical well-scoped range. Most tools map to a distinct lifecycle step, but several report tools could arguably be folded into query_audit_events or export_bundle, making the count feel slightly padded.

    Completeness4/5

    The server covers the core compliance evidence workflow end-to-end: discover audit sources, query events, analyze gaps, generate/list/verify/sign/export bundles, schedule generation, and apply undos. Minor gaps include the lack of a control catalog/detail endpoint and no bundle deletion or rotation, but these do not block primary workflows.

    Maintenance

    ActivityActive
    ResponsivenessNo issues