Skip to main content
Glama
orkait

Hyperstack

by orkait
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Hyperstack

No user-submitted related servers found.

    Related Servers

    • godkiller-mcp

      taurus42119-stack
      A
      license
      A
      quality
      B
      maintenance
      An MCP server that enforces hard quality gates on AI coding agents, including forced web search, planning, and empirical test execution, to prevent common failure modes and ensure production-grade code.
      13
      24
      MIT

    • Unravel MCP

      EruditeCoder108
      A
      license
      Not graded
      quality
      C
      maintenance
      A deterministic AST evidence engine that forces AI agents to debug using verified execution facts instead of pattern-matching symptoms, enabling hallucination-free debugging for MCP-compatible agents.
      4 npm
      Business Source 1.1

    • Spec Guard

      jpstone
      A
      license
      Not graded
      quality
      D
      maintenance
      A methodology and MCP server for agent-driven software development where humans write specs and agents implement code, enforced by six mechanical gates to ensure spec validity, contracts, tests, and review.
      17 npm
      MIT

    • agentboost

      codeman008
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides coding agents with structured planning, persistent project memory, automated verification, and safety permission controls through MCP tools, enabling better planning, context retention, self-checking, and guarded execution.
      2 npm
      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.4/5.0

    Scored across 118 tools

    Disambiguation4/5

    Domain prefixes (reactflow_, marketing_, etc.) clearly separate tool groups, but the high number (118) across many domains may still cause confusion, especially with similar verb patterns like 'get_*' across different domains. Within a domain, tools are mostly distinct.

    Naming Consistency5/5

    All tools follow a consistent <domain>_<verb>_<noun> pattern (e.g., reactflow_list_apis, marketing_get_positioning). Minor exceptions like hyperstack_setup don't break the overall consistency.

    Tool Count2/5

    118 tools is excessive for a single MCP server. While each sub-domain individually might warrant its count, the aggregate scope is too broad and will overwhelm agent prompts. The server tries to cover too many unrelated areas (e.g., React Flow, marketing, product management, etc.).

    Completeness3/5

    Within each sub-domain, the tool surface is fairly complete for knowledge retrieval (list, get, search, generate). However, the server is a collection of static knowledge bases with little cross-domain integration or action-oriented tools, leaving gaps in workflows that require combining domains.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources