Skip to main content
Glama

Related Servers

Alternatives to mcp-server-example

No user-submitted related servers found.

    Related Servers

    • F
      license
      A
      quality
      C
      maintenance
      Enables AI agents to discover and query enterprise knowledge documents and business metrics through standardized MCP tools, supporting retrieval, structured sales/order analysis, anomaly scanning, and data lineage lookups.
      12
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to search, read, and traverse documentation bundles in Open Knowledge Format via MCP tools.
      233 npm
      72
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to securely search and list internal company documents via MCP tools, so they can answer employee questions based on current internal documentation.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to query an organization's device posture, compliance, policies, and software/CVE status through a remote, read-only, OAuth-secured MCP endpoint.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides RAG (Retrieval Augmented Generation) access to technical documentation through MCP, enabling LLMs to search and retrieve relevant documentation on-demand.
      4
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables to build and query a knowledge base with retrieval-augmented generation, supporting document ingestion, hybrid search, and live data integration from external APIs via MCP tools.
      2
      -

    TDQS

    A4/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool targets a distinct operation: listing devices, retrieving a device detail, and searching SDK methods. No two tools overlap in purpose or output, so an agent can easily select the right one.

    Naming Consistency5/5

    All tool names follow a clear lower_snake_case verb_noun pattern: list_devices, get_device, search_sdk. The convention is perfectly consistent across the set.

    Tool Count4/5

    Three tools is on the smaller side, but the server appears focused on read-only device catalog and SDK lookup. The count is reasonable for a narrow purpose, though it might feel slightly thin if the server expected broader functionality.

    Completeness4/5

    For the implied read-only catalog use case, the coverage is adequate: list and get cover device data, and search covers SDK exploration. Missing create/update/delete operations are acceptable if the server is intentionally read-only, but a get_sdk_method or list_sdk_methods would round out the SDK side.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues