Pingcheck Mcp

io.github.Churman1113Published by GitHub account Churman1113v0.2.1Updated Oct 24, 2026

PingCheck status monitoring for AI agents. Read public pages or your own monitors via pk_ API key.

VerifiedSTDIODesktop onlySecurity & Monitoring

Overview

AI-generated overview

Lets an assistant read PingCheck status monitoring data, including public status pages and the user's own monitors via a pk_ API key.

What you can do
PingCheck MCP exposes PingCheck status monitoring to an AI assistant. According to the registry description, it can read public status pages and the user's own monitors, with access to private monitors granted through a pk_ API key. No individual tools are listed in the manifest, so the exact tool set is not documented here.
When to use it
Worth adding when you want an assistant to look up uptime or status information from PingCheck while troubleshooting or reporting on service health. It is less useful if you do not use PingCheck or only need general web monitoring data.
Requirements
Runs as a local process over stdio, installed from the npm package pingcheck-mcp, so Node.js and npm are needed. A pk_ API key is required to read your own monitors; public pages need no key. No environment variables or headers are declared in the manifest.
Before you install
The pk_ API key is a credential: treat it as a secret and avoid exposing it in logs or shared configuration. The description only mentions reading public pages and your own monitors, but the manifest lists no tools, so verify what the server can access before installing.

Installation

In SourceWeft

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

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.2.1LatestSep 16, 2026

Score

25% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 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.