PageRadar

app.pageradarPublished by pageradar.appOfficial publisherv1.0.0Updated Oct 24, 2026

Monitor web pages for changes: create monitors, list detected changes and read diffs.

VerifiedStreamable HTTPWeb executableWeb Search & Scraping

Overview

AI-generated overview

PageRadar is a remote MCP server that lets an assistant create web page monitors, list detected changes and read diffs.

What you can do
  • Create and manage monitors that watch web pages for changes
  • List detected changes across monitored pages
  • Read diffs showing what changed on a page
  • Work with the PageRadar account tied to the supplied API key
When to use it
Useful when you want an assistant to keep an eye on specific web pages and report what changed, for example tracking announcements, pricing pages or documentation updates.
Requirements
A remote MCP endpoint at pageradar.app over streamable HTTP. Authentication is required: an OAuth-based Authorization header carrying a PageRadar API key, which is created in the PageRadar account settings. No local package or environment variables are needed.
Before you install
The server requires an API key sent in the Authorization header, so treat it as a secret and grant only the access you intend. Creating monitors changes state in your PageRadar account, and monitored page content is fetched and processed by PageRadar's service.

Installation

In SourceWeft

  1. Open PageRadar 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/app.pageradar%2Fpageradar/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": {
    "pageradar": {
      "type": "http",
      "url": "https://pageradar.app/api/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. v1.0.0LatestOct 13, 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.