# Read and update incidents and on-call (slim)

> Read and update incidents and on-call: 0 companies fully do it, 6 with a limit, 10 carry the tag. Every listing in Observability & incidents with the reason and a source.

- Full: https://www.anchorterminal.com/niches/observability.oncall-and-incident-records/index.md (~1,200 tokens) · this version ~280 tokens · JSON https://www.anchorterminal.com/niches/observability.oncall-and-incident-records/index.json · canonical https://www.anchorterminal.com/niches/observability.oncall-and-incident-records/
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-15
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

No company's docs show a full fit yet. The listings below do the job with a limit, or not at all. Full fit: 0 companies, with a limit: 6, tagged: 10. Weight 12, 6 accounts.

Done when: The incident or schedule read with its body, alerts and timeline; any write (declare, note, override, coverage request) applied once even if retried, and the change visible on a re-read.
caveat: better-stack (Better Stack, Inc.)
caveat: cronitor-mcp (Cronitor)
caveat: grafana-mcp-server (Raintank Inc., d/b/a Grafana Labs)
caveat: incident-io (Pineapple Technology Ltd.)
caveat: pagerduty-mcp (PagerDuty, Inc.)
caveat: rootly-mcp (Rootly Inc.)

Data: https://www.anchorterminal.com/api/v1/use-cases/observability.oncall-and-incident-records.json
