Skip to main content
Glama

Related Servers

Alternatives to specmd-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables developers to define and register MCP tools and expose them over stdio or HTTP using JSON-RPC 2.0, with schema validation and manifest discovery.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides a shared MCP SDK wrapper for building MCP servers with stdio transport, tool registration, JSON-safe responses, and environment helpers.
      43 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables CLI coding agents to read, query, create, update, delete and validate a project's spec graph through seven spec_* tools, so specs act as the ground truth for every piece of work. The tools are exposed over an MCP stdio server that resolves the workspace root from the host session.
      Apache 2.0
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP-compatible clients and agents to drive SpectraProbe's static analysis engine over stdio, exposing twelve tools for probing targets, inspecting metadata, strings, dependencies, symbols, imports, resources and JavaScript, searching evidence, creating reports, listing providers and checking analysis status.
      2
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to perform sandboxed file reads, writes, and listing, inspect credential-masked environment variables, check git status, and execute commands with strict timeouts over a clean stdio JSON-RPC channel.
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      Enables MCP clients to render Markdown to HTML, estimate page counts, verify document delivery constraints, and atomically ship documents through a zero-dependency JSON-RPC stdio server.
      4
      MIT

    TDQS

    C2.8/5.0

    Scored across 9 tools

    Disambiguation4/5

    Most tools target distinct operations (create, inspect, blackbox, trace_create, trace_update, capabilities). However, 'validate_pair' is explicitly a narrower subset of 'validate', and 'inspect' vs 'blackbox' both produce reports, causing minor confusion. Descriptions clarify the boundaries, but two overlaps remain.

    Naming Consistency3/5

    The server mixes single verbs ('create', 'validate', 'inspect') with compound snake_case names ('trace_create', 'validate_pair') and nouns ('blackbox', 'capabilities'). While all lowercase and underscore-separated, the pattern is inconsistent. It is still readable but lacks a predictable verb_noun structure.

    Tool Count5/5

    Nine tools is well within the ideal 3–15 range for a spec and trace management server. Each tool appears to earn its place, aside from one nonfunctional tool. The count is appropriate and not bloated.

    Completeness3/5

    The surface covers creation, validation, inspection, and trace lifecycle, but lacks update/delete operations for the core SPEC.md file. Additionally, 'propose_patch' is not implemented, leaving a planned patch workflow incomplete. These are notable gaps for a complete spec management lifecycle.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues