Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

PageWatch - page-to-data extraction and change monitoring

REMOTE · PAGEWATCH.ZENITH-OPS.WORKERS.DEV

Extract prices, lists, tables, events from static pages and watch them for changes.

+3 this week 60 Trust /100

Last scanned (21 hours ago)

Scores higher than 43% of remote servers

Reachable. Last reached 4 Nov 2026.

Category Web Scraping

Trust breakdown (7 categories)

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 Security46
Transport & Reachability100
Schema Quality & AI Usability51
  • AI-judged instruction clarity (fair).Partial
  • Context-footprint check failed: tool/resource definitions use about 507 tokens (~169/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 Management53
  • Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage86
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 58% 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 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Changelog

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.

  • 3 Nov 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.

  • 1 Nov 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.

  • 30 Oct 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.

  • 27 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 25 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 23 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 21 Oct 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.

  • 20 Oct 26 0
    • Stability: unverified → 0.03 ▲ functional
Diagnostics

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 4 Nov 2026 · Probed https://pagewatch.zenith-ops.workers.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=zenith-ops.workers.dev CN=YE2,O=Let's Encrypt,C=US 18 Oct 2026 16 Jan 2027 ECDSA 256 ECDSA-SHA384 6a179eb6536965b882c4f13df3965472396
SANs: *.zenith-ops.workers.dev, zenith-ops.workers.dev
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
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 pagewatch.zenith-ops.workers.dev. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
dev. present 60074 8 Verified
workers.dev. 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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://pagewatch.zenith-ops.workers.dev/mcp Verified 200
http (plaintext) http://pagewatch.zenith-ops.workers.dev/mcp Inconclusive 405
MCP tools · 3 exposed · ~507 tokens

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 →

Tool Tokens
extract_page ~222

Fetch one public static web page and extract structured data from it (text, attr, list, table, price, events, page, links, json). Free tier: 30 calls per day per client. No JavaScript rendering.

NameTypeReqDescription
allboolean––
attrstring–Attribute name for mode=attr.
fieldsobject–mode=list: {"name": "css" or "css@attr"}.
jsonpathstring–mode=json: JSONPath-lite such as $.a.b[0].
matchstring–mode=links: regular expression filter.
modestring–What to extract. Default text for extract_page, page for watch_page.
paidboolean–true: use the paid endpoint (x402). The result is the payment requirements unless a payment header is sent.
sameHostboolean––
selectorstring–CSS selector (required for text, attr, list).
tableIndexinteger––
urlstringyes–

No output schema declared.

No examples provided.

get_changes ~36

Read the latest state and the change log of a monitor by id.

NameTypeReqDescription
idstringyes–
limitinteger––

No output schema declared.

No examples provided.

watch_page ~249

Create a monitor that checks a public page on a schedule and records changes. Returns monitor id, manage token (shown once), feed and events URLs. Free plan: checks every 60 minutes or slower, 3 active monitors per client, 30 days.

NameTypeReqDescription
allboolean––
attrstring–Attribute name for mode=attr.
fieldsobject–mode=list: {"name": "css" or "css@attr"}.
interval_minutesinteger––
jsonpathstring–mode=json: JSONPath-lite such as $.a.b[0].
matchstring–mode=links: regular expression filter.
modestring–What to extract. Default text for extract_page, page for watch_page.
paidboolean–true: use the paid endpoint (x402). The result is the payment requirements unless a payment header is sent.
sameHostboolean––
selectorstring–CSS selector (required for text, attr, list).
tableIndexinteger––
urlstringyes–
webhook_urlstring–https URL for signed change notifications.

No output schema declared.

No examples provided.

Install

How do I install the PageWatch - page-to-data extraction and change monitoring MCP server?

PageWatch - page-to-data extraction and change monitoring is a hosted endpoint at https://pagewatch.zenith-ops.workers.dev/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 · pagewatch.zenith-ops.workers.dev

# add to Claude Code
claude mcp add --transport http dev-workers-zenith-ops-pagewatch-pagewatch 'https://pagewatch.zenith-ops.workers.dev/mcp'
Common questions

What is the PageWatch - page-to-data extraction and change monitoring MCP server?

PageWatch - page-to-data extraction and change monitoring is an MCP server listed in the public MCP registry as dev.workers.zenith-ops.pagewatch/pagewatch. Extract prices, lists, tables, events from static pages and watch them for changes. This page covers its hosted endpoint (https://pagewatch.zenith-ops.workers.dev/mcp).

Is the PageWatch - page-to-data extraction and change monitoring MCP server safe to use?

PageWatch - page-to-data extraction and change monitoring scores 60 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 PageWatch - page-to-data extraction and change monitoring MCP server expose?

PageWatch - page-to-data extraction and change monitoring exposes 3 tools: extract_page, watch_page, get_changes. Their descriptions and schemas cost roughly 507 tokens of context every time the server is loaded.

Does the PageWatch - page-to-data extraction and change monitoring MCP server require authentication?

No. We connected to PageWatch - page-to-data extraction and change monitoring without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the PageWatch - page-to-data extraction and change monitoring MCP server still maintained?

PageWatch - page-to-data extraction and change monitoring is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.