mcpbeat Sign in

Release Change Analyzer MCP Server

not responding

Release Change Analyzer is listed as active in the registry but did not answer our last check.

Summarize repository changes for a release

Uptime history 34 days of history · worst day 0%
34 days agonow
0.0%
Uptime 24h
0 of 90 checks
Tools
hidden behind auth
10 ms
Response time
average over 24h
open, no key
Access
streamable-http

Release Change Analyzer does not always answer

Over the last week it answered 0.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 13 min ago.

run in your terminal
claude mcp add release-change-analyzer --transport http https://openings-vote-drilling-initially.trycloudflare.com/mcp/release-change-analyzer
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "release-change-analyzer": {
      "url": "https://openings-vote-drilling-initially.trycloudflare.com/mcp/release-change-analyzer"
    }
  }
}
~/.codex/config.toml
[mcp_servers.release-change-analyzer]
url = "https://openings-vote-drilling-initially.trycloudflare.com/mcp/release-change-analyzer"
.cursor/mcp.json
{
  "mcpServers": {
    "release-change-analyzer": {
      "url": "https://openings-vote-drilling-initially.trycloudflare.com/mcp/release-change-analyzer"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "release-change-analyzer": {
      "url": "https://openings-vote-drilling-initially.trycloudflare.com/mcp/release-change-analyzer"
    }
  }
}

Endpoints

URLTransportStateLatencyChecked
https://openings-vote-drilling-initially.trycloudflare.com/mcp/release-change-analyzer streamable-http answering 10 ms 13 min ago

Alternatives to Release Change Analyzer

same job, measured the same way
Repo Release Tools
by anselmoo

Config-driven branch and release helpers for Git repositories

1 338 installs/wk local only
MCP Abap Adt
by fr0ster

MCP server for SAP ABAP ADT: repository analysis and CRUD for RAP and classic ABAP

296 installs/wk local only
Github Analytics MCP Server
by thenextgennexus

Get GitHub repository stats, search repos, analyze languages, and compare projects

14 installs/wk local only
Repo-to-RAG
by evozim

GitHub repository vectorizer and context synthesizer for RAG pipelines.

answering
I
Terraform Ingest MCP
by zloeber

Ingest and analyze Terraform modules from multiple repositories for AI RAG systems

274 installs/wk local only
Instagit
by instagitai

MCP server for Instagit — AI-powered Git repository analysis for coding agents

33 installs/wk local only
searchcode
by searchcode

Code intelligence for LLMs. Analyze, search, and retrieve code from any public git repository.

7 tools answering
Codacy
by mcparmory

Analyze code quality, security issues, and coverage across repositories

250 installs/wk local only

Release Change Analyzer — questions

Answers built from our own checks of this server.

Is Release Change Analyzer working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 90 checks got a reply (0.0%), average response time 10 ms. The bar chart above shows every period we have measured.
The registry lists Release Change Analyzer as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect Release Change Analyzer?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Release Change Analyzer need an API key?
No. Release Change Analyzer completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. This is what we observed, not what the docs claim.