otel-mcp-server
Related Servers
Alternatives to otel-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables AI agents to query OriginChain's telemetry agent for log patterns, semantic incident analysis, distributed traces, service graphs, and read-only SQL queries over telemetry data.104 npmMIT
- 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
- AlicenseNot gradedqualityBmaintenanceEnables secure enterprise AI agents to access internal tools like GitHub, Gmail, Calendar, file systems, databases, and knowledge bases through the Model Context Protocol, with built-in security, audit, and observability.MIT
- AlicenseDqualityDmaintenanceEnables AI assistants to interact with local Docker containers, Kubernetes clusters, and system logs using the Model Context Protocol.9ISC
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to discover and invoke enterprise tools like web search, document parsing, meeting scheduling, and email through a unified Model Context Protocol server that aggregates and routes across multiple backends.1-
- FlicenseNot gradedqualityCmaintenanceEnables secure, stateful AI agents and LLM tools to access enterprise databases, knowledge bases, live system metrics, and sandboxed code execution through the Model Context Protocol, with authentication, rate limiting, and safety guards.-
TDQS
Scored across 29 tools
Most tools target a distinct backend+resource (metrics_query vs logs_query vs traces_search), and domain prefixes make routing obvious. There is mild overlap among the summary-style tools — system_health, exchange_status, and transparency_metrics all surface posture/alerts/uptime, and verify_trace reads like a verification verb but is actually a business-level trace lookup (contrast zk_proof_verify). These edge cases are clarified by descriptions, so misselection risk is low but not zero.
The dominant pattern is snake_case with a domain prefix (metrics_*, traces_*, logs_*, zk_*, anomalies_*, system_*), which is readable and mostly predictable. However, six tools drop the prefix entirely (exchange_status, total_volume, recent_trades, transparency_metrics, verify_trace, backend_capabilities), and suffix styles mix verbs and nouns (traces_services vs traces_search, zk_solvency vs zk_proof_get), so the convention is not fully uniform.
At 29 tools the surface is on the heavy side and exceeds the comfortable 3-15 band, with each domain contributing 4-6 tools. The breadth is justified by the server spanning four distinct backends (Prometheus, Jaeger, Loki, ZK) plus a business-exchange domain, so it is borderline rather than bloated. A few summary tools (exchange_status, transparency_metrics, system_health) could be consolidated.
Coverage is strong across every advertised domain: metrics (targets, instant/range queries, alerts, metadata, label values), traces (get, services, operations, dependencies, search), logs (query, label names/values, trace correlation), ZK (proof get/verify, solvency, stats), anomalies, and system topology/health. Minor gaps remain — there is no Prometheus label-name listing to mirror logs_labels, no span-level retrieval, and no ZK proof history/listing — but agents can work around these via the query tools.