OnlineOrNot

com.onlineornotPublished by onlineornot.comOfficial publisherv0.1.1Updated Nov 8, 2026

Monitor websites, APIs, browser flows, and scheduled jobs; manage status pages with OnlineOrNot.

VerifiedStreamable HTTPWeb executableSecurity & Monitoring

Overview

AI-generated overview

Remote OnlineOrNot MCP server that lets an assistant monitor websites, APIs, browser flows and scheduled jobs and manage status pages.

What you can do
  • Monitor websites, APIs, browser flows and scheduled jobs through OnlineOrNot
  • Manage status pages for reporting service health
  • No tool list is published, so the exact set of actions is not documented here
When to use it
Useful when you want an assistant to check or adjust uptime monitoring and status pages for sites and services you already track in OnlineOrNot, without switching to the web dashboard.
Requirements
A remote MCP endpoint at mcp.onlineornot.com over streamable HTTP, with OAuth sign-in required. An OnlineOrNot account with the relevant monitors and status pages is implied.
Before you install
Access is granted through OAuth to your OnlineOrNot account, so the assistant may be able to change monitoring configuration or status pages, not just read them. Review the permissions granted at sign-in.

Installation

In SourceWeft

  1. Open OnlineOrNot 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.onlineornot%2Fonlineornot/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": {
    "onlineornot": {
      "type": "http",
      "url": "https://mcp.onlineornot.com/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.1LatestNov 8, 2026

Score

83% 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
  • 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.