BetterStack Status Page Scraper & API Tool

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

Get any company's BetterStack (Better Uptime) status page as clean JSON — components, incidents…

The publisher's own server: Scraper API

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingSecurity & Monitoring

Overview

AI-generated overview

A remote MCP server that fetches a company's BetterStack (Better Uptime) status page as clean JSON, including components and incidents.

What you can do
Retrieve a company's BetterStack status page as structured JSON, covering components and incidents. The manifest lists no individual tools, so the exact operations are not documented; the description points to status-page retrieval as the main capability.
When to use it
Useful when an assistant needs to check or report on a service's current status, component health, or incident history from its BetterStack status page.
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, unless the MCP client supports OAuth, in which case the token is optional.
Before you install
You must supply an Apify API token as a secret in the Authorization header; treat it as a credential and avoid exposing it. The server is hosted by a third party, so the status-page queries you make pass through that provider.

Installation

In SourceWeft

  1. Open BetterStack Status Page Scraper & 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%2Fbetterstack-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": {
    "betterstack-status-page-scraper-api-tool": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=enezli/betterstack-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 Scraper-Api integrations