Skip to main content
Glama
MarkAC007

mcp-server-scf

by MarkAC007
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to mcp-server-scf

No user-submitted related servers found.

    Related Servers

    • ComplianceCow MCP Server

      ComplianceCow
      F
      license
      C
      quality
      B
      maintenance
      Enables AI agents to interact with the ComplianceCow platform to retrieve compliance insights, dashboard data, and auditable evidence through a Compliance Graph. It also supports automated remediation actions such as fixing policies and creating tickets in external tools.
      100
      13
      -

    • Security Controls MCP Server

      Ansvar-Systems
      A
      license
      A
      quality
      C
      maintenance
      Enables searching and bidirectional mapping of 1,451 security controls across 262 SCF-mapped frameworks, including ISO 27001, NIST CSF, DORA, and many others, through natural language queries.
      14
      640 PyPI
      9
      Apache 2.0

    • Fianu Compliance Intelligence

      fianulabs
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to query software supply chain compliance data, including asset status, security vulnerabilities, and evidence lineage. It allows for natural language analysis of compliance posture, policy violations, and deployment blockers across an organization.
      -

    • NIST MCP Server

      tnicholson
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides comprehensive access to NIST cybersecurity frameworks and controls, enabling AI assistants and applications to query, analyze, and manage NIST security controls through a standardized interface.
      10
      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

    A3.5/5.0

    Scored across 224 tools

    Disambiguation2/5

    With 224 tools, many surfaces overlap: reference vs org instances (get_evidence vs get_catalog_evidence), multiple work queues, several assessment/review/verdict tools, and many vendor/document/reconciliation variants. Descriptions often clarify role and required fields, but the sheer number of adjacent tools makes misselection likely.

    Naming Consistency5/5

    All tools use the scf_ prefix with snake_case verb_noun naming (list_, get_, create_, update_, delete_, etc.). Variants like bulk_, batch_, trigger_, preview_, and review_ remain predictable and semantically consistent.

    Tool Count1/5

    224 exposed tools is an extreme mismatch for a single MCP server; it far exceeds the typical 3–15 scoped tools and forces agents to navigate an enormous surface. Many tools could be consolidated or grouped into resources.

    Completeness4/5

    The surface broadly covers a massive GRC domain: controls, frameworks, risks, evidence, vendors, documents, engagements, teams, assignments, comments, reconciliation, and webhooks, with lifecycle operations for most entities. Some minor lifecycle gaps exist, such as no delete for vendors/systems, but agents can usually work around them.

    Maintenance

    ActivityActive
    ResponsivenessWithin a week

    Resources