Austin Oaks Page Watch MCP Server

by freshypenguin Your server? Claim it

answering

Austin Oaks Page Watch is answering right now. Last checked 9 min ago. It exposes 3 tools.

Watch a public web page for changes when your agent cannot stay running. Hourly checks, signed diffs

Uptime history 10 days of history

10 days agonow

100.0%

Uptime 24h

92 of 92 checks

Tools

read from the server

289 ms

Response time

average over 24h

open, no key

Access

streamable-http

Nothing serious here today

Today is the operative word: we check Austin Oaks Page Watch every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 9 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add ao-page-watch --transport http https://ao-page-watch-production.up.railway.app/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "ao-page-watch": {
      "url": "https://ao-page-watch-production.up.railway.app/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.ao-page-watch]
url = "https://ao-page-watch-production.up.railway.app/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "ao-page-watch": {
      "url": "https://ao-page-watch-production.up.railway.app/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "ao-page-watch": {
      "url": "https://ao-page-watch-production.up.railway.app/mcp"
    }
  }
}

Available tools 3

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

changes

check_changes

Ask whether a watched page changed since you last checked, using the token from watch_url. Returns the monitor status, checks remaining, changed_since_last_poll, and the latest signed change record with a line diff excerpt. Safe to call from any later run; calling it marks the changes as seen.

unwatch

unwatch_url

Stop a monitor by token. Remaining checks are forfeited.

watch

watch_url

Start watching a public web page for changes when you cannot stay running yourself. Use when a task needs to know whether a page changed since you last looked, and you will not be alive to check: a price, a status page, a job listing, a policy, a schedule, a document. Give it a URL. It takes a first snapshot now, then re-fetches every 3600 seconds, extracts the visible text deterministically, and records a signed change record whenever the text hash changes. You get back a token; call check_changes with it later, from any run, to learn whether the page changed and see the diff. Free: 3 monitors per caller, 168 hourly checks each (about seven days). More checks or more monitors are sold per call over x402 on the HTTP route POST /v1/watch. It will NOT render JavaScript, log in, use proxies, or bypass bot protection. A page that blocks plain fetches is reported BLOCKED and your remaining checks are kept and can be moved to another URL. No language model is involved; no 'meaningful change' guessing.

Endpoints

URL	Transport	State	Latency	Checked
https://ao-page-watch-production.up.railway.app/mcp	streamable-http	answering	298 ms	9 min ago

Alternatives to Austin Oaks Page Watch

same job, measured the same way

Pulse — heartbeat & status monitor for AI agents

by workers-notdown-app-pulse

Your agent pings once per run; get a public up/late/down status page. Auto-creates checks. One call.

4 tools answering

AfterImage

by afterimage

Shared copies of public web pages for AI agents. Search stored pages or fetch a URL.

2 tools answering

Pingcheck MCP

by churman1113

PingCheck status monitoring for AI agents. Read public pages or your own monitors via pk_ API key.

56 installs/wk local only

Optibot

by getoptimal

AI code review for your AI assistant — review local changes, branch diffs, and patch files.

54 installs/wk local only

Clawhub

by maxz712

Git hosting for AI agents: repos, changes, focused diffs, reviews, issues, code search.

17 installs/wk local only

Ecommerce Website Hosting AI Business Intelligence

by promptswing

Publish a site your AI built to paid hosting, then read it back, change a page or restore a version.

answering

Open for Agents Website Visibility

by mdotk

Check how well AI agents can discover and understand a public website.

answering

Orcpin

by npraught

Paid x402 facts for AI agents: signed statements, door reports, endpoint checks, chain reads

223 installs/wk local only

Austin Oaks Page Watch — questions

Answers built from our own checks of this server.

What can Austin Oaks Page Watch do?

It exposes 3 tools, read directly from the server on our last check. Among them: check_changes, unwatch_url, watch_url. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Austin Oaks Page Watch working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 289 ms. The bar chart above shows every period we have measured.

How do I connect Austin Oaks Page Watch?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Austin Oaks Page Watch need an API key?

No. Austin Oaks Page Watch completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Austin Oaks Page Watch?

It answers our handshake in 289 ms on average, which is faster than 52% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.