Skip to main content
Glama
Peter-N91

hve-squad MCP server

by Peter-N91
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to hve-squad MCP server

No user-submitted related servers found.

    Related Servers

    • agentforge

      doggychip
      F
      license
      A
      quality
      F
      maintenance
      MCP server that exposes 300+ AI agents as tools via a single API key. Supports listing agents, invoking any agent with chat-completion style messages, checking agent health, and retrieving platform statistics.
      5
      3
      -

    • WhitePact

      Guruprasath-Annadurai
      A
      license
      A
      quality
      A
      maintenance
      An MCP server that exposes governance, trust-scoring, compliance, guardrail, cost, drift, and supply-chain scanning tools and resources to any MCP client over stdio, Streamable HTTP, or legacy HTTP+SSE. It lets agents route every tool call through a deterministic five-way decision (allow, redact, require approval, deny, or quarantine) with hash-chained evidence, human approval workflows, and in-agent trust gates for LangChain, LangGraph, and Google ADK.
      30
      1
      MIT

    • Keshro MCP

      jlewitt1
      A
      license
      D
      quality
      C
      maintenance
      The intelligent execution layer for coding agents, exposed as an MCP server for high-stakes engineering projects. It enables AI agents to manage plans, tasks, and integrations via tool calls.
      25
      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

    A4.4/5.0

    Scored across 6 tools

    Disambiguation4/5

    Each stage tool focuses on a distinct phase (research, plan, review, architect) and the descriptions provide clear 'use for' cues. The main overlap risk is between squad_review and squad_architect, or between a stage tool and squad_run, but the intended scope is made explicit enough for an agent to select correctly.

    Naming Consistency5/5

    All tools follow a consistent squad_<action> pattern in lowercase snake_case. The verbs (research, plan, review, architect, run, federate) are uniform in style, even if 'architect' is used as a verb, and the prefix makes the family relationship obvious.

    Tool Count5/5

    Six tools is well within the ideal range for a workflow-orchestration server. Each tool covers a distinct stage or meta-operation, and there is no obvious bloat or redundancy; the count feels properly scoped for the stated purpose.

    Completeness4/5

    The tool set covers research, planning, review, architecture, the full pipeline, and federation setup. However, the squad_run description mentions an 'Implement' stage that has no corresponding standalone tool, which is a minor gap if a caller wants to run only that phase. Overall core workflows are still complete.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources