Red Hat Lightspeed MCP

An MCP server to connect Red Hat Lightspeed functionality to an AI / LLM

MCP Servers Python Grade C Listed Apache-2.0
62.3/100
Rank #533 of 1328
Compare Red Hat Lightspeed MCP

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-12 · 1d ago
Recent change
Grade Changed +6

Is Red Hat Lightspeed MCP safe? Red Hat Lightspeed MCP scores 62.3/100 (Grade C), ranked #533 of 1328 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 6.5/10; 100% of recent commits are signed; last pushed 2026-09-12. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-09
Grade Changed
Trust grade D → C
2026-09-09
Rank Moved
Rank rose 568 spots (#1089 → #521)
2026-09-09
HVTrust Changed
HVTrust up 20.1pts (42.3 → 62.4)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 6.5/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.
62.8
Activity sub-score · out of 100
#300

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 →

Signals refreshed 2026-09-13 20:11 UTC · Repo last pushed yesterday

Rank Trend

2026-08-11 2026-09-13

Activity & Reach

Stars
24
Forks
38
Last Push
2026-09-12
yesterday
Commits (4 wk)
58
Downloads (7d)
HN mentions (30d)
Open Issues
5
Rank Change
▼4
was #529

Analysis

HVTrust Dimensions vs MCP Servers

62.3 / 100 · 100.0% confidence

Red Hat Lightspeed MCP MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
13.1 / 25
3.0 above avg 10.1
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.6 below avg 13.4
Transparency50% declared license · 50% OSSF Scorecard
14.0 / 17
1.9 above avg 12.1
Maintenance60% last-push freshness · 40% commit activity
19.0 / 20
6.9 above avg 12.1
AdoptionLog-scaled stars · package downloads
3.4 / 20
3.6 below avg 7.0

Activity Inputs

62.8 / 100
StarsRepository reach
8.4 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
22.1 / 25
CommunityFork signal
7.4 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
6.5 / 10
OpenSSF Scorecard · scanned Sep 13, 2026
Signed Commits
100%
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 10
SAST 5
Security-Policy 0
Signed-Releases 0
Token-Permissions 0
Vulnerabilities 8

Is Red Hat Lightspeed MCP safe?

Red Hat Lightspeed MCP 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 Red Hat Lightspeed MCP publish package provenance?
No published build provenance is currently detected for Red Hat Lightspeed MCP. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Red Hat Lightspeed MCP have an OpenSSF Scorecard?
Red Hat Lightspeed MCP has an OpenSSF Scorecard score of 6.5/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 Red Hat Lightspeed MCP actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Red Hat Lightspeed MCP use?
Red Hat Lightspeed MCP ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Red Hat Lightspeed MCP's commits signed?
100% of the last 100 commits to Red Hat Lightspeed MCP 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
Red Hat Lightspeed MCP appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
None detected
No clear third-party provider dependency detected.
Credential signal: No explicit API-key/config marker detected.
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 Red Hat Lightspeed MCP?

For maintainers

HVTrust scores Red Hat Lightspeed MCP 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 16HVTrust 3Grade 3Listed 1Scorecard 1
2026-09-09
Grade Changed
Trust grade D → C
2026-09-09
Rank Moved
Rank rose 568 spots (#1089 → #521)
2026-09-09
HVTrust Changed
HVTrust up 20.1pts (42.3 → 62.4)
2026-09-08
Grade Changed
Trust grade C → D
2026-09-08
Rank Moved
Rank dropped 580 spots (#509 → #1089)
2026-09-08
HVTrust Changed
HVTrust down 20.2pts (62.5 → 42.3)
2026-09-07
Rank Moved
Rank dropped 27 spots (#482 → #509)
2026-09-05
Rank Moved
Rank dropped 72 spots (#403 → #475)
2026-09-04
Rank Moved
Rank dropped 25 spots (#378 → #403)
2026-09-03
Rank Moved
Rank dropped 17 spots (#361 → #378)
2026-09-02
Rank Moved
Rank rose 15 spots (#376 → #361)
2026-09-01
Rank Moved
Rank dropped 14 spots (#362 → #376)
2026-08-31
Rank Moved
Rank dropped 22 spots (#340 → #362)
2026-08-29
Scorecard Added
OSSF Scorecard: 6.5/10
2026-08-29
Grade Changed
Trust grade D → C
2026-08-29
Rank Moved
Rank rose 665 spots (#1011 → #346)
2026-08-29
HVTrust Changed
HVTrust up 36.7pts (24.8 → 61.5)
2026-08-28
Rank Moved
Rank dropped 42 spots (#969 → #1011)
2026-08-27
Rank Moved
Rank dropped 24 spots (#945 → #969)
2026-08-26
Rank Moved
Rank dropped 107 spots (#838 → #945)
2026-08-16
Rank Moved
Rank dropped 18 spots (#819 → #837)
2026-08-12
Rank Moved
Rank rose 10 spots (#822 → #812)
2026-08-10
Rank Moved
Rank dropped 43 spots (#778 → #821)
2026-08-08
Newly Listed
First tracked at rank #771

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 62.3 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/red-hat-lightspeed-mcp.svg)](https://hvtracker.net/agents/red-hat-lightspeed-mcp)
HTML:
<a href="https://hvtracker.net/agents/red-hat-lightspeed-mcp"><img src="https://hvtracker.net/badge/red-hat-lightspeed-mcp.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