Skip to main content
Glama

Related Servers

Alternatives to ai-security-wiki

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to assess AI-readiness and improve AI leverage through analysis tools, resources, and prompts for project scanning and remediation.
      11 npm
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Enables AI assistants to perform governed risk assessments through AIR: discover projects, upload evidence, run assessments, and retrieve structured reports.
      37
      186 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to apply organization-specific AI product governance policies through read-only tools, prompts, and resources, including risk-tier scoring, unit-economics calculations, and gated governance workflows.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Provides governed tools for evaluating proposed agent actions against policy, classifying risk, and creating structured governance and audit records, while pausing consequential steps for explicit human approval. This lets agentic workflows run under traceable, least-privilege control rather than unrestricted automation.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents and builders to run local, audit-traceable governance assessments, including an A³ scorecard, ISO/IEC 42001 and NIST evidence templates, compliance checklists, passport lookup, and sensitive-text screening.
      MIT

    TDQS

    A3.7/5.0

    Scored across 10 tools

    Disambiguation4/5

    Each tool targets a distinct step or resource: classify, scope, plan, investigate, remediate, explain, plus three lookup tools. The closest pairs (search_knowledge vs. get_risk/get_control, and investigate_risk vs. explain_finding) are explicitly separated in the descriptions (search vs. read details; investigate vs. explain). Minor residual overlap between investigate_risk and explain_finding keeps it from a 5.

    Naming Consistency5/5

    All ten tools use snake_case verb_noun form (classify_system, scope_risks, investigate_risk, get_control). get_reference/get_risk/get_control form a coherent get_* family and the action verbs clearly map to workflow stages. Only build_audit_plan adds a third noun, which is still readable and consistent.

    Tool Count5/5

    Ten tools for a multi-stage audit workflow (classify → scope → plan → investigate → remediate → explain) with three reference readers is well-scoped. No redundant or filler tools are apparent; each corresponds to a workflow step or lookup need.

    Completeness4/5

    The surface covers the full advisory lifecycle from classification through remediation proposals and explanation, and explicitly declares what it does not do (no scanning, no execution, no applied changes). The main gap is that there is no tool to record evidence/verification outcomes or update an existing audit plan, so the loop from retest back into the register is left to the calling agent.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues