Skip to main content
Glama
Wirasm

Orbit-MCP

by Wirasm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Orbit-MCP

No user-submitted related servers found.

    Related Servers

    • InfiniteMCP

      day50-dev
      F
      license
      Not graded
      quality
      D
      maintenance
      A meta-MCP server that acts as a universal gateway, allowing users to discover and execute tools from thousands of other MCP servers through semantic search. It dynamically loads servers on demand and provides standardized functions for searching, discovering, and running tools across the entire MCP ecosystem.
      6
      -

    • MCP Gateway

      MikkoParkkola
      F
      license
      A
      quality
      A
      maintenance
      A multiplexing gateway that aggregates multiple MCP servers into a single port, significantly reducing context token usage through a Meta-MCP discovery system. It enables dynamic tool discovery and invocation across various transport protocols including stdio, HTTP, and SSE.
      15
      65
      -

    • SuperMCP Server

      YakupAtahanov
      A
      license
      Not graded
      quality
      D
      maintenance
      A powerful orchestration layer for Model Context Protocol (MCP) servers that enables AI assistants to dynamically discover, inspect, and interact with multiple MCP servers through a unified interface.
      MIT

    • Smart MCP Proxy

      Dumbris
      A
      license
      Not graded
      quality
      D
      maintenance
      Federating gateway for AI agents to discover and call tools from multiple MCP servers with intelligent search and dynamic tool registration.
      39
      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 25 tools

    Disambiguation3/5

    Several tools have overlapping purposes, such as discover_gateway_tools and list_enabled_tools both listing tools from enabled servers. list_available_servers vs list_enabled_servers are distinct but could confuse agents. Description clarity helps, but the boundaries between some tools remain fuzzy.

    Naming Consistency4/5

    Most tools follow a verb_noun pattern (list_packs, create_pack, enable_server). Minor deviations exist: hello_orbit is not verb_noun, gateway_status uses noun_noun instead of get_gateway_status. These are small inconsistencies in an otherwise predictable scheme.

    Tool Count3/5

    At 25 tools, the set is on the heavy side for the domain of MCP server management. It is borderline but each tool addresses a specific management function, so the count is not unreasonable, though it could be consolidated to reduce cognitive load.

    Completeness4/5

    The domain covers server lifecycle (enable/disable/reset), OAuth management, gateway operations, and pack CRUD. Major operations are present, but there is no delete_pack tool (only uninstall_pack, which disables servers without removing the pack). Minor gaps exist but agents can work around them.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources