Skip to main content
Glama

Related Servers

Alternatives to mcp-lens

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      A progressive-disclosure gateway for MCP servers that keeps tool lists small by exposing one top-level tool per server, allowing agents to search, list, inspect, and call underlying tools within a selected domain.
      14
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      A configuration-driven framework for building MCP servers that expose domain-oriented tools (e.g., get_customer, get_database_sizes) instead of generic SQL interfaces, by loading tool metadata and SQL queries from declarative packs.
      Apache 2.0
    • F
      license
      Not graded
      quality
      D
      maintenance
      A meta-MCP server that discovers and explores other MCP servers using progressive disclosure patterns to reduce token usage by up to 99%.
      -
    • A
      license
      Not graded
      quality
      Not graded
      maintenance
      A lightweight and fast MCP server that enables AI agents to efficiently discover and execute tools through progressive disclosure, minimizing context consumption while supporting safe code execution in external environments.
      3 npm
      -
    • A
      license
      B
      quality
      A
      maintenance
      A meta-MCP server that manages and aggregates other MCP servers, enabling LLMs to dynamically extend their own capabilities by searching for, adding, and configuring tool servers.
      16
      66 PyPI
      143
      AGPL 3.0
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables developers to build MCP servers with registry-managed tool metadata, runtime hot-reloading, pluggable authentication and authorization, per-audience tool views, and resilient stateless operation.
      -

    TDQS

    A4.2/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a distinct role in a clear pipeline: search to discover, get schema to understand inputs, and execute to run. There is no overlap or ambiguity between the three tools.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern: search_capabilities, get_capability_schema, execute_capability. The naming clearly communicates the action and target for each tool.

    Tool Count5/5

    Three tools is perfectly scoped for a capability catalog interface. Each tool is necessary for the workflow, and there are no redundant or extraneous tools.

    Completeness5/5

    The tool set covers the full intended workflow: discovering capabilities, understanding their schemas, and executing them. There are no obvious gaps in the core purpose of the server.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues