SigNoz MCP Server

MCP Server for SigNoz

MCP Servers Go Listed Apache-2.0

Is SigNoz MCP Server safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 5.0 / 10
Provenance None
Signed commits 100%
Last push today
Compare SigNoz MCP Server
Suggest a correction

In detail: SigNoz MCP Server scores 65.0/100 (Grade B), ranked #475 of 1325 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 5.0/10; 100% of recent commits are signed; last pushed 2026-09-26. Every point is earned from checkable signals — never paid placement. How scoring works →

How SigNoz MCP Server compares in MCP Servers

  1. #272 MCP Uptime Kuma 65.1 +0.1
  2. #273 PageIndex MCP 65.1 +0.1
  3. #274 SigNoz MCP Server 65.0 this agent
  4. #275 Cronometer MCP 65.0 ±0
  5. #276 Anythingmcp 64.9 −0.1

Bars show each HVTrust score; the tick marks SigNoz MCP Server’s 65.0.

Where the 65.0 comes from

HVTrust dimensions vs the MCP Servers average

65.0 / 100 · 100.0% confidence

SigNoz MCP Server MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
11.2 / 25
0.9 above avg 10.3
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.6 below avg 13.4
Transparency50% declared license · 50% OSSF Scorecard
12.8 / 17
0.6 above avg 12.2
Maintenance60% last-push freshness · 40% commit activity
17.6 / 20
5.5 above avg 12.1
AdoptionLog-scaled stars · package downloads
11.6 / 20
4.4 above avg 7.2

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-26
Grade Changed
Trust grade C → B
2026-09-25
Rank Moved
Rank rose 16 spots (#494 → #478)
2026-09-24
Rank Moved
Rank rose 188 spots (#682 → #494)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.0/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
63.0
Activity sub-score · out of 100
#274

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-09-26 06:32 UTC · Repo last pushed today

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars
123
Forks
46
Last Push
2026-09-26
today
Commits (4 wk)
25
Downloads (7d)
78,939
docker
HN mentions (30d)
—
Open Issues
8
Rank Change
▲3
was #478

Analysis

Activity Inputs

63.0 / 100
StarsRepository reach
12.6 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
17.6 / 25
CommunityFork signal
7.8 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
5.0 / 10
OpenSSF Scorecard · scanned Sep 24, 2026
Signed Commits
100%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 8
CI-Tests 10
CII-Best-Practices 0
Code-Review 10
Contributors 10
Dangerous-Workflow 0
Dependency-Update-Tool 10
Fuzzing 0
License 10
Maintained 10
Packaging 10
Pinned-Dependencies 0
SAST 0
Security-Policy 0
Signed-Releases 0
Token-Permissions 0
Vulnerabilities 6

Common questions about SigNoz MCP Server

SigNoz MCP Server has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
Does SigNoz MCP Server publish package provenance?
No published build provenance is currently detected for SigNoz MCP Server. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does SigNoz MCP Server have an OpenSSF Scorecard?
SigNoz MCP Server has an OpenSSF Scorecard score of 5.0/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is SigNoz MCP Server actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does SigNoz MCP Server use?
SigNoz MCP Server ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are SigNoz MCP Server's commits signed?
100% of the last 100 commits to SigNoz MCP Server are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
high confidence
Implemented
SigNoz MCP Server appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
low confidence
None detected
No clear third-party provider dependency detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
N/A
No package source configured
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

Detected changes to SigNoz MCP Server's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented

Maintain SigNoz MCP Server?

For maintainers

HVTrust scores SigNoz MCP Server from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Reputation Timeline

Signal history
Rank 31HVTrust 9Grade 9Listed 2Scorecard 1Delisted 1MCP 1
2026-09-26
Grade Changed
Trust grade C → B
2026-09-25
Rank Moved
Rank rose 16 spots (#494 → #478)
2026-09-24
Rank Moved
Rank rose 188 spots (#682 → #494)
2026-09-24
HVTrust Changed
HVTrust up 6.3pts (58.0 → 64.3)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Grade Changed
Trust grade D → C
2026-09-23
Rank Moved
Rank rose 126 spots (#808 → #682)
2026-09-23
HVTrust Changed
HVTrust up 29.3pts (28.7 → 58.0)
2026-09-22
Newly Listed
First tracked at rank #808
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-20
Rank Moved
Rank dropped 10 spots (#687 → #697)
2026-09-18
Grade Changed
Trust grade D → C
2026-09-18
Rank Moved
Rank rose 493 spots (#1180 → #687)
2026-09-18
HVTrust Changed
HVTrust up 18.7pts (38.9 → 57.6)
2026-09-17
Grade Changed
Trust grade C → D
2026-09-17
Rank Moved
Rank dropped 468 spots (#712 → #1180)
2026-09-17
HVTrust Changed
HVTrust down 17.9pts (56.8 → 38.9)
2026-09-16
Rank Moved
Rank rose 10 spots (#722 → #712)
2026-09-15
Rank Moved
Rank rose 13 spots (#735 → #722)
2026-09-13
Rank Moved
Rank dropped 11 spots (#722 → #733)
2026-09-12
Grade Changed
Trust grade D → C
2026-09-12
Rank Moved
Rank rose 460 spots (#1182 → #722)
2026-09-12
HVTrust Changed
HVTrust up 18.4pts (38.0 → 56.4)
2026-09-11
Grade Changed
Trust grade C → D
2026-09-11
Rank Moved
Rank dropped 481 spots (#701 → #1182)
2026-09-11
HVTrust Changed
HVTrust down 18.7pts (56.7 → 38.0)
2026-09-09
Grade Changed
Trust grade D → C
2026-09-09
Rank Moved
Rank rose 473 spots (#1167 → #694)
2026-09-09
HVTrust Changed
HVTrust up 18.6pts (38.2 → 56.8)
2026-09-08
Grade Changed
Trust grade C → D
2026-09-08
Rank Moved
Rank dropped 493 spots (#674 → #1167)
2026-09-08
HVTrust Changed
HVTrust down 18.8pts (57.0 → 38.2)
2026-09-07
Rank Moved
Rank dropped 47 spots (#627 → #674)
2026-09-06
Rank Moved
Rank dropped 11 spots (#616 → #627)
2026-09-05
Rank Moved
Rank dropped 74 spots (#542 → #616)
2026-09-04
Rank Moved
Rank dropped 26 spots (#516 → #542)
2026-09-03
Rank Moved
Rank dropped 24 spots (#492 → #516)
2026-09-02
Rank Moved
Rank dropped 21 spots (#471 → #492)
2026-09-01
Rank Moved
Rank dropped 13 spots (#458 → #471)
2026-08-31
Scorecard Added
OSSF Scorecard: 5.0/10
2026-08-31
Grade Changed
Trust grade D → C
2026-08-31
Rank Moved
Rank rose 658 spots (#1116 → #458)
2026-08-31
HVTrust Changed
HVTrust up 33.6pts (24.1 → 57.7)
2026-08-30
Rank Moved
Rank dropped 42 spots (#1074 → #1116)
2026-08-29
Rank Moved
Rank dropped 44 spots (#1030 → #1074)
2026-08-28
Rank Moved
Rank dropped 35 spots (#995 → #1030)
2026-08-27
Rank Moved
Rank dropped 24 spots (#971 → #995)
2026-08-26
Rank Moved
Rank dropped 104 spots (#867 → #971)
2026-08-24
Rank Moved
Rank dropped 14 spots (#856 → #870)
2026-08-22
Rank Moved
Rank rose 11 spots (#869 → #858)
2026-08-17
Rank Moved
Rank rose 11 spots (#872 → #861)
2026-08-16
Rank Moved
Rank dropped 24 spots (#848 → #872)
2026-08-10
Rank Moved
Rank dropped 50 spots (#794 → #844)
2026-08-08
Newly Listed
First tracked at rank #795

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 65.0 Grade B
Markdown:
[![HVTrust](https://hvtracker.net/badge/signoz-mcp-server.svg)](https://hvtracker.net/agents/signoz-mcp-server)
HTML:
<a href="https://hvtracker.net/agents/signoz-mcp-server"><img src="https://hvtracker.net/badge/signoz-mcp-server.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON