Healthchecks.io + Memtro

Only when you ask, and only what it has been granted: create a check (it alerts nobody unless told to use every integration); change a check's name, slug, tags, schedule, grace period or integrations; pause a check's monitoring (no alerts fire while paused); resume a paused check; delete a check (permanent). Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.

A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.

Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.

API key, and host for a self-hosted instance. In Healthchecks.io, open the project → Settings → API Keys and create an API key. A read-only key reads checks and their history. Use the read-write key to read pings or to create, change, pause, resume or delete checks.