Skip to main content
Glama
Keel-GRC

mcp-keelgrc

Official
by Keel-GRC
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to mcp-keelgrc

No user-submitted related servers found.

    Related Servers

    • @konsulto/mcp by konsulto

      @konsulto/mcpofficial

      konsulto
      A
      license
      A
      quality
      D
      maintenance
      MCP server that enables Claude Code to drive the Konsulto cybersecurity audit platform from the CLI, including reading and writing findings, managing evidence, and handling scope and assets.
      19
      11 npm
      1
      MIT

    • compliance-intelligence

      GJB65
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for a compliance knowledge graph covering 686 frameworks, 21,696+ controls and 310K+ cross-framework mappings, with tools to map controls between two standards and run coverage analysis. Node and Python implementations over stdio, plus a hosted streamable HTTP endpoint.
      MIT

    • tardigrade-shield

      Blu5Morpheus
      A
      license
      Not graded
      quality
      C
      maintenance
      Model-agnostic cybersecurity MCP server for CMMC 2.0 compliance workflows with air-gapped Ollama mode.
      MIT
    • octopilot-mcp by octopilot

      octopilot-mcpofficial

      octopilot
      F
      license
      A
      quality
      D
      maintenance
      Model Context Protocol (MCP) server for Octopilot — enables AI agents to detect, generate, build, and wire up new repositories end-to-end using the Octopilot CI/CD toolchain.
      7
      -
    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

    A3.9/5.0

    Scored across 18 tools

    Disambiguation5/5

    Each tool maps to a distinct resource and action; there is no meaningful overlap between list, create, delete, and upsert operations. The few convenience names like whoami and readiness are also unambiguous.

    Naming Consistency4/5

    All tools share the keel_ prefix and mostly follow a verb_noun pattern such as list_risks, create_task, and delete_webhook. keel_whoami and keel_readiness are minor deviations from that pattern.

    Tool Count4/5

    18 tools is slightly above the typical well-scoped range, but the broad Keel GRC domain of risks, vendors, tasks, policies, evidence, people, and webhooks justifies the count. Each tool appears to serve a purpose with no obvious filler.

    Completeness3/5

    The set is read-and-create heavy but lacks update and delete operations for core entities like tasks, risks, vendors, and policies, which are common lifecycle actions in a GRC workflow. Evidence file upload is also unsupported, requiring fallback to external tools.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources