Skip to main content
Glama
chy4pro

jev-in-mcp

by chy4pro
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to jev-in-mcp

No user-submitted related servers found.

    Related Servers

    • toolJev

      VishiATChoudhary
      A
      license
      Not graded
      quality
      B
      maintenance
      Fronts every MCP server you have with two tools: search shortlists relevant tools, and execute runs sandboxed Python that calls upstream tools as mcp..(). It enables agents to make bulk, repeated, or conditional tool calls using calibrated decision-model choices instead of per-item LLM generation.
      3
      MIT

    • MCP-Lens

      M8T-Jacob
      A
      license
      Not graded
      quality
      D
      maintenance
      Acts as a proxy/router for multiple downstream MCP servers, exposing only meta-tools to the host to reduce token usage, enabling efficient search and invocation of tools from a fleet of servers.
      8 npm
      MIT
    • MetaMCP by dataware-co

      MetaMCPofficial

      dataware-co
      A
      license
      A
      quality
      B
      maintenance
      Aggregates multiple MCP servers into a single interface, reducing token overhead and simplifying tool management for LLMs.
      6
      129 npm
      18
      Apache 2.0

    • McpOrchestrator

      Byggarepop
      A
      license
      Not graded
      quality
      A
      maintenance
      Lets an agent reach many downstream MCP servers and Agent Skills through a single relay connection, loading their tool manifests only on demand so the always-on context stays flat as servers are added. The agent works through three meta-tools — list_capabilities, discover_tools and route — while the relay forwards requests without interpreting them.
      2
      MIT
    Deploy Server
    Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    A3.9/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of confusion or overlap. The single tool has a clear, distinct purpose.

    Naming Consistency5/5

    The tool name 'jev_status' is clear and descriptive, and with only one tool there are no conflicting naming conventions to cause inconsistency.

    Tool Count3/5

    The server exposes a single tool, which feels thin for a typical MCP server. However, it is appropriate for a status-only tool, so the count is borderline.

    Completeness5/5

    The status tool covers the key aspects of its domain: connection state, key configuration, and tool permissions. No obvious gaps for a status endpoint.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources