skgate
Related Servers
Alternatives to skgate
- AlicenseNot gradedqualityAmaintenanceA unified hub for centrally managing and dynamically orchestrating multiple MCP servers/APIs into separate endpoints with flexible routing strategies.775 npm2,587Apache 2.0
Related Servers
- AlicenseNot gradedqualityAmaintenanceSelf-hosted MCP gateway that unifies stdio, Docker, and remote MCP servers behind one endpoint per client, with proactive OAuth refresh and no telemetry.4MIT
- AlicenseNot gradedqualityAmaintenanceMcpMux is a desktop app that runs a local MCP gateway. You configure servers once — every AI client connects through a single URL.23 npm25GPL 3.0
- FlicenseNot gradedqualityDmaintenanceA self-hosted MCP gateway that aggregates all your MCP servers behind a single Streamable HTTP endpoint, with automatic registry discovery (19,000+ servers), on-demand Docker provisioning, multi-device support via SSH, OAuth2 PKCE authentication, and a workflow engine for saving and replaying multi-step tool sequences.-
- AlicenseAqualityBmaintenanceGrok asked for MCP on a URL. This is it. First MCP server built for Grok URL-based • Zero config • Just works12791 npm19MIT
- AlicenseNot gradedqualityDmaintenanceA Node.js MCP server with custom OAuth 2.1 + PKCE authentication, enabling secure remote connections to LLMs like Claude and ChatGPT.432 npmMIT
- AlicenseAqualityDmaintenanceMCP server for integrating xAI's Grok model into OpenAI Codex Desktop/GUI, enabling direct Grok calls via chat completions or responses with OAuth or API key authentication.9MIT
TDQS
Scored across 3 tools
All three tools are read-only introspection, but they target distinct surfaces: product metadata (about), feature inventory (list_features), and environment variables (config_help). 'about' and 'list_features' are the closest pair since about returns a summary and mode while list_features returns feature entries, but the descriptions draw a workable line and about is explicitly an entry point.
The names mix conventions: 'about' is a bare preposition/noun, 'list_features' is verb_noun, and 'config_help' is noun_noun. All are lowercase snake-ish and readable, but there is no predictable pattern an agent could extrapolate from.
Three tools is thin for a server whose whole purpose is explaining a product, though each is scoped to a different information source with no redundancy. It sits at the borderline rather than being clearly under- or over-provisioned.
The surface is deliberately offline and binary-only, so it cannot read live environment values, enumerate configured MCP servers/tools, or validate an actual running config. Documentation lookup is covered, but agents that need to inspect or verify a running skgate instance hit a dead end.