F
licenseA
qualityF
maintenanceMCP 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
4
-
hve-squad MCP server
by Peter-N91
Related Servers
Alternatives to hve-squad MCP server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceAn 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.302MIT
- FlicenseAqualityDmaintenanceAn MCP server that exposes tools for sub-agent style reasoning across multiple LLM providers, enabling delegation of prompts to various models and running critique loops, debates, red-teaming, and answer ranking.6-
- FlicenseNot gradedqualityBmaintenanceMCP server that enables an agent to spawn sub-agents (a crew) via a local tool, allowing delegation of large tasks to parallel workers with a human approval gate and efficient token usage.-
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server that turns multiple AI coding agents into a coordinated team that chats, debates, remembers, audits security, and works in parallel on the same project.MIT
- AlicenseDqualityCmaintenanceThe 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.25MIT
TDQS
A4.2/5.0
Scored across 6 tools
Disambiguation4/5
Tools are distinct by stage or entry point: research, plan, review, architect, federate, and run. The catch-all squad_run could conceptually overlap with stage-specific tools, but its description explicitly directs users to narrower tools when applicable, so ambiguity is minimal.
Naming Consistency5/5
All tools share the squad_ prefix followed by a single descriptive term (review, run, architect, etc.), yielding a predictable and consistent pattern. There is no mixing of camelCase or inconsistent verb/noun styles.
Tool Count5/5
6 tools is well-scoped for a squad orchestration server covering the main entry points and a federation meta layer. Each tool corresponds to a distinct stage or catch-all, with no redundancy.
Completeness3/5
The squad lifecycle includes Research, Plan, Implement, and Review, but there is no dedicated tool for the Implement stage. While squad_run covers the full pipeline including Implement, agents cannot directly trigger only implementation, leaving a notable gap.
Maintenance
ActivityActive
ResponsivenessUnresponsive