All product capabilities
Alerting & MCP

It reaches your people — and your agents.

Route incidents to the channels your team already lives in, publish a branded status page, and — because PulseTrace speaks MCP — let AI clients query monitors and act under the policy you set.

Notification destinations are configured per organization and fire from the same incident timeline, so Slack, PagerDuty, email and a generic webhook all tell one consistent story instead of drifting apart. The branded status page updates itself from those incidents at the detail level you choose, and because PulseTrace speaks MCP, an AI client can watch and act on the very same events under scoped, policy-gated access.

  • Slack, email, webhooks & PagerDuty routing per organization.
  • Branded status / trust page that updates itself from the same incidents.
  • MCP tools — AI clients query and act under scoped, policy-gated access.
mcp · connected clients
claude-desktop
scopes: monitors:read · incidents:read
Active
ops-copilot
tool call · list_incidents(status=open)
Policy-gated
runbook-agent
requires approval to acknowledge
Approved