Release Change Analyzer

io.github.Wxt-aiPublished by GitHub account Wxt-aiv1.0.7Updated Oct 8, 2026

Summarize repository changes for a release

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

Remote MCP server that summarizes repository changes for a release, letting an assistant turn code changes into release notes.

What you can do
  • Summarize repository changes for a release.
  • No tool list, instructions or README is published, so the exact operations and inputs are not documented; the only stated capability is producing a summary of changes for a release.
When to use it
Consider it when you want an assistant to condense a repository's changes into a release summary, for example while preparing release notes. Because the tool set is undocumented, verify what it actually does before relying on it.
Requirements
A remote streamable HTTP endpoint; no package, environment variables or headers are declared. No authentication is declared, so nothing is needed to connect, but the endpoint is a temporary-looking tunnel host that may not be stable.
Before you install
The endpoint is an unauthenticated third-party tunnel address, so anything sent to it leaves your machine and is not protected by credentials. No tool list or documentation is published, so what data it reads or sends cannot be verified; avoid passing private repository content until you trust the operator.

Installation

In SourceWeft

  1. Open Release Change Analyzer in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Wxt-ai%2Frelease-change-analyzer/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "release-change-analyzer": {
      "type": "http",
      "url": "https://openings-vote-drilling-initially.trycloudflare.com/mcp/release-change-analyzer"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.7LatestSep 16, 2026

Score

28% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.