Skip to main content
Glama
SureshKhemka

constraints-registry-mcp

by SureshKhemka

Related Servers

Alternatives to constraints-registry-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that provides CLI coding agents with persistent decision memory, codebase dependency-graph awareness, plan validation against architectural constraints, and a self-bootstrapping constraints.md file.
      7 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Serves coding agents with project-specific knowledge (decisions, conventions, constraints) over MCP and provides verification verdicts on whether code still complies.
      365 npm
      AGPL 3.0
    • F
      license
      A
      quality
      C
      maintenance
      MCP server that exposes pre-extracted facts about code behavior, design decisions, and assumptions to AI agents, saving time and tokens by avoiding direct source file reading.
      6
      -

    TDQS

    A4.2/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: describe_scope discovers valid scope values, get_constraints retrieves constraints, and validate checks artifacts. No overlap or ambiguity.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern: describe_scope, get_constraints, validate. The pattern is predictable and clear.

    Tool Count5/5

    Three tools are well-scoped for a constraints registry: discover vocabulary, retrieve constraints, and validate. Each tool earns its place without unnecessary bulk.

    Completeness4/5

    The set covers the core workflow (discover, fetch, validate). Minor gap: no explicit tool to list all constraint definitions without scope filtering, but the design intentionally omits scope-agnostic retrieval.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues