mcpbeat Sign in

PingZen Uptime Monitoring MCP Server

answering

PingZen Uptime Monitoring is answering right now. Last checked 14 min ago.

Uptime monitoring with 127 tools across 23 protocols. Tag filtering + Code Mode.

Uptime history 47 days of history · worst day 87%
47 days agonow
98.9%
Uptime 24h
90 of 91 checks
Tools
hidden behind auth
309 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

PingZen Uptime Monitoring missed 2 checks this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of 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 14 min ago.

run in your terminal
claude mcp add mcp --transport http https://pingzen.dev/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://pingzen.dev/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.mcp]
url = "https://pingzen.dev/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://pingzen.dev/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://pingzen.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://pingzen.dev/mcp streamable-http sign-in 394 ms 14 min ago

Alternatives to PingZen Uptime Monitoring

same job, measured the same way
VMware Monitor
by zw008

Read-only VMware vCenter/ESXi monitoring with 27 MCP tools. Code-level safety.

3 221 installs/wk local only
Hyperping
by hyperping

Uptime, API and server monitoring with outages, reporting, on-call and status pages.

26 tools answering
mistaike.ai
by mistaike-ai

295k+ bug-fix patterns with MCP Hub proxy, PII filtering, and code search

answering
1ClickReport
by 1clickreport

75 tools for marketing analytics, campaign management and AI monitoring across 7 platforms.

answering
AitherOS ADK
by aitherium

Agent runtime with typed memory, knowledge and code graphs, plus file and web tools

1 827 installs/wk local only
Knowing
by blackwell-systems

Content-addressed code graph with 22 MCP tools for AI agents.

43 installs/wk local only
Cerebras Code MCP
by kevint-cerebras

Model Context Protocol (MCP) server for Cerebras to make coding faster in AI-first IDEs

88 installs/wk local only
URLs-LE
by nolindnaidoo

Extract URLs from documentation, configuration and code, with their protocol and position.

43 installs/wk local only

PingZen Uptime Monitoring — questions

Answers built from our own checks of this server.

Why is there no tool list for PingZen Uptime Monitoring?
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: 98.9% of checks in the last 24 hours got a reply.
Is PingZen Uptime Monitoring working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 90 of 91 checks got a reply (98.9%), average response time 309 ms. The bar chart above shows every period we have measured.
How do I connect PingZen Uptime Monitoring?
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. 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 PingZen Uptime Monitoring?
No API key is involved. PingZen Uptime Monitoring 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 PingZen Uptime Monitoring?
It answers our handshake in 309 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.