tracehub-mcp
Related Servers
Alternatives to tracehub-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables natural language querying and analysis of OpenTelemetry traces, metrics, and logs stored in Elasticsearch/OpenSearch, allowing AI assistants to investigate performance issues, find root causes, and explore system behavior.14MIT
- AlicenseNot gradedqualityBmaintenanceEnables coding agents to query a local OTLP trace collector: list recent traces, inspect span trees and critical paths, flag SQL N+1 loops, surface gen_ai metrics, and diagnose slow traces with a local OpenAI-compatible model.MIT
- AlicenseAqualityBmaintenanceEnables AI agents to query telemetry metrics with statistical anomaly detection, inspect OpenTelemetry error traces, correlate incidents with Git deployments, and generate actionable incident summaries and remediation runbooks.5MIT
- AlicenseAqualityCmaintenanceBridges AI coding assistants with the OpenTelemetry ecosystem, providing real-time access to repositories, documentation, examples, semantic conventions, and instrumentation scoring for high-quality observability.920Apache 2.0
- AlicenseAqualityDmaintenanceConnects AI assistants to Warpmetrics telemetry data to monitor AI agent performance, execution runs, and LLM costs. It allows users to query success rates, latency, and spend metrics directly through natural language interfaces.2063 npmMIT

SigNoz MCP Serverofficial
AlicenseNot gradedqualityBmaintenanceEnables AI assistants and LLMs to query SigNoz observability data (metrics, traces, logs, alerts, dashboards) using natural language.132Apache 2.0
TDQS
Scored across 19 tools
Most tools have clearly distinct purposes (search_traces vs search_spans_tool, find_errors vs investigate_error_spike, triage_trace vs correlate_trace). A few clusters are close-overlap: get_llm_usage / compare_time_windows / investigate_cost_spike and get_llm_model_stats / get_llm_usage all touch token/cost aggregation, but descriptions differentiate them. Boundaries are mostly sharp with one or two spots where an agent must read carefully.
Overwhelmingly consistent snake_case verb_noun pattern (list_services, get_trace, search_traces, investigate_cost_spike). The notable deviation is the redundant `_tool` suffix on search_spans_tool and list_llm_tools_tool, which breaks the otherwise clean convention. Minor but visible inconsistency.
19 tools is borderline heavy (16-25 range) for a trace-analysis server. Most earn their place, but the usage/cost-analysis cluster (get_llm_usage, compare_time_windows, investigate_cost_spike, get_llm_expensive_traces) could arguably be consolidated. Slightly over the ideal scope.
The surface covers listing, search, detail retrieval, triage, cross-backend correlation, error analysis, LLM usage/cost/latency, sessions, prompt versions, and span-level tools — a rich read/analysis lifecycle. As a read-only observability server, CRUD gaps aren't expected; minor gaps exist (no span-by-id fetch, no annotation/feedback writing) but agents can work around them.