jev-mcp
Related Servers
Alternatives to jev-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceA browse-first MCP middleware that provides an LLM-friendly catalogue for discovering and invoking tools across multiple upstream MCP servers, reducing context overhead.-
- FlicenseNot gradedqualityCmaintenanceEnables an LLM to dynamically discover and call tools across multiple MCP servers (file, GitHub, SQL, Python execution) with authentication, rate limiting, and observability, supporting parallel execution and secure deployment.-
- AlicenseNot gradedqualityBmaintenanceA context-aware MCP proxy that reduces token usage by exposing only 3 tools (mcp_search, mcp_call, mcp_schema) to LLMs, with on-demand tool loading and BM25 search.103 npm2MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to proxy tool selection through a tiny local model, filtering large tool catalogs and escalating only low-confidence or destructive operations to a frontier model. This reduces latency, token costs, and frontier-model calls while maintaining reliable tool routing.MIT
- AlicenseNot gradedqualityDmaintenanceEnterprise-grade dynamic MCP proxy that eliminates token bloat by lazy-loading tool schemas based on semantic intent, enabling efficient orchestration of multiple backend tools from a single endpoint.MIT
- AlicenseNot gradedqualityDmaintenanceMCP proxy that reduces context usage through semantic tool routing, enabling on-demand discovery and routing of relevant tools.MIT
TDQS
Scored across 1 tool
Only one tool is exposed, so there is no competing operation to confuse it with; its description clearly states it selects MCP tools and does not execute them. The purpose is unambiguous, though the set is too small to demonstrate real disambiguation.
mcp_select uses a readable snake_case verb form with a server prefix, and with only one tool there is no convention mixing. The name is understandable, though it does not follow a broader verb_noun pattern because no other tools exist.
A single tool is explicitly considered too few for the apparent scope; the server is a focused selector, but one operation leaves no room for related lifecycle actions. The score reflects the thin surface rather than poor quality.
The tool covers the core selection operation, but a selection service would typically also expose ways to inspect available tools, configure budget, or refresh the index. Those gaps are notable but not fatal for a minimal router.