Is The MCP server for GoReleaser safe to use?

The MCP server for GoReleaser has an HVTrust score of 78.6/100 (Grade B), ranked #208 of 1374 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for The MCP server for GoReleaser?

The MCP server for GoReleaser scores 78.6/100 on HVTracker's evidence-weighted HVTrust scale. It has 22 GitHub stars and is categorized under MCP Servers.

The MCP server for GoReleaser

Repository

The GoReleaser MCP

MCP Servers Go Listed MIT

Is The MCP server for GoReleaser safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 6.3 / 10

Provenance Attested

Signed commits 100%

Last push yesterday

Advisories None known

Compare The MCP server for GoReleaser

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: The MCP server for GoReleaser scores 78.6/100 (Grade B), ranked #208 of 1374 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.3/10; 100% of recent commits are signed; no published advisory affects its latest release (@goreleaser/mcp); last pushed 2026-11-09. Every point is earned from checkable signals — never paid placement. How scoring works →

How The MCP server for GoReleaser could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Raise the OSSF Scorecard from 6.3 to 9.0lowest checks: Branch-Protection 0, CII-Best-Practices 0, Code-Review 0 +5.6 → 84.2 A · #42 of 778

Already done? Suggest a correction Add the trust badge

Chain of custody

Scanners check what the code says. This traces who ships The MCP server for GoReleaser and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

Source Signed

github.com/goreleaser/mcp, MIT, last pushed 2026-11-09. 100% of the last 100 commits carry a verified signature, so changes trace to a verified account.
Review and release Mixed

OpenSSF Scorecard rates the repository's practices 6.3/10 (scanned Nov 1, 2026). The checks that decide who can get a change released:
- Code Review0
- Branch Protection0
- Signed Releases8
- Dangerous Workflow10
- Token Permissions0
- Pinned Dependencies10
All 18 Scorecard checks

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 7
Published packages Linked and attested
- npm @goreleaser/mcp Source link points back to this repo Build provenance attested
What you install today No known advisories

Latest release checked: @goreleaser/mcp 0.8.0. No published advisory affects it (OSV, checked 2026-11-10).

Changes to this chain

2026-09-23 Package provenance attestation detected
2026-08-28 OSSF Scorecard: 6.4/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

GitHub repository data
Package downloads
Supply-chain checks
Public actions (missing)
Community mentions (missing)

Verify this score yourself

Every build re-issues The MCP server for GoReleaser’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How The MCP server for GoReleaser compares in MCP Servers

#116 MCP Observatory 78.6 ±0
#117 AirMCP 78.6 ±0
#118 The MCP server for GoReleaser 78.6 this agent
#119 XcodeBuildMCP 78.6 ±0
#120 DevSpace 78.6 ±0

Bars show each HVTrust score; the tick marks The MCP server for GoReleaser’s 78.6.

Where the 78.6 comes from

HVTrust dimensions vs the MCP Servers average

78.6 / 100 · 100.0% confidence

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

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

20.4 / 25

9.6 above avg 10.8

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.3 above avg 13.7

Transparency50% declared license · 50% OSSF Scorecard

13.9 / 17

1.6 above avg 12.3

Maintenance60% last-push freshness · 40% commit activity

13.7 / 20

1.5 above avg 12.2

AdoptionLog-scaled stars · package downloads

6.6 / 20

1.0 below avg 7.6

Quick Trust Read

What Would Improve It

Improve adoption to lift the weakest part of the trust profile.

Recent Changes

2026-11-05

Grade Changed

Trust grade A → B

2026-11-05

Rank Moved

Rank dropped 29 spots (#178 → #207)

2026-11-04

Grade Changed

Trust grade B → A

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 6.3/10. Tighten the weakest checks to improve public safety evidence.

Compare with another agent View MCP Servers Report missing data

48.1

Activity sub-score · out of 100

#118

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

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars

Forks

Last Push

2026-11-09

yesterday

Commits (4 wk)

Downloads (7d)

319

npm

HN mentions (30d)

—

Open Issues

Rank Change

▼1

was #207

Analysis

Activity Inputs

48.1 / 100

StarsRepository reach

8.2 / 30

FreshnessLast push recency

24.9 / 25

ActivityRecent commits

11.3 / 25

CommunityFork signal

3.6 / 20

Common questions about The MCP server for GoReleaser

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.3/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

How this surface has changed

Detected changes to The MCP server for GoReleaser'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

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

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

2026-11-05

Grade Changed

Trust grade A → B

2026-11-05

Rank Moved

Rank dropped 29 spots (#178 → #207)

2026-11-04

Grade Changed

Trust grade B → A

2026-11-04

Rank Moved

Rank rose 42 spots (#220 → #178)

2026-11-03

Rank Moved

Rank dropped 11 spots (#209 → #220)

2026-10-28

Rank Moved

Rank rose 11 spots (#201 → #190)

2026-10-25

Rank Moved

Rank rose 13 spots (#209 → #196)

2026-10-09

Rank Moved

Rank dropped 10 spots (#187 → #197)

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

2026-09-23

Grade Changed

Trust grade D → B

2026-09-23

Rank Moved

Rank rose 623 spots (#797 → #174)

2026-09-23

HVTrust Changed

HVTrust up 49.0pts (28.8 → 77.8)

2026-09-22

Newly Listed

First tracked at rank #797

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-17

Grade Changed

Trust grade A → B

2026-09-17

Rank Moved

Rank dropped 35 spots (#136 → #171)

2026-09-15

Grade Changed

Trust grade B → A

2026-09-15

Rank Moved

Rank rose 32 spots (#166 → #134)

2026-09-07

Rank Moved

Rank dropped 17 spots (#142 → #159)

2026-09-05

Rank Moved

Rank dropped 30 spots (#110 → #140)

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)

GitHub → npm: @goreleaser/mcp

Embed Badge Badge guide for maintainers →

For maintainers

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.4 · Raw JSON

The MCP server for GoReleaser

How The MCP server for GoReleaser could raise its score

Chain of custody

Source Signed

Review and release Mixed

Published packages Linked and attested

What you install today No known advisories

Changes to this chain

Evidence behind this score

Verify this score yourself

What this score doesn’t check

How The MCP server for GoReleaser compares in MCP Servers

Where the 78.6 comes from

HVTrust dimensions vs the MCP Servers average

Quick Trust Read

Rank Trend

Activity & Reach

Analysis

Activity Inputs

Common questions about The MCP server for GoReleaser

AI agent surface

Maintain The MCP server for GoReleaser?

Reputation Timeline

Embed Badge Badge guide for maintainers →

Other agents in MCP Servers