mcpbeat Sign in

YoPingMe uptime monitoring MCP Server

answering

YoPingMe uptime monitoring is answering right now. Last checked 13 min ago.

Website uptime monitoring: live status, uptime reports, incidents, response times, failed checks

Uptime history 10 days of history · worst day 99%
10 days agonow
100.0%
Uptime 24h
91 of 91 checks
Tools
hidden behind auth
193 ms
Response time
average over 24h
API key or OAuth
Access
streamable-http

Nothing serious here today

Today is the operative word: we check YoPingMe uptime monitoring 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 13 min ago.

run in your terminal
claude mcp add uptime --transport http https://app.yoping.me/api/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "uptime": {
      "url": "https://app.yoping.me/api/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.uptime]
url = "https://app.yoping.me/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "uptime": {
      "url": "https://app.yoping.me/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "uptime": {
      "url": "https://app.yoping.me/api/mcp"
    }
  }
}

This endpoint answered with an authorization challenge — the server is running, but you need an API key or OAuth to use it.

Endpoints

URLTransportStateLatencyChecked
https://app.yoping.me/api/mcp streamable-http needs key 372 ms 13 min ago

Alternatives to YoPingMe uptime monitoring

same job, measured the same way
Hyperping
by hyperping

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

26 tools answering
Checkly
by usefulapi

Query Checkly synthetic monitoring — checks, statuses, results, alerts, reporting and dashboards.

22 tools answering
DebugBundle
by debugbundle

DebugBundle MCP: runtime error reporting, incident response, health checks, and product analytics.

192 installs/wk local only
Safeship
by safeship

API monitoring from your editor. Checks the JSON your endpoints return, not just the status code.

answering
Nslookup
by venomseven

DNS lookups, health reports, SSL certs, security scans, GEO scoring, uptime checks

88 installs/wk 23 tools answering
Umami
by mikusnuz

MCP server for Umami Analytics API v2 — websites, stats, events, reports, and realtime

169 installs/wk local only
StillOnline
by shenwell

StillOnline MCP: uptime, status pages, checks. REST API for Cursor and Claude Code.

47 installs/wk local only
Carrierscore
by carrierscore

FMCSA motor-carrier risk scores, monitoring, and carrier-selection evidence reports for AI agents.

8 tools answering

YoPingMe uptime monitoring — questions

Answers built from our own checks of this server.

Why is there no tool list for YoPingMe 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: 100.0% of checks in the last 24 hours got a reply.
Is YoPingMe uptime monitoring 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 193 ms. The bar chart above shows every period we have measured.
How do I connect YoPingMe 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 will need your own key or an OAuth login: it refuses anonymous clients.
Does YoPingMe uptime monitoring need an API key?
Yes. Every time we knock, YoPingMe uptime monitoring answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.
How fast is YoPingMe uptime monitoring?
It answers our handshake in 193 ms on average, which is faster than 73% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.