Skip to main content
Glama
awslabs

MCP Server for OSCAL

by awslabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to MCP Server for OSCAL

No user-submitted related servers found.

    Related Servers

    • 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

    • nist-mcp

      ball2jh
      A
      license
      A
      quality
      D
      maintenance
      Provides structured access to the full NIST cybersecurity catalog, including SP 800/1800 publications, security controls, CSF 2.0, and the NVD database. It enables AI assistants to search and retrieve cybersecurity standards, CVEs, and compliance guidance directly from a local SQLite index.
      20
      1
      MIT

    • Cinch MCP Server

      nirhalfon
      A
      license
      A
      quality
      B
      maintenance
      Enables MCP-compatible agents to query security checklists, protocols, and framework mappings to safely build and operate AI agents, with tools for checklist runs, protocol lookup, mapping lookup, and threat search.
      9
      CC BY-4.0

    • AWP MCP Server

      agentwebprotocol
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides tools for AI assistants to access the Agent Web Protocol (AWP) specification, validate agent.json files, and generate protocol-compliant configurations. It enables developers to integrate the AWP standard into their websites through natural language prompts and automated validation.
      4 npm
      MIT

    • dir-mcp

      agntcy
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants and IDEs to work with the AGNTCY Agent Directory, providing tools for validating, publishing, searching agent records, and navigating OASF taxonomies.
      2
      Apache 2.0
    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.0

    Scored across 40 tools

    Disambiguation5/5

    Each tool targets a distinct operation or resource: list_* for paginated child elements, query_* for document-level queries, get_* for single items, validate_* for validation, and text_search for full-text search. No two tools have overlapping purposes.

    Naming Consistency5/5

    Tools follow a consistent verb_noun pattern (e.g., list_catalogs, query_profile, get_capability). Even 'about' and 'text_search_oscal' fit the pattern. The naming is predictable and uniform across all 40 tools.

    Tool Count4/5

    40 tools is on the higher side but appropriate for the complex OSCAL domain covering multiple document types, child elements, validation, and search. Each tool earns its place; the count reflects the domain's breadth rather than redundancy.

    Completeness5/5

    The tool surface covers all major OSCAL document types with list, query, and child-element tools, plus validation, schema retrieval, documentation query, and full-text search. For a read-only server, there are no obvious gaps.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources