PingZen Uptime Monitoring
Monitor websites, APIs, and services from your agent with PingZen’s broad protocol coverage and uptime tooling.
Overview
dev.pingzen/mcp is an MCP server for the Operate phase that monitors websites, APIs, and services with 44 tools across 22 protocols via PingZen.
What is this MCP server?
- 44 MCP tools across 22 monitoring protocols (per server description)
- PingZen Uptime Monitoring remote at https://pingzen.dev/mcp with API key or JWT auth
- Optional self-hosted stdio via Docker image ilyakong/pingzen-mcp:0.9.3
- Bearer API keys prefixed pz_ or JWT from PingZen
- Version 0.9.3 with PostgreSQL-backed self-host env vars documented
- 44 tools across 22 protocols (catalog description)
- Package version 0.9.3
- Docker image: docker.io/ilyakong/pingzen-mcp:0.9.3
What problem does it solve?
Keeping dozens of endpoints and protocols healthy forces constant dashboard context-switching that your coding agent cannot see by default.
Who is it for?
Indie SaaS and API operators who want agent-driven uptime management across many check types and hosted or Docker MCP setups.
Skip if: Pre-launch prototypes with no production URLs, or teams that only need local unit tests without external probes.
What do I get? / Deliverables
Your agent can configure and query PingZen monitors so uptime issues surface in the same session where you fix code.
- Monitors defined across supported protocols
- Agent-accessible status and alert context for failing checks
- Operational runbooks tied to live PingZen data
Recommended MCP Servers
Journey fit
After you ship, keeping endpoints healthy is Operate work; agents use this MCP to inspect checks, incidents, and monitor config without opening another dashboard tab. Monitoring is the canonical subphase for uptime, synthetic checks, and protocol-level observability integrations.
How it compares
Operate-phase monitoring MCP with 44 tools, not a Build-phase integration stub or a Launch-phase SEO connector.
Common Questions / FAQ
Who is dev.pingzen/mcp for?
Solo builders and small teams running production web apps and APIs who want MCP-driven uptime monitoring from PingZen.
When should I use dev.pingzen/mcp?
Use it in Operate when you need to add checks, investigate outages, or tune multi-protocol monitoring while coding with an agent.
How do I add dev.pingzen/mcp to my agent?
Use remote https://pingzen.dev/mcp with Authorization bearer pz_* API key or JWT, or run docker.io/ilyakong/pingzen-mcp:0.9.3 stdio with MCP_API_TOKEN set.