Placeholder. No logo or screenshot has been supplied for this listing yet.

Do you maintain this server? Claim this listing to add a logo or screenshot and to correct or extend it. Free, and a person checks every claim.

What it does

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

Description as published by the publisher in the official MCP Registry, read 10 Oct 2026. Not written or verified by Few Servers.

Facts

Registry name	`dev.pingzen/mcp`
Publisher	pingzen.dev Namespace verified by the registry through the publisher's domain.
Category	Monitoring and observability sorted by our keyword rules
Transport	remote (streamable-http), local package (Docker)
Version	0.13.0
This version published	31 Mar 2026
Last seen	10 Oct 2026, in our crawl of the official MCP Registry
Tested by Few Servers	No

Remote endpoint (streamable-http), as published: https://pingzen.dev/mcp
Docker package, as published: docker.io/ilyakong/pingzen-mcp:0.9.3 · transport stdio
```
docker run -i --rm docker.io/ilyakong/pingzen-mcp:0.9.3
```
Standard run command for Docker packages. The registry publishes the package name, not a command; check the repository for required arguments.

Install details read from the registry record on 12 Oct 2026. We have not run this server.

The registry record declares a secret value (a key or token) that is not marked required. Declared by the publisher:

Authorization (header, secret, not marked required): Bearer API key (pz_...) or JWT token — or use OAuth 2.0 (auto-handled by MCP clients)
MCP_API_TOKEN (environment variable, secret, not marked required): API key (pz_...) or JWT token from PingZen (omit for test mode)
DATABASE_URL (environment variable, secret, not marked required): PostgreSQL connection string
SECRET_KEY (environment variable, secret, not marked required): JWT signing secret

Being listed is not a safety check. Read the repository and check what a server asks for before you connect it. How the directory works.

No reviews yet.