Austin Oaks Page Watch
REMOTE · AO-PAGE-WATCH-PRODUCTION.UP.RAILWAY.APP · SCANNED SEP 24
Watch a public web page for changes when your agent cannot stay running. Hourly checks, signed diffs
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (unwatch_url). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 430 tokens (~143/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
- Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage83
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 50% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Austin Oaks Page Watch MCP server?
Austin Oaks Page Watch is a hosted endpoint at https://ao-page-watch-production.up.railway.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · ao-page-watch-production.up.railway.app
claude mcp add --transport http com-freshypenguin-ao-page-watch 'https://ao-page-watch-production.up.railway.app/mcp'
{
"mcpServers": {
"com-freshypenguin-ao-page-watch": {
"url": "https://ao-page-watch-production.up.railway.app/mcp"
}
}
} {
"servers": {
"com-freshypenguin-ao-page-watch": {
"type": "http",
"url": "https://ao-page-watch-production.up.railway.app/mcp"
}
}
} [mcp_servers.com-freshypenguin-ao-page-watch] url = "https://ao-page-watch-production.up.railway.app/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-freshypenguin-ao-page-watch": {
"type": "remote",
"url": "https://ao-page-watch-production.up.railway.app/mcp",
"enabled": true
}
}
} openclaw mcp add com-freshypenguin-ao-page-watch --url 'https://ao-page-watch-production.up.railway.app/mcp' --transport streamable-http
mcp_servers:
com-freshypenguin-ao-page-watch:
url: "https://ao-page-watch-production.up.railway.app/mcp" {
"McpServers": {
"com-freshypenguin-ao-page-watch": {
"Transport": "http",
"Url": "https://ao-page-watch-production.up.railway.app/mcp"
}
}
} assistant mcp add com-freshypenguin-ao-page-watch -t streamable-http -u 'https://ao-page-watch-production.up.railway.app/mcp'
{
"mcpServers": {
"com-freshypenguin-ao-page-watch": {
"type": "http",
"url": "https://ao-page-watch-production.up.railway.app/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 24 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 24 Sept 2026 · Probed https://ao-page-watch-production.up.railway.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.up.railway.app | CN=YE1,O=Let's Encrypt,C=US | 29 Jul 2026 | 27 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 6da79bb561da3efeb0e751ca21abd3999fe |
| SANs: *.up.railway.app, up.railway.app | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of ao-page-watch-production.up.railway.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| railway.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://ao-page-watch-production.up.railway.app/mcp | Verified | 200 | |
| http (plaintext) | http://ao-page-watch-production.up.railway.app/mcp | HTTPS enforced | 301 | https://ao-page-watch-production.up.railway.app/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_changes Check a watched page for changes ~88
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many recent change records to include. |
| token | string | yes | – |
No output schema declared.
No examples provided.
unwatch_url Stop watching a page ~28
Stop a monitor by token. Remaining checks are forfeited.
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | yes | – |
No output schema declared.
No examples provided.
watch_url Watch a web page for changes ~248
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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Public http(s) URL to watch. |
No output schema declared.
No examples provided.
What is the Austin Oaks Page Watch MCP server?
Austin Oaks Page Watch is an MCP server listed in the public MCP registry as com.freshypenguin/ao-page-watch. Watch a public web page for changes when your agent cannot stay running. Hourly checks, signed diffs. This page covers its hosted endpoint (https://ao-page-watch-production.up.railway.app/mcp).
Is the Austin Oaks Page Watch MCP server safe to use?
Austin Oaks Page Watch scores 72 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Austin Oaks Page Watch MCP server expose?
Austin Oaks Page Watch exposes 3 tools: watch_url, check_changes, unwatch_url. Their descriptions and schemas cost roughly 364 tokens of context every time the server is loaded.
Does the Austin Oaks Page Watch MCP server require authentication?
No. We connected to Austin Oaks Page Watch without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Austin Oaks Page Watch MCP server still maintained?
Austin Oaks Page Watch is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.