# SigNoz MCP Server (oci · docker.io/signoz/signoz-mcp-server) SigNoz MCP server: access metrics, traces, logs, alerts, and dashboards via AI assistants - Trust score: 7/100 (low) - Change this week: +1 - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-11-06 ## Components - oci · `docker.io/signoz/signoz-mcp-server`: 7/100 (this document), [markdown](https://verifymcp.io/servers/signoz-signoz-mcp-server/docker-io-signoz-signoz-mcp-server.md), [page](https://verifymcp.io/servers/signoz-signoz-mcp-server/docker-io-signoz-signoz-mcp-server) ## Channel facts - Registry: `oci` - Package: `docker.io/signoz/signoz-mcp-server` - Version: `v0.18.0` - Transport: `stdio` ## Trust breakdown How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog) Scored 2026-11-06. - **Supply Chain Security**: 0/100 - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package. - Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read. - Install-script risk not yet assessed. - Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read. - **Provenance & Transparency**: 35/100 - Source repository is publicly reachable at the declared URL. - Provenance check failed: no build-provenance attestation is published. - License check failed: no license is declared. - Actively maintained (last published 0 days ago). - Publishes a security disclosure policy (SECURITY.md). - **Schema Quality & AI Usability**: 0/100 - Schema quality not yet verified: this package installed, but its server did not start, so we have no schema to assess. - **Stability & Change Management**: 0/100 - Stability not yet verified: this package installed, but its server did not start, so we have no schema to compare. - **Tool Coverage**: 0/100 - Tool coverage not yet verified: this package installed, but its server did not start, so we have no tool definitions to assess. - **Tool Safety**: 0/100 - Tool safety not yet verified: this package installed, but its server did not start, so we have no tool text to scan. - **Capabilities**: 0/100 - Protocol version not yet verified: this package installed, but its server did not start, so we never saw its MCP handshake. **Unverified: 6 categories.** Categories scored 0 because we could not verify them: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm. ## Install ### How do I install the SigNoz MCP Server server? SigNoz MCP Server runs locally as a container image, launched with docker run --rm -i docker.io/signoz/signoz-mcp-server:v0.18.0. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation. ### Claude ```bash claude mcp add signoz-signoz-mcp-server -- docker run --rm -i docker.io/signoz/signoz-mcp-server:v0.18.0 ``` ### Cursor ```json { "mcpServers": { "signoz-signoz-mcp-server": { "command": "docker", "args": [ "run", "--rm", "-i", "docker.io/signoz/signoz-mcp-server:v0.18.0" ] } } } ``` ### VS Code ```json { "servers": { "signoz-signoz-mcp-server": { "command": "docker", "args": [ "run", "--rm", "-i", "docker.io/signoz/signoz-mcp-server:v0.18.0" ] } } } ``` ### Codex ```bash codex mcp add signoz-signoz-mcp-server -- docker run --rm -i docker.io/signoz/signoz-mcp-server:v0.18.0 ``` ### opencode ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "signoz-signoz-mcp-server": { "type": "local", "command": [ "docker", "run", "--rm", "-i", "docker.io/signoz/signoz-mcp-server:v0.18.0" ], "enabled": true } } } ``` ### Hermes ```yaml mcp_servers: signoz-signoz-mcp-server: command: "docker" args: ["run", "--rm", "-i", "docker.io/signoz/signoz-mcp-server:v0.18.0"] ``` ### Netclaw ```json { "McpServers": { "signoz-signoz-mcp-server": { "Transport": "stdio", "Command": "docker", "Arguments": [ "run", "--rm", "-i", "docker.io/signoz/signoz-mcp-server:v0.18.0" ] } } } ``` ### Other ```json { "mcpServers": { "signoz-signoz-mcp-server": { "command": "docker", "args": [ "run", "--rm", "-i", "docker.io/signoz/signoz-mcp-server:v0.18.0" ] } } } ``` ## Changelog Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims. ### 2026-11-05 (score 7, +1) - [functional improvement] Security disclosure: fail → pass - [functional] Package version: v0.17.0 → v0.18.0 ### 2026-10-30 (score 6, 0) - [functional] Package version: v0.16.0 → v0.17.0 ### 2026-10-23 (score 6) First indexed and scored. ## MCP tools (0) Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package. ## Diagnostics Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/signoz-signoz-mcp-server/docker-io-signoz-signoz-mcp-server#diagnostics ## Score history - 2026-11-06: 7 - 2026-11-05: 7 - 2026-11-04: 6 - 2026-11-03: 6 - 2026-11-02: 6 - 2026-11-01: 6 - 2026-10-31: 6 - 2026-10-30: 6 - 2026-10-29: 6 - 2026-10-28: 6 - 2026-10-27: 6 - 2026-10-26: 6 - 2026-10-25: 6 - 2026-10-24: 6 - 2026-10-23: 6 ## Common questions ### What is the SigNoz MCP Server server? SigNoz MCP Server is listed in the public MCP registry as io.github.SigNoz/signoz-mcp-server. SigNoz MCP server: access metrics, traces, logs, alerts, and dashboards via AI assistants. This page covers its container image (docker.io/signoz/signoz-mcp-server). ### Is the SigNoz MCP Server server safe to use? SigNoz MCP Server scores 7 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm. ### Is the SigNoz MCP Server server still maintained? SigNoz MCP Server is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced. ### What did VerifyMCP test on the SigNoz MCP Server server? VerifyMCP ran 5 checks on SigNoz MCP Server, covering Source repository, Provenance, License, Maintenance and 1 more. 9 items could not be completed, a gap on our side rather than a finding about SigNoz MCP Server: Malware scan, Known CVEs, Install scripts, Dependency health and 5 more. 6 categories score 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a container image, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out. ## Links - Docker Hub: https://hub.docker.com/r/signoz/signoz-mcp-server - Repository: https://github.com/SigNoz/signoz-mcp-server - Changelog RSS feed: https://verifymcp.io/servers/signoz-signoz-mcp-server/docker-io-signoz-signoz-mcp-server.xml - Changelog JSON feed: https://verifymcp.io/servers/signoz-signoz-mcp-server/docker-io-signoz-signoz-mcp-server/changelog.json - Trust report (JSON): https://verifymcp.io/servers/signoz-signoz-mcp-server/docker-io-signoz-signoz-mcp-server.json - HTML version of this page: https://verifymcp.io/servers/signoz-signoz-mcp-server/docker-io-signoz-signoz-mcp-server