Is SigNoz MCP Server safe to use?

SigNoz MCP Server has an HVTrust score of 57.2/100 (Grade C), ranked #542 of 1320 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for SigNoz MCP Server?

SigNoz MCP Server scores 57.2/100 on HVTracker's evidence-weighted HVTrust scale. It has 118 GitHub stars and is categorized under MCP Servers.

SigNoz MCP Server

SigNoz/signoz-mcp-server

MCP Server for SigNoz

MCP Servers Go Grade C Listed Apache-2.0

57.2/100

Rank #542 of 1320

Compare SigNoz MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade C · 2/5 signals

Last push

2026-09-04 · 0d ago

Recent change

Rank +10

Is SigNoz MCP Server safe? SigNoz MCP Server scores 57.2/100 (Grade C), ranked #542 of 1320 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 4.8/10; 100% of recent commits are signed; last pushed 2026-09-04. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#251 Local Memory — 57.3 (C) → #252 Qdrant MCP Server — 57.3 (C) → #254 Rust MCP Sdk — 57.2 (C) → #255 Agent360 Browser MCP — 57.2 (C) →

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

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)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 4.8/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.

Compare with another agent Get email alerts for SigNoz MCP Server View MCP Servers Report missing data

60.1

Activity sub-score · out of 100

#253

In MCP Servers

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

Rank Trend

2026-08-11 2026-09-04

Activity & Reach

Stars

118

Forks

Last Push

2026-09-04

today

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▼26

was #516

Analysis

HVTrust Dimensions vs MCP Servers

57.2 / 100 · 100.0% confidence

SigNoz MCP Server MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

11.0 / 25

1.4 above avg 9.6

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.6 below avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

12.6 / 17

0.8 above avg 11.8

Maintenance60% last-push freshness · 40% commit activity

16.8 / 20

4.6 above avg 12.2

AdoptionLog-scaled stars · package downloads

5.0 / 20

1.3 below avg 6.3

Activity Inputs

60.1 / 100

StarsRepository reach

12.5 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

15.0 / 25

CommunityFork signal

7.6 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

4.8 / 10

OpenSSF Scorecard · scanned Sep 2, 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 3

Is SigNoz MCP Server safe?

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 4.8/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

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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

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

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

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