updated 2026-08-12 05:02 UTC

The MCP server for GoReleaser

goreleaser/mcp

The GoReleaser MCP

MCP Servers Go Grade D Listed MIT
43.3/100
Rank #560 of 1283
Compare The MCP server for GoReleaser

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade C · 2/5 signals
Last push
2026-08-10 · 2d ago
Recent change
Rank +1

Is The MCP server for GoReleaser safe? The MCP server for GoReleaser scores 43.3/100 (Grade D), ranked #560 of 1283 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; no OSSF Scorecard result yet; 100% of recent commits are signed; last pushed 2026-08-10. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#209 Scrcpy MCP — 43.5 (D) → #210 Illustrator MCP Server — 43.4 (D) → #212 Caldav MCP — 43.3 (D) → #213 AIquila — Nextcloud MCP Server — 43.2 (D) →

Quick Trust Read

What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-08-10
Rank Moved
Rank dropped 12 spots (#546 → #558)
2026-08-08
Newly Listed
First tracked at rank #544
Maintainer Checklist
Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.
Compare with another agent Get email alerts for The MCP server for GoReleaser View MCP Servers Report missing data
47.7
Activity sub-score · out of 100
#211
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 D 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-08-12 05:02 UTC · Repo last pushed 2 days ago

Rank Trend

2026-08-11 2026-08-12

Activity & Reach

Stars
22
Forks
4
Last Push
2026-08-10
2 days ago
Commits (4 wk)
7?
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
1
Rank Change
=
was #560

Analysis

HVTrust Dimensions vs MCP Servers

43.3 / 100 · 67.0% confidence

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

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
12.5 / 25
7.5 above avg 5.0
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.7 above avg 13.3
Transparency50% declared license · 50% OSSF Scorecard
8.5 / 17
in line with avg 8.8
Maintenance60% last-push freshness · 40% commit activity
13.7 / 20
1.3 above avg 12.4
AdoptionLog-scaled stars · package downloads
3.3 / 20
2.5 below avg 5.8

Activity Inputs

47.7 / 100
StarsRepository reach
8.2 / 30
FreshnessLast push recency
24.7 / 25
ActivityRecent commits
11.3 / 25
CommunityFork signal
3.3 / 20

Supply Chain Trust

Package Provenance
Verified
npm attestation
OSSF Scorecard
—
Not available
Signed Commits
100%
of last 100 commits verified

Is The MCP server for GoReleaser safe?

Public trust evidence for The MCP server for GoReleaser is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
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?
No OpenSSF Scorecard data is currently published for The MCP server for GoReleaser. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.
Is The MCP server for GoReleaser actively maintained?
Actively maintained. The repository was pushed to within the last 2 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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Listed 1Rank 1
2026-08-10
Rank Moved
Rank dropped 12 spots (#546 → #558)
2026-08-08
Newly Listed
First tracked at rank #544
GitHub → npm: @goreleaser/mcp

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 43.3 Grade D
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)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON