RealUptime

io.realuptimePublished by realuptime.ioOfficial publisherv0.1.0Updated Oct 24, 2026

RealUptime monitors, incidents, status pages, Errors issues, and free third-party outage checks.

VerifiedStreamable HTTPWeb executableCloud & InfrastructureSecurity & Monitoring

Overview

AI-generated overview

Lets an assistant query RealUptime monitors, incidents, status pages and Errors issues, and run third-party outage checks.

What you can do
RealUptime lets an assistant reach monitors, incidents, status pages and Errors issues through a remote endpoint, plus free third-party outage checks. The tool list is not given, so the exact operations available can only be inferred from that description.
When to use it
Useful for checking monitor status, incidents and status pages in conversation, or for running third-party outage checks. A free-tier key covers read access; creating or changing monitors and incidents requires a paid plan.
Requirements
Needs a connection to the remote endpoint at with OAuth authentication; requests carry an Authorization header holding a Bearer API key obtained from the account page. A free-tier key reaches every read tool; creating or changing monitors and incidents needs a Growth plan.
Before you install
Requires an API key in the Authorization header, which should be kept private. Creating or changing monitors and incidents writes data and needs a paid Growth plan, so it may incur cost.

Installation

In SourceWeft

  1. Open RealUptime 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/io.realuptime%2Fmcp/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": {
    "realuptime": {
      "type": "http",
      "url": "https://mcp.realuptime.io/mcp"
    }
  }
}

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.0LatestSep 25, 2026

Score

56% 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

    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.