Instatus Status Page Scraper – JSON API Tool

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

Instatus status page scraper turns any company's Instatus page into clean JSON — components…

The publisher's own server: Instatus

VerifiedStreamable HTTPWeb executableWeb Search & Scraping

Overview

AI-generated overview

A remote MCP server that scrapes a company's Instatus status page and returns its components and status data as clean JSON.

What you can do
Retrieve a company's Instatus status page content as structured JSON, including its components and their status information. The manifest lists no individual tools, so the exact operations are not documented here.
When to use it
Useful when you want an assistant to check or collect the current status of services published on an Instatus status page, for example during incident review or service 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 your MCP client supports it.
Before you install
You must supply an Apify API token as a credential; treat it as a secret. The server reads third-party status pages, so requests go to Apify and to the target site. Usage may be subject to Apify account limits or billing.

Installation

In SourceWeft

  1. Open Instatus Status Page Scraper – JSON API Tool 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%2Finstatus-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": {
    "instatus-status-page-scraper-json-api-to": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=enezli/instatus-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

2
  1. v0.1.1LatestSep 28, 2026
  2. v0.1Sep 16, 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 Instatus integrations

Instatus

com.instatusOfficial publisher

Instatus's hosted MCP server, published by instatus.com; credential required; Streamable HTTP.

Streamable HTTPWeb executableAuth
Communication & CollaborationCredential requiredNov 3, 2026