Koskamo

PulseWatch MCP

An MCP server provided by PulseWatch that allows agents to check the current outage status and recent incidents for over 1,700 SaaS and cloud vendors. It supports listing tracked vendors, validating vendor names, and accessing pricing information, with paid tools for status checks using x402 USDC payments.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

PulseWatch MCP logo, by PulseWatchVendor evidenceStreamable HTTPNo sign-inEndpoint checked 2026-10-26Operated by PulseWatch
You need:No accounts or API keys.
MCP endpoint (Streamable HTTP)
https://api.pulsewatch.us/mcp
Vendor documentation

What you can do with it

  • Check current outage status for a specific vendor
  • Retrieve recent incidents for a vendor
  • List or search tracked vendors
  • Validate vendor name format

Source and maintenance

Vendor evidenceRegistry 1.1.0
mcp-registry: us.pulsewatch.api/status@1.1.0Project website

Tools

Reported by the attributed source; not independently observed by Koskamo.

No tool definitions available.

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · registry · passed · metadata changed · Source metadata updated
  • · backfill · recorded · Pre-expansion baseline; unobserved rich metadata remains unknown

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http pulsewatch-mcp https://api.pulsewatch.us/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add pulsewatch-mcp --url https://api.pulsewatch.us/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable pulsewatch-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "pulsewatch-mcp": {
      "url": "https://api.pulsewatch.us/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "pulsewatch-mcp": {
      "type": "streamableHttp",
      "url": "https://api.pulsewatch.us/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start pulsewatch-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "pulsewatch-mcp": {
      "type": "http",
      "url": "https://api.pulsewatch.us/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http pulsewatch-mcp https://api.pulsewatch.us/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.
Claude Desktop configuration
{
  "mcpServers": {
    "pulsewatch-mcp": {
      "url": "https://api.pulsewatch.us/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "pulsewatch-mcp": {
      "serverUrl": "https://api.pulsewatch.us/mcp"
    }
  }
}

Let your agent find its tools

Find servers like PulseWatch MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows
See all 298

Do you run PulseWatch MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing