PingZen Uptime Monitoring

dev.pingzenPublished by pingzen.devOfficial publisherv0.13.0Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableSecurity & Monitoring

Overview

AI-generated overview

PingZen Uptime Monitoring exposes 127 tools across 23 protocols so an assistant can manage uptime checks and monitoring from chat.

What you can do
Manage uptime monitoring checks and targets across many protocols, with tag-based filtering to narrow what is acted on (tool list not published in the manifest).
When to use it
When you already use PingZen for uptime monitoring and want an assistant to work with your checks and monitoring data directly, including through tag-filtered views.
Requirements
A remote endpoint at pingzen.dev, or the Docker image run locally over stdio. Authentication uses an Authorization bearer header with a PingZen API key or JWT, or OAuth 2.0 handled by the MCP client. Local runs also need DATABASE_URL for PostgreSQL and SECRET_KEY for JWT signing; MCP_API_TOKEN can be omitted for test mode.
Before you install
Requires secrets: DATABASE_URL (PostgreSQL connection string), SECRET_KEY (JWT signing secret), MCP_API_TOKEN and the Authorization header. The server can act on monitoring configuration, so changes may affect live checks and alerts. The manifest declares no authentication, so confirm how access is actually enforced before connecting.

Installation

In SourceWeft

  1. Open PingZen Uptime Monitoring in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/dev.pingzen%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "pingzen-uptime-monitoring": {
      "type": "http",
      "url": "https://pingzen.dev/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v0.13.0LatestSep 16, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.