Skip to main content
Glama
huanglixinccc

aliyun-sls-codex

by huanglixinccc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to aliyun-sls-codex

No user-submitted related servers found.

    Related Servers

    • elasticsearch-logs

      ws135y
      F
      license
      Not graded
      quality
      C
      maintenance
      Read-only MCP server for Elasticsearch log querying. Enables natural language search, filtering, context retrieval, and aggregation of logs.
      -

    • mcp-opensearch

      bunnyiesart
      A
      license
      A
      quality
      B
      maintenance
      A read-only MCP server that enables AI assistants to search, aggregate, and explore OpenSearch log data through 12 tools for connectivity, index discovery, search, and aggregations.
      17
      MIT

    • Crow

      yusif-v
      F
      license
      Not graded
      quality
      A
      maintenance
      MCP server for read-only CrowdStrike Falcon visibility, enabling AI agents to list and retrieve detections, alerts, hosts, incidents, perform IOC lookups, and run LogScale queries.
      -

    • ms-sentinel-mcp-server

      dstreefkerk
      A
      license
      C
      quality
      D
      maintenance
      MCP server for Microsoft Sentinel. Enables access to Sentinel logs, incidents, analytics, and Entra ID data via a modular, queryable interface. Strictly non-production. Designed for use with Claude and other LLMs.
      49
      18
      MIT

    • hpc-support-mcp

      PetitSphincter
      A
      license
      Not graded
      quality
      C
      maintenance
      A read-only MCP server exposing SLURM, GPFS, Prometheus (node exporter + DCGM GPU metrics) and generic Elasticsearch exploration as diagnostic tools for LLM-based HPC support assistants.
      Apache 2.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.6/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clear, distinct purpose: search by keywords, fetch context around a timestamp, and verify connectivity. There is no overlap or ambiguity between them.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern: search_logs, get_context_logs, check_connection. The naming is uniform and predictable.

    Tool Count5/5

    With 3 tools, the server is well-scoped for a focused log-searching utility. Each tool is essential to the core workflow of finding and examining logs.

    Completeness4/5

    The tools cover the main workflow of searching logs and retrieving surrounding context, but lack explicit time-range controls or the ability to list available log stores. These are minor gaps that can be worked around with existing parameters or configuration.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources