Get started

Instatus for AI agents

Instatus is a status page and incident communication platform for tracking service health and notifying subscribers. On-call and platform teams use it to catch issues before customers report them. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.

Connect InstatusSee the 15 actions ↓
DevOps and monitoringAPI keyMCP + RESTinstatus.com
AUDIT LOG · INSTATUSPOLICY: acme-support
09:41:07 · claude · u_8f2read
instatus.list_incidents
List Incidents✓ allowed · 212ms
09:41:08 · claude · u_8f2read
instatus.get_incident
Get Incident✓ allowed · 164ms
09:41:09 · claude · u_8f2write
instatus.create_incident
Create Incident✓ approved · approved by user
EVERY INSTATUS CALL, ON THE RECORD
01 · USE CASES

What agents do in Instatus.

01

Post an incident update

Add an update to an active incident on the public status page as the issue progresses.

02

Create a new incident

Create an incident and mark the affected component when an outage is confirmed.

03

Resolve an incident with approval

Mark an incident resolved only after the on-call engineer confirms the service is stable.

02 · ACTIONS

15 Instatus actions, graded by risk.

Every Instatus action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.

read

7

Look things up. Allowed by default.

  • instatus.get_incident
    Get Incident
  • instatus.get_component
    Get Component
  • instatus.list_incidents
    List Incidents
  • instatus.get_maintenance
    Get Maintenance
  • instatus.list_components
    List Components
  • instatus.list_maintenances
    List Maintenances
  • instatus.list_status_pages
    List Status Pages

write

8

Create and change things. Allow, or ask the user first.

  • instatus.create_incident
    Create Incident
  • instatus.update_incident
    Update Incident
  • instatus.create_component
    Create Component
  • instatus.update_component
    Update Component
  • instatus.create_maintenance
    Create Maintenance
  • instatus.update_maintenance
    Update Maintenance
  • instatus.add_incident_update
    Add Incident Update
  • instatus.add_maintenance_update
    Add Maintenance Update

destructive

0

Delete, cancel or archive. Ask first, or deny outright.

  • No destructive actions.
03 · HOW IT WORKS

Instatus in three steps.

  1. 01Your users connect InstatusThey add their Instatus api key on Arc0 Connect, under your brand. It goes straight into the vault.
  2. 02You set the rulesReads run, and writes like “create Incident” can wait for the user to approve.
  3. 03Any agent can actYour agent calls Instatus through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
POLICY.TS
await arc0.policies.set('instatus', {
  read: 'allow',
  write: 'ask',        // create_incident
  destructive: 'deny',  
})

# Claude Code: the same connection, one URL
$ claude mcp add --transport http arc0 \
    https://mcp.arc0.ai/u/u_8f2
04 · AUTH AND DATA

How Instatus connects.

Users add their Instatus api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.

The same Instatus connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →

AUTH
API key
CREDENTIALS
Per-tenant encrypted vault
MODEL SEES
Results only, never credentials
AUDIT LOG
Every call, on every plan
05 · WORKS WITH

Use Instatus from any agent.

Claude
ChatGPT
Cursor
Codex
VS Code
OpenAI Agents SDK
Claude Agent SDK
Vercel AI SDK
Mastra
LangGraph
06 · RELATED

More devops and monitoring apps.

PagerDuty368 actionsServiceNow171 actionsNew Relic159 actionsGrafana Cloud118 actionsBetter Stack117 actionsDatadog65 actionsMezmo36 actionsStatuscake30 actions
ALL DEVOPS AND MONITORING APPS →
07 · FAQ

Instatus and Arc0, answered.

Q01

Can I use Instatus with Claude, ChatGPT or Cursor?

Yes. Connect Instatus to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Instatus actions you allow.

Q02

How do users connect Instatus?

Users add their Instatus api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.

Q03

Which Instatus actions can my agent take?

15 in total: 7 read, 8 write and 0 destructive, such as “create Incident”. Your policies decide which of them each agent may call.

Q04

Can I make my agent read-only in Instatus?

Yes. Allow read actions and deny writes in the Instatus policy. Your agent can still look things up, and any write it attempts is blocked and logged.

Q05

Can my own backend call Instatus too?

Yes. The same Instatus connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.

Get started

Plug Instatus into your agent.

Your users connect Instatus once, under your brand. Your agent gets 15 actions behind your policies, with every call on the record.

Connect InstatusBrowse all apps →

Free to build · MCP + REST · Audit log on every plan