Is Rootly MCP Server safe to use?

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

What is the trust score for Rootly MCP Server?

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

Rootly MCP Server

rootlyhq/rootly-mcp-server

Rootly MCP server

MCP Servers Python Listed Apache-2.0

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

OSSF Scorecard 7.9 / 10

Provenance None

Signed commits 36%

Last push yesterday

Compare Rootly MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Rootly MCP Server scores 61.9/100 (Grade C), ranked #575 of 1325 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 7.9/10; 36% of recent commits are signed; last pushed 2026-09-25. Every point is earned from checkable signals — never paid placement. How scoring works →

How Rootly MCP Server compares in MCP Servers

Bars show each HVTrust score; the tick marks Rootly MCP Server’s 61.9.

Where the 61.9 comes from

HVTrust dimensions vs the MCP Servers average

61.9 / 100 · 100.0% confidence

Rootly MCP Server MCP Servers average (775 agents)

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

11.7 / 25

1.4 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

15.2 / 17

3.0 above avg 12.2

Maintenance60% last-push freshness · 40% commit activity

19.2 / 20

7.2 above avg 12.0

AdoptionLog-scaled stars · package downloads

4.0 / 20

3.2 below 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-25

Rank Moved

Rank dropped 18 spots (#558 → #576)

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: Google Gemini

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

Maintainer Checklist

Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.

Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.

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

64.0

Activity sub-score · out of 100

#325

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-26

Activity & Reach

Stars

Forks

Last Push

2026-09-25

yesterday

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▲1

was #576

Analysis

Activity Inputs

64.0 / 100

StarsRepository reach

10.0 / 30

FreshnessLast push recency

24.9 / 25

ActivityRecent commits

22.6 / 25

CommunityFork signal

6.4 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

7.9 / 10

OpenSSF Scorecard · scanned Sep 25, 2026

Signed Commits

36%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 5

CI-Tests 10

CII-Best-Practices 0

Code-Review 10

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging -1

Pinned-Dependencies 7

SAST 0

Security-Policy 10

Signed-Releases -1

Token-Permissions 10

Vulnerabilities 8

Common questions about Rootly MCP Server

Rootly 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 Rootly MCP Server publish package provenance?

No published build provenance is currently detected for Rootly 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 Rootly MCP Server have an OpenSSF Scorecard?

Rootly MCP Server has an OpenSSF Scorecard score of 7.9/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 Rootly MCP Server actively maintained?

Actively maintained. The repository was pushed to within the last 1 day(s).

What license does Rootly MCP Server use?

Rootly MCP Server ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Rootly MCP Server's commits signed?

36% of the last 100 commits to Rootly 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

Rootly MCP Server appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

1 detected

Public provider/service dependencies detected.

Google Gemini

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 Rootly 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

Provider Added

Runtime surface grew — new detected provider dependency: Google Gemini

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

Maintain Rootly MCP Server?

For maintainers

HVTrust scores Rootly 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-25

Rank Moved

Rank dropped 18 spots (#558 → #576)

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: Google Gemini

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Rank Moved

Rank dropped 217 spots (#338 → #555)

2026-09-23

HVTrust Changed

HVTrust up 11.4pts (50.9 → 62.3)

2026-09-22

Newly Listed

First tracked at rank #338

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-14

Rank Moved

Rank rose 47 spots (#578 → #531)

2026-09-13

Rank Moved

Rank dropped 14 spots (#564 → #578)

2026-09-09

Rank Moved

Rank dropped 10 spots (#539 → #549)

2026-09-07

Rank Moved

Rank dropped 34 spots (#509 → #543)

2026-09-06

Rank Moved

Rank dropped 15 spots (#494 → #509)

2026-09-05

Rank Moved

Rank dropped 77 spots (#417 → #494)

2026-09-04

Rank Moved

Rank dropped 10 spots (#407 → #417)

2026-09-03

Rank Moved

Rank dropped 22 spots (#385 → #407)

2026-08-31

Rank Moved

Rank dropped 23 spots (#347 → #370)

2026-08-30

Rank Moved

Rank rose 27 spots (#374 → #347)

2026-08-27

Rank Moved

Rank dropped 14 spots (#357 → #371)

2026-08-26

Scorecard Added

OSSF Scorecard: 7.3/10

2026-08-26

Grade Changed

Trust grade D → C

2026-08-26

Rank Moved

Rank rose 566 spots (#923 → #357)

2026-08-26

HVTrust Changed

HVTrust up 37.2pts (23.0 → 60.2)

2026-08-24

Rank Moved

Rank dropped 16 spots (#912 → #928)

2026-08-20

Rank Moved

Rank dropped 11 spots (#906 → #917)

2026-08-17

Rank Moved

Rank rose 16 spots (#917 → #901)

2026-08-16

Rank Moved

Rank dropped 20 spots (#897 → #917)

2026-08-14

Rank Moved

Rank rose 13 spots (#906 → #893)

2026-08-12

Rank Moved

Rank rose 13 spots (#910 → #897)

2026-08-10

Rank Moved

Rank dropped 40 spots (#859 → #899)

2026-08-08

Newly Listed

First tracked at rank #856

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/rootly-mcp-server.svg)](https://hvtracker.net/agents/rootly-mcp-server)
            
HTML:
            <a href="https://hvtracker.net/agents/rootly-mcp-server"><img src="https://hvtracker.net/badge/rootly-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