What is the key difference between PeppolStatus and Pagerduty MCP?

PeppolStatus belongs to the Monitoring category with cloud HTTP/SSE execution, while Pagerduty MCP belongs to the Monitoring category with local stdio execution.

How do I install PeppolStatus or Pagerduty MCP in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are PeppolStatus and Pagerduty MCP free or paid?

PeppolStatus operates under a Free / Open Source model (No auth required). Pagerduty MCP operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

PeppolStatus lists 51 tools with 0 views and 0 GitHub stars. Pagerduty MCP lists 80 tools with 2 views and 79 GitHub stars.

Can I use both PeppolStatus and Pagerduty MCP together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

PeppolStatus vs Pagerduty MCP

In-depth architectural comparison of the PeppolStatus and Pagerduty MCP 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.

At a Glance & Executive Verdict

PeppolStatus

Monitoring · Remote HTTP/SSE

Quality: 55/100 (Good) | Auth: No auth required

Pagerduty MCP

Monitoring · Local stdio

Quality: 41/100 (Fair) | Auth: No auth required

Verdict Summary: Choose PeppolStatus if you need specialized Monitoring tools running via a hosted cloud SSE transport. Choose Pagerduty MCP if your workspace requires Monitoring integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose PeppolStatus when:

You need dedicated capabilities in the Monitoring domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: list_hosts, get_host, list_host_incidents.

Explore PeppolStatus Details

Choose Pagerduty MCP 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: create_alert_grouping_setting, delete_alert_grouping_setting, get_alert_grouping_setting.

Explore Pagerduty MCP Details

Feature & Specification Comparison

Specification	P PeppolStatus Monitoring	Pagerduty MCP Monitoring
Summary	Peppol market intelligence and network monitoring: migrations, provider churn, leads, and uptime.	PagerDuty's official MCP server which provides tools to interact with your PagerDuty account.
Category & Scope	Monitoring	Monitoring
Quality signal

Tools & Capabilities Breakdown

PeppolStatus Tools (51)

list_hosts

List monitored hosts Every monitored host with its current verdict, latest hourly all-locations latency and 24h uptime, worst-first, plus a network-wide rollup.

get_host

Get a host's current state Current role, verdict, network attribution (IPs/PTR), TLS certificate and operating provider for a host. `?at=` returns point-in-time state.

list_host_incidents

List a host's incidents Incidents for one host, newest-first, cursor-paginated.

get_host_uptime

Get a host's uptime aggregates The aggregate ladder for a host at a chosen resolution, per-location plus the `__all__` rollup, optionally windowed by `[from, to)`, cursor-paginated.

list_host_software

List all hosts' software (Market) Every host with open software fingerprint rows, one row per (hostname, role) with the vendor / version / hosting axes folded in (value, tier, first-seen; plus vendor `variant` and version `kind`). The evidence blob is omitted to keep the list lean — it stays on the per-host resource. Cursor-paginated on the stable (hostname, role) order; optional `vendor=` filter. Market tier.

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).

PeppolStatus Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "peppolstatus": {
      "url": "https://peppolstatus.com/mcp"
    }
  }
}

Pagerduty MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "pagerduty-mcp": {
      "command": "uvx",
      "args": [
        "pagerduty-mcp"
      ]
    }
  }
}

Frequently Asked Questions

PeppolStatus is categorized under Monitoring and uses a remote streaming HTTP/SSE transport. In contrast, Pagerduty MCP belongs to Monitoring using local stdio subprocess. Select PeppolStatus when you need capabilities focused on monitoring and Pagerduty MCP when you require tools for monitoring.

More alternatives to PeppolStatus More alternatives to Pagerduty MCP Monitoring category hub Canonical compare URL