Developer · Remote MCP server
PingZen Uptime Monitoring
Uptime monitoring with 127 tools across 23 protocols. Tag filtering + Code Mode.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
dev.pingzen/mcp- Version
- 0.13.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP, stdio (local process)
- Package
- OCI image (Docker)
- Published
- 2026-03-31
- Updated
- 2026-03-31
- Publisher
- dev.pingzen
- Namespace
- Namespace verified by the MCP Registry via the domain pingzen.dev · how
- Website
- pingzen.dev
- Repository
- gitlab.com/dobryj/recorder2025 (folder projects/pinger/backend/mcp_server)
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://pingzen.dev/mcp | Authorization (secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| OCI image (Docker)runtime: docker | docker.io/ilyakong/pingzen-mcp:0.9.3 | - | stdio |
How to connect PingZen Uptime Monitoring
PingZen Uptime Monitoring is a remote MCP server: there is nothing to install. Its endpoint is https://pingzen.dev/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization (secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
It can also run locally from a container image in an OCI registry such as Docker Hub or GitHub Container Registry: docker.io/ilyakong/pingzen-mcp:0.9.3. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Docker or another OCI container runtime; started with docker run - the usual command is docker run -i --rm -e MCP_API_TOKEN -e DATABASE_URL -e SECRET_KEY docker.io/ilyakong/pingzen-mcp:0.9.3. It reads these environment variables: MCP_API_TOKEN (secret), DATABASE_URL (secret) and SECRET_KEY (secret); set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"mcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"MCP_API_TOKEN",
"-e",
"DATABASE_URL",
"-e",
"SECRET_KEY",
"docker.io/ilyakong/pingzen-mcp:0.9.3"
],
"env": {
"MCP_API_TOKEN": "<secret>",
"DATABASE_URL": "<secret>",
"SECRET_KEY": "<secret>"
}
}
}
}Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| PindocCode-pinned team memory for AI coding agents - typed artifacts, MCP-native, self-host. | Local · HTTP |
| Pine Script v6 DocumentationPine Script v6 documentation lookup, function validation, and linting for AI code generation. | Remote & Local · HTTP, SSE, stdioLive check: ✓ handshake |
| PineconeCreate and manage vector database indexes, backups, and collections. | Local · stdio |
| Pingcheck MCPPingCheck status monitoring for AI agents. Read public pages or your own monitors via pk_ API key. | Local · stdio |
| Pipe Docs (SPR) MCP ServerDocs + source RAG for Pipe language: semantic search, cited answers, code symbol lookup. | Local · stdio |
| PipeheroDebug webhooks from your AI agent: inspect and replay captured webhooks on localhost. | Remote · HTTPLive check: ✓ handshake |
| PipepostMCP server to publish to Substack, Ghost, Dev.to, WordPress, LinkedIn + 5 more from Claude Code. | Local · stdio |
| PiPic Integration GuideRead-only PiPic CLI and HTTP API guidance; no image bytes are transferred. | Remote · HTTPLive check: ✓ handshake |