Stackpulse MCP

An official MCP server provided by Stackpulse that allows AI assistants to query the status of over 9,800 third-party services and manage user-specific dashboards and URL monitors. It supports reading service outages, incident history, and reliability metrics, as well as creating and modifying dashboards and monitors for infrastructure monitoring.

Endpoint and access

No sign-in: your client connects and lists tools immediately, with no account or key.

No sign-inEndpoint checked 2026-10-18Operated by Stackpulse

MCP endpoint (Streamable HTTP)

https://stackpulse.app/mcp

Vendor documentation

What you can do with it

Check if a specific service like GitHub or Vercel is currently experiencing outages
Review incident history and reliability metrics for a user's custom dashboard
Create a new dashboard to monitor specific services like Stripe and Shopify
Pause or resume URL monitors for an API endpoint during deployments

Tools advertised by the last live check:

search_services
get_service
list_outages
list_dashboards
get_stack_status
get_incident_history
get_monitor
get_reliability
create_dashboard
rename_dashboard
add_services
remove_services
add_monitor
check_monitor
pause_monitor
resume_monitor

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 a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http stackpulse-mcp https://stackpulse.app/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 stackpulse-mcp --url https://stackpulse.app/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable stackpulse-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "stackpulse-mcp": {
      "url": "https://stackpulse.app/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.

Cline configuration

{
  "mcpServers": {
    "stackpulse-mcp": {
      "type": "streamableHttp",
      "url": "https://stackpulse.app/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start stackpulse-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "stackpulse-mcp": {
      "type": "http",
      "url": "https://stackpulse.app/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 stackpulse-mcp https://stackpulse.app/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": {
    "stackpulse-mcp": {
      "url": "https://stackpulse.app/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": {
    "stackpulse-mcp": {
      "serverUrl": "https://stackpulse.app/mcp"
    }
  }
}

See all 206

Do you run Stackpulse 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