Skip to main content
Glama
3ii-factory

spec-drift-mcp

by 3ii-factory
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to spec-drift-mcp

No user-submitted related servers found.

    Related Servers

    • agentseed

      Morningstar202604
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents to enforce spec-driven development and verify code before it is marked done, using six tools that catch invented APIs, scan for hallucinated content, check plugin conformance, sandbox-run tests, validate schemas, and record audit evidence.
      771 npm
      8
      PolyForm Noncommercial 1.0.0

    • MCP Contractor

      adaniki-dev
      A
      license
      Not graded
      quality
      D
      maintenance
      A contract linter for AI agents that uses structured YAML contracts to define dependencies, business rules, and exports, enabling agents to work without breaking project conventions.
      11 npm
      MIT

    • Checkride

      siqah
      A
      license
      A
      quality
      B
      maintenance
      Enables AI coding agents to run fast, sandboxed pre-flight validation—tests, type-checking, linting, security audits, Git safety scans, and fix suggestions—before committing or pushing code, with instant caching and optional Docker isolation.
      10
      12 npm
      MIT

    • Carrot AI PM

      talvinder
      A
      license
      D
      quality
      D
      maintenance
      Spec-driven development tool for AI coding assistants that generates specs, validates code compliance, and provides actionable feedback.
      11
      29
      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.9/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clear, distinct purpose: listing specs, explaining a spec, and checking drift. No overlap or ambiguity.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with underscores: list_specs, explain_spec, check_drift.

    Tool Count4/5

    Three tools is minimal but appropriate for the focused domain of spec drift detection. Each tool is essential and well-scoped.

    Completeness5/5

    The set covers the full workflow: list available specs, get detailed spec, and check for drift. No obvious missing operations for the stated purpose.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources