mcpbeat Sign in

Dev Changes MCP Server

answering

Dev Changes is answering right now. Last checked 6 min ago.

Turn described changes into reviewed pull requests: propose, triage, review, dependency audits.

Uptime history 91 days of history · worst day 64%
91 days agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
237 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Dev Changes every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

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 6 min ago.

run in your terminal
claude mcp add dev-changes --transport http https://mcp.openhelm.ai/dev/mcp
Settings → Connectors → Add custom connector, then paste this address
https://mcp.openhelm.ai/dev/mcp
~/.codex/config.toml
[mcp_servers.dev-changes]
url = "https://mcp.openhelm.ai/dev/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "dev-changes": {
      "url": "https://mcp.openhelm.ai/dev/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "dev-changes": {
      "type": "http",
      "url": "https://mcp.openhelm.ai/dev/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://mcp.openhelm.ai/dev/mcp streamable-http sign-in 272 ms 6 min ago

Alternatives to Dev Changes

same job, measured the same way
Localhero.ai
by localhero

Manage product translations from Claude and ship reviewed changes as GitHub pull requests.

answering
Celmis
by constantinemakoid

Self-hosted code intelligence: cross-repo Q&A, dependency audits and PR review, over MCP

local only
Tenpace Review Router
by patrax

Human-authenticated setup for routing GitHub pull requests into the right Slack channel.

5 tools answering
Tenpace Review Router
by tenpace-app

Human-authenticated setup for routing GitHub pull requests into the right Slack channel.

5 tools answering
featury
by featury

Ask what your product does, triage requests and publish the changelog, from a map of your code.

answering
Relay
by vishnumuthyalu

Turn GitHub pushes into plain-English client update emails. Map repos to clients and review digests.

answering
Graphify
by graphify-labs

Search indexed code, trace dependencies, assess change impact, and recall repository memory.

answering
Standupbot
by rimysore

Turns your GitHub activity into a daily standup — commits, PRs, reviews & issues.

33 installs/wk local only

Dev Changes — questions

Answers built from our own checks of this server.

Why is there no tool list for Dev Changes?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is Dev Changes working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 237 ms. The bar chart above shows every period we have measured.
How do I connect Dev Changes?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to Dev Changes?
No API key is involved. Dev Changes answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is Dev Changes?
It answers our handshake in 237 ms on average, which is faster than 60% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.