mcpserverlist-mcp
Related Servers
Alternatives to mcpserverlist-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceProvides a local stdio MCP interface that forwards tool calls to an already-running ModMind bridge for Minecraft automation.5AGPL 3.0
- AlicenseNot gradedqualityCmaintenanceA 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 npmMIT
- AlicenseNot gradedqualityDmaintenanceThis 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
- AlicenseNot gradedqualityDmaintenanceProxies STDIO-based MCP clients to streaming HTTP MCP servers, enabling local clients to connect to remote servers.8 npm3MIT
- AlicenseNot gradedqualityAmaintenanceBridge 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 npm54MIT
- AlicenseNot gradedqualityAmaintenanceEnables running local MCP servers on machines behind NAT and accessing their tools from anywhere through a single Streamable HTTP endpoint, without opening any inbound ports.MIT
TDQS
Scored across 32 tools
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.
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.
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.
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.