Skip to main content
Glama
crunchtools

mcp-syslog

by crunchtools

Related Servers

Alternatives to mcp-syslog

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      B
      maintenance
      Provides telemetry tools for retrieving recent logs and system metrics to support root-cause analysis of infrastructure incidents. Enables autonomous incident triage with grounded verification and human-in-the-loop remediation.
      1
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables log analysis through MCP tools for searching logs, retrieving error contexts, and summarizing incidents with self-verified root-cause hypotheses.
      6 npm
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables debugging of distributed transactions by continuously ingesting Docker container logs, indexing them by trace/request ID, and exposing MCP tools to search, tail, and correlate logs across services.
      7
      ISC
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables natural-language querying and investigation of homelab logs from syslog, Docker, OTLP, and AI transcripts, with SQLite full-text search, timeline correlation, incident clustering, and fleet topology insights.
      4
      AGPL 3.0
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables querying and analyzing logs from multiple remote Unix hosts via the Log Collector API, with tools for search, error detection, and summary generation.
      -

    TDQS

    A3.5/5.0

    Scored across 6 tools

    Disambiguation4/5

    Each tool targets a distinct query mode: listing sources, filtered search, regex grep, tailing, contextual windows, and stats. The main overlap is between syslog_search_tool (severity/pattern) and syslog_grep_tool (regex), which an agent could confuse, but the descriptions draw a reasonable line between structured filtering and regex matching.

    Naming Consistency4/5

    All tools follow a clear syslog_<action>_tool pattern, which is highly predictable. The action terms mix nouns (sources, stats) and verbs (search, grep, tail), a minor inconsistency within an otherwise uniform convention.

    Tool Count5/5

    Six tools is well-scoped for a log query server, with each tool covering a genuinely distinct access pattern (discovery, search, grep, tail, context, stats). No tool feels redundant or vestigial.

    Completeness4/5

    The read-only query lifecycle is well covered: discovery, filtering, regex, recency, surrounding context, and aggregate stats. Minor gaps exist around schema/field discovery or export, but core investigative workflows are fully supported without dead ends.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive