Statuspage Incidents

dev.fly.looper-productsPublished by looper-products.fly.devOfficial publisherv0.1.0Updated Oct 29, 2026

Read-only: recent incidents from public Atlassian Statuspage pages. Free, no API key.

VerifiedStreamable HTTPWeb executableCloud & InfrastructureSecurity & Monitoring

Overview

AI-generated overview

Read-only MCP server that fetches recent incidents from any public Atlassian Statuspage status page, with no login or API key.

What you can do
  • Fetch recent incidents from a public Atlassian Statuspage status page by passing its base URL
  • Return each incident's name, status, impact, created_at, resolved_at and shortlink
  • Work against any public Statuspage-hosted page through its free, unauthenticated JSON API
When to use it
Use it when you want an assistant to check whether a service is having an outage or to review recent incident history for a vendor that publishes a public Atlassian Statuspage, such as a cloud or developer platform.
Requirements
A remote endpoint at looper-products.fly.dev over streamable HTTP; no account, API key or environment variables are needed. The target status page must be public and hosted on Atlassian Statuspage, and network access to it is required.
Before you install
Read-only and unauthenticated, so it cannot change anything. The base URL you supply is sent to the remote server, which then requests that page's public API; avoid pointing it at internal or non-public hosts.

Installation

In SourceWeft

  1. Open Statuspage Incidents in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/dev.fly.looper-products%2Fstatuspage-incidents/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "statuspage-incidents": {
      "type": "http",
      "url": "https://looper-products.fly.dev/mcp-statuspage/"
    }
  }
}

Tools

1

get_statuspage_incidents

Read-only: fetch recent incidents from a public Atlassian Statuspage-hosted status page (e.g. https://www.githubstatus.com) via its free, unauthenticated JSON API at <base>/api/v2/incidents.json. Returns each incident's name, status, impact, created_at, resolved_at and shortlink. No login or API key.

Parameterslimitpage_urlrequired

Version history

1
  1. v0.1.0LatestOct 29, 2026

Score

72% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.