Skip to main content
Glama
prathamesh-git9

mcp-servers (Six production-minded MCP servers)

by prathamesh-git9
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

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

No user-submitted related servers found.

    Related Servers

    • Oktyv

      duke-of-beans
      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.
      -

    • frontier-orchestrator

      luckeyfaraday
      A
      license
      A
      quality
      C
      maintenance
      Multi-agent orchestration MCP server that lets Claude Code delegate backend, frontend, and tooling tasks to specialized AI agents (Codex, Kimi, Grok) with contract-first sequencing and workspace mutation guards.
      4
      7
      MIT

    • Hermes Squad

      BarnsL
      A
      license
      Not graded
      quality
      B
      maintenance
      Multi-agent AI orchestrator that runs parallel coding agents in isolated sessions with self-improving intelligence, exposed via an MCP server for task execution and management.
      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

    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

    ActivitySlowing
    ResponsivenessNo issues

    Resources