MCP Rating Gateway
Related Servers
Alternatives to MCP Rating Gateway
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceA flexible MCP proxy server that connects to and routes between multiple backend MCP servers over STDIO or SSE, enabling dynamic management and namespacing of tools.111MIT
- AlicenseNot gradedqualityCmaintenanceEnables developers to expose any dev tool as a safe, audited MCP server with permission tiers, audit logging, and automatic argument validation.MIT
- AlicenseBqualityDmaintenanceDynamic MCP server for Node.js enabling runtime tool creation, management, and execution in isolated sandboxes (Docker or Node).88 npm1MIT
- AlicenseAqualityBmaintenanceLets agents create reusable MCP tools, verify and mount them at runtime, and request credentials by name with user consent. Runs locally and caches verified tool servers for reuse.2MIT
- FlicenseAqualityDmaintenanceUniversal MCP proxy server that discovers, searches, and executes tools across all configured MCP servers from a single entry point.7-
- FlicenseNot gradedqualityCmaintenanceEnables agents to connect to remote MCP servers once, access their tools through a compact MCP endpoint, pair a CLI inside sandboxes, and create watches that turn command or tool output into pollable structured events.2-
TDQS
Scored across 13 tools
Most tools target clearly distinct operations (discover, connect, disconnect, call, audit, health, usage). The main soft spots are mcp_discover vs mcp_recommend (both 'find me a server') and mcp_list_active vs mcp_server_info (both about connected servers), though descriptions give enough hints to separate them.
All tools share a clean mcp_ prefix in snake_case, which is highly predictable. Minor deviation: most are verb-led (mcp_discover, mcp_connect, mcp_call_tool) but several are bare nouns (mcp_profiles, mcp_groups, mcp_usage, mcp_sandbox) with an implied 'manage'.
13 tools sits squarely in the well-scoped range and maps neatly onto the gateway lifecycle. Each tool covers a distinct concern (registry, connections, security, diagnostics, analytics) without redundancy.
The connection lifecycle is fully covered: discover, connect, list, inspect, call, sandbox-configure, disconnect, plus audit/health/usage monitoring. Minor gaps exist around credential/auth management and registry publish/remove operations, but core gateway workflows have no dead ends.