Skip to main content
Glama

Related Servers

Alternatives to fedramp-docs-mcp

No user-submitted related servers found.

    Related Servers

    • 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
    • A
      license
      Not graded
      quality
      C
      maintenance
      Model-agnostic cybersecurity MCP server for CMMC 2.0 compliance workflows with air-gapped Ollama mode.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      A local MCP server that gives AI coding assistants retrieval access to your personal knowledge base of books, standards, and docs, grounding their answers in sources you trust.
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server that acts as a governed customer-support tool, resolving questions only when the knowledge base supports a cited, grounded answer and honestly escalating everything else with provenance and evidence.
      23 PyPI
      MIT
    • F
      license
      A
      quality
      C
      maintenance
      MCP server for querying SAM.gov federal contract opportunities, providing precise search, retrieval, and attachment tools with full source traceability and explicit abstention when data is absent.
      5
      -

    TDQS

    A3.7/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: definitions, FRR sections, KSI indicators, source info, listings for FRRs and KSIs, and cross-document search. There is no overlap in functionality, making it easy for an agent to select the correct tool.

    Naming Consistency4/5

    Tool names follow a mostly consistent verb_noun pattern using snake_case (e.g., get_definition, list_frrs). The outlier is 'search' which lacks a noun suffix, but it remains clear and standard for a search tool.

    Tool Count5/5

    Seven tools is well-scoped for a documentation retrieval server focused on FedRAMP definitions, rules, and indicators. Each tool serves a clear purpose without unnecessary redundancy or missing essential operations.

    Completeness4/5

    The tool set covers retrieval (get), listing (list with filters), and search for the three document types (FRDs, FRRs, KSIs), plus source metadata. A minor gap is the absence of a dedicated list_tools for definitions, but search partially mitigates this.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues