mcpbeat Sign in

PingWise MCP Server

answering

PingWise is answering right now. Last checked 13 min ago.

Uptime monitoring: read monitors, incidents and response times; create and change monitors.

Uptime history 17 hours of history
17 hours agonow
100.0%
Uptime 24h
62 of 62 checks
—
Tools
hidden behind auth
187 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check PingWise 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 pingwise --transport http https://app.pingwise.com/mcp
Settings → Connectors → Add custom connector, then paste this address
https://app.pingwise.com/mcp
~/.codex/config.toml
[mcp_servers.pingwise]
url = "https://app.pingwise.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "pingwise": {
      "url": "https://app.pingwise.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "pingwise": {
      "type": "http",
      "url": "https://app.pingwise.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://app.pingwise.com/mcp streamable-http sign-in 308 ms 13 min ago

Alternatives to PingWise

same job, measured the same way
Pingstack
by pingstack

Cron, uptime, DNS, SSL and domain monitoring. Create checks and read incidents and uptime.

answering
StatOSS
by statoss

Status pages and uptime monitoring: read status, monitors and incidents; open incidents.

answering
SolidPing
by fclairamb

Self-hostable uptime monitoring: create checks, read incidents, manage status pages.

answering
YoPingMe uptime monitoring
by yoping

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

answering
BadgerBell
by badgerbell

Uptime monitoring and status pages: set up monitors, read incidents, draft status updates.

answering
SutramX
by sutramx

SutramX uptime monitoring: monitors, check results, incidents, status pages and uptime/SLO reports.

62 installs/wk local only
Repose
by vncntknl

Uptime monitoring that doesn't cry wolf: manage monitors, read incidents, record deploys.

answering
UptimeRobot
by uptimerobot

Monitor websites, APIs, and servers: create monitors, triage incidents, and query uptime stats.

answering

PingWise — questions

Answers built from our own checks of this server.

Why is there no tool list for PingWise?
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 PingWise working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 62 of 62 checks got a reply (100.0%), average response time 187 ms. The bar chart above shows every period we have measured.
How do I connect PingWise?
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 PingWise?
No API key is involved. PingWise 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 PingWise?
It answers our handshake in 187 ms on average, which is faster than 71% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.