Skip to main content
Glama
prathamesh-git9

mcp-servers (Six production-minded MCP servers)

Related Servers

Alternatives to mcp-servers (Six production-minded MCP servers)

No user-submitted related servers found.

    Related Servers

    • A
      license
      C
      quality
      C
      maintenance
      An MCP execution layer that lets capable AI models safely control a developer workstation for file edits, terminal and process execution, Git operations, language-server analysis, browser and Windows UI automation, media processing, job/resource control, and checkpointing. It also coordinates durable single- or multi-agent tasks across providers with leases, dependency graphs, evidence logs, repair loops, and separate verification gates.
      128
      1
      ISC
    • A
      license
      Not graded
      quality
      A
      maintenance
      Provides a provider-agnostic MCP server that coordinates structured multi-agent workflows, owning task claims, action logs, handoffs, and server-side health gates for coding agents. It enables tracked specs, tasks, reviews, and verified completion across Claude Code, Codex CLI, Cursor, Grok Build, and OpenCode.
      29 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Provides a provider-agnostic MCP server that gives AI coding agents a shared workflow for drafting specs, claiming tracked tasks, logging actions and handoffs, and gating completion on health-check evidence. It also bundles read-only skills for triage, review, consultation, and product guidance across Claude Code, Codex CLI, Cursor, Grok Build, and OpenCode.
      29 npm
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that enables AI agents to execute real-world actions through 10 specialized engines covering authenticated API calls, browser automation, visual QA, shell commands, file operations, job scraping, and parallel task execution.
      -

    TDQS

    B3.1/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: lookup retrieves evidence, while verify_claim checks claims against that evidence. There is no ambiguity or overlap in their roles.

    Naming Consistency4/5

    Both tool names are imperative verbs, but 'lookup' is a single word while 'verify_claim' follows a verb_noun pattern. This is a minor deviation, and the names are still predictable and readable.

    Tool Count3/5

    With only two tools, the set feels slightly thin for a production-oriented server. However, the narrow scope of evidence retrieval and verification may justify the small number, making it borderline appropriate.

    Completeness4/5

    The two tools form a logical pipeline: retrieve evidence first, then verify claims against it. Minor gaps might exist, such as a way to browse or filter evidence sources, but the core workflow appears covered.

    Maintenance

    ActivityStale
    ResponsivenessNo issues