OpenStatus Status Page Scraper & JSON API

com.ranovamPublished by ranovam.comv0.1.1Updated Oct 24, 2026

Get any company's OpenStatus status page as clean JSON — monitors, components and live status.

The publisher's own server: openstatus

VerifiedStreamable HTTPWeb executableWeb Search & Scraping

Overview

AI-generated overview

A remote MCP server that fetches a company's OpenStatus status page and returns its monitors, components and live status as clean JSON.

What you can do
Retrieve a company's OpenStatus status page as structured JSON, covering monitors, components and current status. Results are returned in a clean, machine-readable form suitable for further analysis or reporting.
When to use it
Useful when you want an assistant to check or summarize the operational status of a company that publishes an OpenStatus status page, for example during incident research or vendor monitoring.
Requirements
A remote endpoint at mcp.apify.com over streamable HTTP. Authentication is required: an Apify API token sent as a Bearer token in the Authorization header, or OAuth if the MCP client supports it.
Before you install
An Apify API token is required and must be supplied via the Authorization header; treat it as a secret. Requests go to a third-party hosted endpoint, so the status pages you query are visible to that provider.

Installation

In SourceWeft

  1. Open OpenStatus Status Page Scraper & JSON API in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. 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/com.ranovam%2Fopenstatus-scraper/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "openstatus-status-page-scraper-json-api": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=enezli/openstatus-scraper"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.1.1LatestSep 28, 2026

Score

67% 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 listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • 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.

Other Openstatus integrations