Skip to main content
Glama
compliance-aiops

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
      73 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      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.
      696 npm
      3
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides a typed compliance model and governance runtime that lets AI draft policies, assess controls, find framework gaps, and build verifiable audit trails across frameworks like ISO 27001:2022, SOC 2, GDPR, NIST CSF 2.0, and HIPAA. Every write is gated by a server-side verifier and human approval, producing a tamper-evident record.
      Apache 2.0
    • A
      license
      A
      quality
      C
      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
    • A
      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.
      AGPL 3.0

    TDQS

    A3.7/5.0

    Scored across 19 tools

    Disambiguation4/5

    Most tools target clearly distinct objects/actions (evidence bundles, audit chains, reports, undo tokens), and descriptions cross-reference each other well. Minor overlaps remain: export_bundle(fmt=oscal) vs oscal_assessment_results both produce OSCAL from a bundle, and coverage_summary vs gap_analysis are complementary per-framework views that could be confused at a glance.

    Naming Consistency4/5

    All names use consistent snake_case with readable, domain-specific terms. Verb style is mixed (sign_bundle, verify_bundle vs coverage_summary, gap_analysis, approval_report) and a few are noun phrases, but the convention is never chaotic.

    Tool Count4/5

    19 tools is slightly above the typical well-scoped band, but the domain is broad (bundle lifecycle, audit querying, verification, reporting, undo, scheduling) and each tool maps to a distinct capability. Nothing looks like filler.

    Completeness4/5

    The surface covers the core lifecycle: generate, sign, verify, export (markdown/csv/json/OSCAL), list, coverage/control/gap analysis, audit query, chain verification, approval/exceptions reports, and undo list/apply. Gaps are minor — no bundle retrieval-by-id, retention/prune, or bundle diff/compare operations.

    Maintenance

    ActivityActive
    ResponsivenessNo recent community issues