The MCP server for GoReleaser

The GoReleaser MCP

MCP Servers Go Grade B Listed MIT
78.8/100
Rank #109 of 1320
Compare The MCP server for GoReleaser

Strong public trust posture, backed by multiple independent signals.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade B · 3/5 signals
Last push
2026-09-03 · 1d ago
Recent change
Grade Changed +9

Is The MCP server for GoReleaser safe? The MCP server for GoReleaser scores 78.8/100 (Grade B), ranked #109 of 1320 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 6.4/10; 100% of recent commits are signed; last pushed 2026-09-03. 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
Improve adoption to lift the weakest part of the trust profile.
Recent Changes
2026-09-02
Grade Changed
Trust grade C → B
2026-09-02
Rank Moved
Rank rose 521 spots (#622 → #101)
2026-09-02
HVTrust Changed
HVTrust up 26.3pts (52.4 → 78.7)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 6.4/10. Tighten the weakest checks to improve public safety evidence.
48.3
Activity sub-score · out of 100
#48

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-04 14:33 UTC · Repo last pushed yesterday

Rank Trend

2026-08-11 2026-09-04

Activity & Reach

Stars
22
Forks
4
Last Push
2026-09-03
yesterday
Commits (4 wk)
8?
Downloads (7d)
293
npm
HN mentions (30d)
Open Issues
0
Rank Change
▼5
was #104

Analysis

HVTrust Dimensions vs MCP Servers

78.8 / 100 · 100.0% confidence

The MCP server for GoReleaser MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
20.5 / 25
11.0 above avg 9.5
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.6 above avg 13.4
Transparency50% declared license · 50% OSSF Scorecard
13.9 / 17
2.1 above avg 11.8
Maintenance60% last-push freshness · 40% commit activity
13.8 / 20
1.6 above avg 12.2
AdoptionLog-scaled stars · package downloads
6.6 / 20
in line with avg 6.2

Activity Inputs

48.3 / 100
StarsRepository reach
8.2 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
11.9 / 25
CommunityFork signal
3.3 / 20

Supply Chain Trust

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

Is The MCP server for GoReleaser safe?

Public supply-chain signals for The MCP server for GoReleaser are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but The MCP server for GoReleaser carries less obvious unverified-evidence risk than projects with thin signals.
Does The MCP server for GoReleaser publish package provenance?
Yes. The MCP server for GoReleaser's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does The MCP server for GoReleaser have an OpenSSF Scorecard?
The MCP server for GoReleaser has an OpenSSF Scorecard score of 6.4/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 The MCP server for GoReleaser actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does The MCP server for GoReleaser use?
The MCP server for GoReleaser ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are The MCP server for GoReleaser's commits signed?
100% of the last 100 commits to The MCP server for GoReleaser 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
medium confidence
Implemented
The MCP server for GoReleaser 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
high confidence
Match
Published package metadata matches the tracked repo
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live

Maintain The MCP server for GoReleaser?

For maintainers

HVTrust scores The MCP server for GoReleaser 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 11HVTrust 2Grade 2Listed 1Scorecard 1
2026-09-02
Grade Changed
Trust grade C → B
2026-09-02
Rank Moved
Rank rose 521 spots (#622 → #101)
2026-09-02
HVTrust Changed
HVTrust up 26.3pts (52.4 → 78.7)
2026-09-01
Rank Moved
Rank dropped 24 spots (#598 → #622)
2026-08-31
Rank Moved
Rank dropped 26 spots (#572 → #598)
2026-08-29
Rank Moved
Rank dropped 27 spots (#538 → #565)
2026-08-28
Scorecard Added
OSSF Scorecard: 6.4/10
2026-08-28
Grade Changed
Trust grade D → C
2026-08-28
Rank Moved
Rank rose 152 spots (#690 → #538)
2026-08-28
HVTrust Changed
HVTrust up 8.9pts (43.2 → 52.1)
2026-08-27
Rank Moved
Rank dropped 22 spots (#668 → #690)
2026-08-26
Rank Moved
Rank dropped 100 spots (#568 → #668)
2026-08-19
Rank Moved
Rank dropped 10 spots (#564 → #574)
2026-08-17
Rank Moved
Rank rose 15 spots (#581 → #566)
2026-08-13
Rank Moved
Rank dropped 15 spots (#555 → #570)
2026-08-10
Rank Moved
Rank dropped 12 spots (#546 → #558)
2026-08-08
Newly Listed
First tracked at rank #544

Embed Badge Badge guide for maintainers →

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

Other agents in MCP Servers

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