Skip to main content
Glama
sudomichael

mcpserverlist-mcp

by sudomichael

Related Servers

Alternatives to mcpserverlist-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      A thin stdio-to-HTTP bridge that forwards MCP messages to the hosted Proxycept server, enabling stdio-only MCP clients to access Proxycept's tool catalog.
      7 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      This server bridges a stdio MCP server to HTTP, allowing MCP clients that communicate over HTTP to use the server's tools. It includes a per-tool allow/deny filter for security.
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Bridge that lets stdio-only MCP clients connect to remote MCP servers with OAuth and other auth support, enabling local clients to use remote, authorized MCP servers.
      53 npm
      54
      MIT

    TDQS

    B3/5.0

    Scored across 32 tools

    Disambiguation3/5

    Several adjacent stages overlap, especially check_repository/import_repository/prepare_repository, check_launch_coverage/run_preflight/get_preflight, and create_server/create_launch/create_publisher_task. The descriptions are unusually detailed and often clarify non-goals, so an agent can usually disambiguate after reading, but the names alone are not enough.

    Naming Consistency4/5

    Names are consistently snake_case, and most follow a verb_noun pattern such as list_servers, create_launch, and get_order. The main deviations are noun-phrase instruction tools like connection_instructions and payment_instructions, which are minor but keep it from being fully uniform.

    Tool Count2/5

    With 32 tools, the surface is above the 25-tool heavy threshold and feels over-scoped for a single MCP server. The workflow is complex, but many stage-specific tools could likely be consolidated or grouped to reduce selection burden.

    Completeness4/5

    The set covers discovery, account management, repository preparation, preflight checks, launch/order/payment flows, publisher tasks, connections, and service cases. Minor gaps remain, such as no update/delete for server profiles, no launch cancellation, and no directory-detail retrieval, but the core lifecycle is well represented.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues