Pingzen Uptime Monitoring

Created By
PingZen2 months ago
Monitor websites, APIs and services with 127 AI tools across 23 protocols (HTTP, TCP, DNS, SSL, ICMP, gRPC, SMTP, SOCKS5, MTProxy, and more). Zero-config OAuth — just add the URL, browser opens, log in, done. Tag filtering for Cursor/Cline, BM25 tool search, Code Mode sandbox. 8 alert channels: Telegram, Discord, Email, Slack, MS Teams, Mattermost, Webhook, Web Push.
Overview

PingZen MCP Server — 127 AI Tools for Uptime Monitoring

Quick Start

Add this URL to your AI client — OAuth handles everything automatically:

https://pingzen.dev/mcp/

Supported Clients

ClientAuthConfig
Claude CodeOAuthclaude mcp add-json pingzen '{"type":"http","url":"https://pingzen.dev/mcp/"}'
CursorOAuth{"mcpServers":{"pingzen":{"url":"https://pingzen.dev/mcp/"}}}
VS CodeOAuth{"servers":{"pingzen":{"type":"http","url":"https://pingzen.dev/mcp/"}}}
Claude DesktopOAuth{"mcpServers":{"pingzen":{"type":"streamable-http","url":"https://pingzen.dev/mcp/"}}}
ClineAPI KeyRequires pz_* API key from dashboard

23 Protocols

HTTP, HTTPS, TCP, UDP, ICMP, Ping, gRPC, DNS, WHOIS, SSL, SMTP, IMAP, POP3, FTP, FTPS, DNSBL, WS, WSS, PageSpeed, API Check, Transaction, SOCKS5, MTProxy

Features

  • 127 tools covering monitors, alerts, incidents, status pages, heartbeats, webhooks, reports, maintenance
  • Tag filtering?include_tags=monitors,alerts for Cursor (40-tool limit)
  • BM25 tool searchsearch_tools meta-tool finds the right tool by keywords
  • Code Mode (experimental) — /mcp/code/ endpoint, LLM writes Python in sandbox
  • 8 alert channels — Telegram, Discord, Email, Slack, MS Teams, Mattermost, Webhook, Web Push
  • OAuth 2.0 + RFC 9728 — zero-config, just add URL

Server Config

{
  "mcpServers": {
    "pingzen": {
      "url": "https://pingzen.dev/mcp/"
    }
  }
}
Project Info
Created At
2 months ago
Updated At
2 months ago
Author Name
PingZen
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago