mcpbeat Sign in

Chipp Releases MCP Server

answering

Chipp Releases is answering right now. Last checked 3 min ago.

Chipp: software factory deploys and releases: history, the deploy gate, Deploy now, rollbacks.

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

Nothing serious here today

Today is the operative word: we check Chipp Releases 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 3 min ago.

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

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.chipp.ai/mcp/releases streamable-http sign-in 471 ms 3 min ago

Alternatives to Chipp Releases

same job, measured the same way
Y
Yeku
by yeku

deploy the software your AI builds you

answering
NEXUS AI
by nexusrun

Deploy full-stack apps with databases, storage, backups, logs, scaling, and rollback. 74 MCP tools.

answering
i3deploy
by i3deploy

Deploy & release tracking with native MCP — ask Claude what's in production and cut the release.

answering
DeployAngel
by deployangel

Wait for production to clear each deploy, and read the evidence when a release fails.

1 411 installs/wk local only
Mayorana
by bennekrouf

Search mayorana.ch: desktop apps, release notes, plans, and the Rust, LLM and Azure blog.

7 tools answering
Groundwork
by nickjlamb

Deployment-readiness checks for document-QA and extraction AI: grounding, extraction, CI gate.

50 installs/wk local only
Gheima
by gheima

Deploy and run apps, databases and storage on the Gheima platform, billed in MAD.

26 installs/wk answering
The Deploy Log
by deployedbyai

AI deployments that shipped and are available now, each sourced to the publisher's own page.

3 tools answering

Chipp Releases — questions

Answers built from our own checks of this server.

Why is there no tool list for Chipp Releases?
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 Chipp Releases 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 480 ms. The bar chart above shows every period we have measured.
How do I connect Chipp Releases?
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 Chipp Releases?
No API key is involved. Chipp Releases 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 Chipp Releases?
It answers our handshake in 480 ms on average, which is faster than 26% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.