Agent Health vs Statuspage

In-depth architectural comparison of the Agent Health and Statuspage MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

Which MCP Server Should You Choose?

A

Choose Agent Health when:

• You need dedicated capabilities in the Monitoring domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: Owned-agent uptime monitoring, DNS domain proof, Signed alerts.

Explore Agent Health Details

Choose Statuspage when:

• You need dedicated capabilities in the Monitoring domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: Queries Atlassian Statuspage v2 feeds, Checks up to 20 vendors in one call, Reports components, incidents, and maintenance.

Explore Statuspage Details

Feature & Specification Comparison

Specification	A Agent Health Monitoring	Statuspage Monitoring
Summary	Free owned-agent uptime monitoring, DNS domain proof, signed alerts and opt-in endpoint checks.	Service status / uptime MCP — Atlassian Statuspage v2.
Category & Scope	Monitoring	Monitoring
Quality signal

Tools & Capabilities Breakdown

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

{
  "mcpServers": {
    "agent-health": {
      "command": "npx",
      "args": [
        "-y",
        "agent-health"
      ]
    }
  }
}

{
  "mcpServers": {
    "statuspage": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-statuspage"
      ]
    }
  }
}

Related MCP Server Comparisons