Skip to main content
Glama
Sign In
vigilai-tech

record-mcp

by vigilai-tech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to record-mcp

No user-submitted related servers found.

    Related Servers

    • proofline-mcp

      Abhishek249
      A
      license
      C
      quality
      B
      maintenance
      Enables AI agents to validate candidate data pipelines against a trusted reference, running deterministic checks and returning evidence reports through MCP.
      1
      MIT
    • Vaikora Guard MCP by Data443

      Vaikora Guard MCPofficial

      Data443
      A
      license
      Not graded
      quality
      D
      maintenance
      Enforces deterministic policies on AI agent tool calls, evaluating actions against compliance modules (SOC 2, HIPAA, GDPR, etc.) and returning ALLOW, BLOCK, or CONSTRAIN decisions with an audit trail.
      MIT

    • TARA

      hbapuram
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables users to trace regulatory rule changes to affected parties and required actions through deterministic safety gates, returning dated action plans and hash-linked evidence records. Supports 12 MCP tools over stdio or streamable HTTP for source comparison, obligation decomposition, scope assessment, planning, and evidence validation across multiple domain packs.
      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.1/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: check_trace vs. check_trace_chain differ by single- vs. multi-trace scope, list_rules vs. get_rule differ by list vs. detail, and list_frameworks covers a separate catalog entity. There are no overlapping or indistinguishable tools.

    Naming Consistency5/5

    All tool names use snake_case with a leading verb (check/list/get) and clear object nouns. check_trace_chain is a predictable extension of check_trace, and there are no mixed naming conventions.

    Tool Count5/5

    Five tools fit the checker/catalog purpose well: two validation entry points and three catalog lookup tools. Each tool earns its place with no filler or obvious thinness.

    Completeness5/5

    The surface covers single-trace checking, chain checking, rule listing/detail, and framework discovery, which are the core operations for a RECORD compliance checker. Remediation and regulatory context are also exposed through the validation and rule tools, leaving no obvious dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources