{"id":"calmoai-mcp-server-signoz","name":"mcp-server-signoz","af_score":66.2,"security_score":55.8,"reliability_score":25.0,"what_it_does":"Provides a Go-based Model Context Protocol (MCP) server (STDIO transport) that exposes SigNoz observability data access as MCP tools. It connects to a user’s SigNoz instance (URL plus optional API key), supporting queries for dashboards, services, APM metrics, and trace/log retrieval via ClickHouse SQL, as well as executing custom ClickHouse or SigNoz builder queries within time ranges.","best_when":"You want an MCP-compatible integration to query SigNoz observability data from tools like Claude Desktop/Cursor using STDIO.","avoid_when":"You need a REST/HTTP API, webhooks, or cloud-hosted managed service rather than a local MCP server process; or you cannot restrict/validate query inputs when enabling custom SQL execution.","last_evaluated":"2026-04-04T19:36:11.106556+00:00","has_mcp":true,"has_api":false,"auth_methods":["SigNoz API key via SIGNOZ_MCP_SIGNOZ_API_KEY (optional per README)"],"has_free_tier":false,"known_gotchas":["Custom ClickHouse/SQL execution tools can be expensive or slow; use strict time ranges and query limits to avoid timeouts.","If your SigNoz instance requires auth, missing/incorrect SIGNOZ_MCP_SIGNOZ_API_KEY will likely cause connectivity/auth errors.","TLS skip verification (SIGNOZ_MCP_SIGNOZ_TLS_SKIP_VERIFY) can reduce security; ensure it’s not enabled in production.","Tool outputs may depend on dashboard/service naming conventions; mismatches can lead to empty results or query failures."],"error_quality":0.0}