Skip to main content
Glama
delorenj

33GOD Pipeline MCP Hub

by delorenj
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

Related Servers

Alternatives to 33GOD Pipeline MCP Hub

No user-submitted related servers found.

    Related Servers

    • fastmcp-gateway by Ultrathink-Solutions

      fastmcp-gatewayofficial

      Ultrathink-Solutions
      A
      license
      Not graded
      quality
      A
      maintenance
      Aggregates tools from multiple upstream MCP servers and exposes them through 4 meta-tools, enabling LLMs to discover and use hundreds of tools without loading all schemas upfront.
      2
      Apache 2.0
    • MetaMCP by mentu-ai

      MetaMCPofficial

      mentu-ai
      A
      license
      A
      quality
      B
      maintenance
      Aggregates multiple MCP servers into a single interface, reducing token overhead and simplifying tool management for LLMs.
      6
      197 npm
      18
      Apache 2.0

    • Caplets

      spiritledsoftware
      A
      license
      Not graded
      quality
      A
      maintenance
      A progressive-disclosure gateway for MCP servers that keeps tool lists small by exposing one top-level tool per server, allowing agents to search, list, inspect, and call underlying tools within a selected domain.
      14
      MIT

    • smart-router

      chris-asmussen
      A
      license
      A
      quality
      B
      maintenance
      A single MCP server that fronts many downstream MCP servers and Skills, exposing only four tools (search, call_tool, use_skill, admin) so that an agent's context window only ever sees search results on demand.
      5
      10
      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

    A3.9/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have completely distinct purposes: list_domains for discovery and call_domain_tool for invocation. No overlap at all.

    Naming Consistency5/5

    Both tools follow a consistent verb_noun snake_case pattern (list_domains, call_domain_tool), making them predictable and clear.

    Tool Count4/5

    With only 2 tools, the set feels thin, but for a hub server that delegates to domains, this minimal surface is acceptable and focused.

    Completeness2/5

    The hub is missing the list_domain_tools tool, which is advertised in list_domains' description. Without it, users cannot discover and invoke tools within domains, causing a critical gap.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources