Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

The MCP server for GoReleaser

OCI · GHCR.IO/GORELEASER/MCP:0.6.0 · 2 COMPONENTS · SCANNED SEP 29

GoReleaser MCP server

Available components

npm · @goreleaser/mcp 47 oci · ghcr.io/goreleaser/mcp:0.6.0 55
+10 this week 55 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security0
  • No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
  • Known CVEs could not be checked: this image's dependency list comes from an SBOM its publisher attached, which nothing verifies, so we will not report it as a clean result.Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: this image's dependency list comes from an SBOM its publisher attached. It names packages and versions but not whether each is deprecated, still maintained or linked to its source, so there is nothing we can fairly grade.Unverified
Provenance & Transparency84
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to goreleaser/mcp). View diagnostics → Pass
  • License check failed: no license is declared. See how to fix → Fail
  • Actively maintained (last published 35 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability38
  • 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 859 tokens (~7/item across 111 items; 1 tools + 110 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
  • Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Install

How do I install the The MCP server for GoReleaser server?

The MCP server for GoReleaser runs locally as a container image, launched with docker run --rm -i ghcr.io/goreleaser/mcp:0.6.0. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

oci · ghcr.io/goreleaser/mcp:0.6.0

# add to Claude Code
claude mcp add goreleaser-mcp -- docker run --rm -i ghcr.io/goreleaser/mcp:0.6.0
// .cursor/mcp.json
{
  "mcpServers": {
    "goreleaser-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/goreleaser/mcp:0.6.0"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "goreleaser-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/goreleaser/mcp:0.6.0"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add goreleaser-mcp -- docker run --rm -i ghcr.io/goreleaser/mcp:0.6.0
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "goreleaser-mcp": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "ghcr.io/goreleaser/mcp:0.6.0"
      ],
      "enabled": true
    }
  }
}
# ~/.hermes/config.yaml
mcp_servers:
  goreleaser-mcp:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/goreleaser/mcp:0.6.0"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "goreleaser-mcp": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/goreleaser/mcp:0.6.0"
      ]
    }
  }
}
// mcp.json
{
  "mcpServers": {
    "goreleaser-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/goreleaser/mcp:0.6.0"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 28 Sept 26 +11
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 25 Sept 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 24 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 23 Sept 26 0
    • Stability: 0.97 → pass security
  • 22 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 29 Sept 2026 · Analysed oci/ghcr.io/goreleaser/mcp:0.6.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem oci
Reason Verified
Discovered via GitHub artifact attestations
Source repo goreleaser/mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/goreleaser/mcp/.github/workflows/release.yml@refs/tags/v0.6.0
Rekor log index 2579301181
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha256:69237abddbf07ff6c96f65b2e1b9084be9b6e8ef430a489db740eab33b5c6acc

Background: How many MCP packages publish verified provenance →

MCP tools · 1 exposed · ~44 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
check ~44

Checks a GoReleaser configuration for errors or deprecations

NameTypeReqDescription
configurationstring–Path to the goreleaser YAML configuration file. If empty will use the default.
NameTypeReqDescription
filepathstringyes–
instructionsstring––
messagestringyes–

No examples provided.

Common questions

What is the The MCP server for GoReleaser server?

The MCP server for GoReleaser is listed in the public MCP registry as io.github.goreleaser/mcp. GoReleaser MCP server. This page covers its container image (ghcr.io/goreleaser/mcp:0.6.0).

Is the The MCP server for GoReleaser server safe to use?

The MCP server for GoReleaser scores 55 out of 100 on VerifyMCP. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the The MCP server for GoReleaser server expose?

The MCP server for GoReleaser exposes 1 tool: check. Their descriptions and schemas cost roughly 44 tokens of context every time the server is loaded.

Is the The MCP server for GoReleaser server still maintained?

The MCP server for GoReleaser is still listed as active in the MCP registry. We last reached this channel on 29 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.