Skip to main content
Glama
SamuelDudley

ism-mcp

by SamuelDudley
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to ism-mcp

No user-submitted related servers found.

    Related Servers

    • mcp-keelgrc by Keel-GRC

      mcp-keelgrcofficial

      Keel-GRC
      A
      license
      A
      quality
      B
      maintenance
      A Model Context Protocol (MCP) server for Keel. Point any MCP client (Claude Desktop, Claude Code, Cursor) at it and drive your compliance program in natural language: "what's my ISO 27001 readiness?", "list controls still in gap", "open a task to rotate our TLS certs."
      18
      178 npm
      MIT

    • turva-mcp

      erekola
      A
      license
      Not graded
      quality
      A
      maintenance
      Read-only MCP server that answers questions about turva.dev from its published data. Five tools return JSON: the service catalog with prices, contact and operator details, engagement principles and dated agent-readiness and security evidence with verification links. Connect over Streamable HTTP. You need no API key. The server does not scan other websites or run audits.
      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

    • purify-feeds-mcp

      eason4kim-rocket
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for querying live CISA KEV, EPSS, and enriched vulnerability feeds with full provenance. Enables natural-language access to auditable security-intelligence data from Claude Desktop and other MCP clients.
      MIT
    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

    A4.5/5.0

    Scored across 17 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose: discovery, coverage management, version diffing, listing by various facets, and database queries. No two tools overlap in functionality.

    Naming Consistency5/5

    All tool names follow the consistent pattern 'ism_' prefix followed by a descriptive verb_noun or verb phrase in snake_case (e.g., ism_applicable, ism_coverage_gaps, ism_list_topics). No mixing of conventions.

    Tool Count5/5

    With 17 tools, the server covers the domain of ISM control discovery, coverage management, versioning, and listing without being excessive. Each tool fills a specific role with no redundancy.

    Completeness4/5

    The tool set covers discovery, search, coverage CRUD (create, read, update), version diffing, and history. A minor gap is the lack of an explicit delete tool for coverage entries, but the 'not-applicable' status may compensate.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources