GitHub Status Component Snapshot

Git Operations operational is a Statuspage component. That is not a test of your agent.

GitHub Status component names + operational status. Not a probe of your agent. $0.01 / component.

Last run

10 row(s). First row: Git Operations — operational

{
  "title": "Git Operations — operational",
  "entityName": "Git Operations",
  "listingName": "Git Operations — operational",
  "productName": "Git Operations — operational",
  "sourceUrl": "https://www.githubstatus.com",
  "sourceName": "GitHub Status components — not a synthetic probe of your agent"
}

Run it

{
  "searchKeywords": [
    "GitHub Status"
  ],
  "sourceMode": "startUrls",
  "outputMode": "buyer-ready-records",
  "maxItems": 10,
  "startUrls": [
    {
      "url": "https://www.githubstatus.com/api/v2/summary.json"
    }
  ]
}

What lands in the dataset

• GitHub Status summary JSON
• component name + status
• statuspage URL

Use it when

Snapshot component status. Alerting is your scheduler.

On-call people who already watch githubstatus.com.

Price

$0.01 / component — about $0.10 for a 10-row Try.

Schedule it. A one-off click is not Store revenue.

What you should know

• Not a synthetic probe of your agent.
• GitHub’s status, not yours.

FAQ

Is the last-run a fixture? No. If the dataset is empty, the public source failed — we do not invent a row.

Does this ping my MCP server? No. It copies GitHub Status components.