PingRobot

io.pingrobotPublished by pingrobot.ioOfficial publisherv1.0.0Updated Oct 26, 2026

Uptime monitoring: see what's down and why, add monitors, schedule maintenance, post status updates.

VerifiedStreamable HTTPWeb executableSecurity & Monitoring

Overview

AI-generated overview

Remote MCP server for PingRobot uptime monitoring: lets an assistant see what is down and why, add monitors, schedule maintenance and post status updates.

What you can do
  • Inspect uptime monitoring state, including which checks are down and the reasons behind failures
  • Create and add new monitors
  • Schedule maintenance windows
  • Post status updates
When to use it
Useful when you want an assistant to help triage outages, check monitor status, or make routine changes to PingRobot monitoring and status communication without switching to the dashboard.
Requirements
A remote streamable HTTP endpoint at pingrobot.io, with no local package to install. Requires a PingRobot API key sent as a bearer token in the Authorization header; keys are created in Settings → API keys.
Before you install
The API key is a credential passed in the Authorization header; a read-only key is recommended for chat assistants. The server can add monitors, schedule maintenance and post status updates, which change monitoring configuration and publish status information.

Installation

In SourceWeft

  1. Open PingRobot in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. 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/io.pingrobot%2Fpingrobot/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": {
    "pingrobot": {
      "type": "http",
      "url": "https://pingrobot.io/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestOct 21, 2026

Score

67% 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 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.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.