mcpbeat Sign in

Runzumi MCP Server

by runzumi-mcp Your server? Claim it
answering

Runzumi is answering right now. Last checked 4 min ago.

Explore GitHub Actions job performance, compute costs and failures with Runzumi analytics.

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

Nothing serious here today

Today is the operative word: we check Runzumi 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 4 min ago.

run in your terminal
claude mcp add runzumi --transport http https://mcp.runzumi.com/mcp
Settings → Connectors → Add custom connector, then paste this address
https://mcp.runzumi.com/mcp
~/.codex/config.toml
[mcp_servers.runzumi]
url = "https://mcp.runzumi.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "runzumi": {
      "url": "https://mcp.runzumi.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "runzumi": {
      "type": "http",
      "url": "https://mcp.runzumi.com/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.runzumi.com/mcp streamable-http sign-in 452 ms 4 min ago

Alternatives to Runzumi

same job, measured the same way
Github Actions
by ofershap

GitHub Actions MCP — view runs, read logs, re-run jobs, and manage CI/CD.

52 installs/wk local only
GitHub CI/CD MCP Server
by devstephenke-sys

GitHub CI/CD MCP server with 70 tools for repos, PRs, Actions, deployments, billing, and more.

47 installs/wk local only
Google Analytics
by mcparmory

Query GA4 analytics data with custom reports, pivot tables, and audience exports

206 installs/wk local only
opsen
by opsen

Engineering spend: GitHub seats, Copilot, Actions and coding agents, priced, with fixes

answering
Regulatory Signals
by rikocr8orh8

Audit GitHub repos for security, compliance, and EU AI Act exposure from Claude or Cursor.

67 installs/wk local only
Scanduro
by sssnl-nl

Remote MCP server for Scanduro QR codes, scan analytics and controlled code actions.

answering
GitDiagram
by gitdiagram

Architecture diagrams, explanations and Mermaid source for public GitHub repositories.

3 tools answering
S
Speedvault
by speedvault

Run web performance audits, get code-level fixes, crawl for SEO, and read real-user Core Web Vitals.

48 installs/wk local only

Runzumi — questions

Answers built from our own checks of this server.

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