PingWise

com.pingwisePublished by pingwise.comOfficial publisherv1.0.0Updated Nov 11, 2026

Uptime monitoring: read monitors, incidents and response times; create and change monitors.

VerifiedStreamable HTTPWeb executableSecurity & Monitoring

Overview

AI-generated overview

PingWise is a remote MCP server for uptime monitoring that lets an assistant read monitors, incidents and response times, and create or change monitors.

What you can do
  • Read uptime monitors and their current state
  • Review incidents and response-time data
  • Create new monitors and change existing ones
When to use it
Useful when you want an assistant to check site or service availability and incident history, or to set up and adjust uptime checks without opening the PingWise dashboard.
Requirements
A remote endpoint at app.pingwise.com over streamable HTTP, with OAuth sign-in required. No environment variables or headers are declared.
Before you install
The server can create and change monitors, so assistant actions modify your monitoring configuration. Access is granted through OAuth to your PingWise account; review the scopes requested during sign-in.

Installation

In SourceWeft

  1. Open PingWise in the dashboard and add it to a workspace.
  2. Connect the required 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/com.pingwise%2Fpingwise/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "pingwise": {
      "type": "http",
      "url": "https://app.pingwise.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestNov 11, 2026

Score

83% 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
  • 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.