Pagewatch
NPM · PAGEWATCH-MCP · 3 COMPONENTS · SCANNED SEP 20
Read a URL as clean markdown, screenshot a website, url to PDF. Web access for agents, no signup.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 57 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability59
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 881 tokens (~176/item across 5 items; 5 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 Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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 Pagewatch MCP server?
Pagewatch runs locally as an npm package, launched with npx -y pagewatch-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · pagewatch-mcp
claude mcp add dev-pagelens-pagewatch -- npx -y pagewatch-mcp
{
"mcpServers": {
"dev-pagelens-pagewatch": {
"command": "npx",
"args": [
"-y",
"pagewatch-mcp"
]
}
}
} {
"servers": {
"dev-pagelens-pagewatch": {
"command": "npx",
"args": [
"-y",
"pagewatch-mcp"
]
}
}
} codex mcp add dev-pagelens-pagewatch -- npx -y pagewatch-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-pagelens-pagewatch": {
"type": "local",
"command": [
"npx",
"-y",
"pagewatch-mcp"
],
"enabled": true
}
}
} openclaw mcp add dev-pagelens-pagewatch --command npx --arg -y --arg pagewatch-mcp
mcp_servers:
dev-pagelens-pagewatch:
command: "npx"
args: ["-y", "pagewatch-mcp"] {
"McpServers": {
"dev-pagelens-pagewatch": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"pagewatch-mcp"
]
}
}
} assistant mcp add dev-pagelens-pagewatch -t stdio -c npx -a -y pagewatch-mcp
{
"mcpServers": {
"dev-pagelens-pagewatch": {
"command": "npx",
"args": [
"-y",
"pagewatch-mcp"
]
}
}
} 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.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −2
- Stability: pass → 0.80 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 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 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 −2
- Stability: pass → 0.80 functional
- 8 Sept 26 0
- Stability: 0.97 → pass security
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
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 20 Sept 2026 · Analysed npm/pagewatch-mcp@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
balance ~76
Check the remaining free credits on your pagewatch key, plus the per-call prices and, if the key is not switched on yet, the free activation link to give your human. Pass api_key if you did not set PAGEWATCH_API_KEY. api_key: an existing pagewatch bearer token, optional.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | – | – | – |
No output schema declared.
No examples provided.
pdf ~158
Render a web page (by url) or raw html into a pdf and return it as base64 pdf data. Provide exactly one of url or html. Respects robots.txt for url input. Pass api_key if you have a pagewatch key, otherwise a free trial key is created for you and returned. url: the page to convert, optional. html: raw html to convert, optional (provide url or html, not both). api_key: an existing pagewatch bearer token, optional. paper: A4, Letter, Legal or A3. landscape: landscape orientation.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | – | – | – |
| html | – | – | – |
| landscape | boolean | – | – |
| paper | string | – | – |
| url | – | – | – |
No output schema declared.
No examples provided.
read_page ~171
Load a web page in a real browser and return its main content as clean markdown, with the title, canonical url and basic metadata. Handles javascript-rendered pages. Respects robots.txt and refuses sites that block automation rather than trying to defeat them. Pass api_key if you already have a pagewatch key, otherwise a free trial key is created for you on the first call and returned in the response. url: the page to read (http or https). api_key: an existing pagewatch bearer token, optional. wait_for_selector: css selector to wait for before reading, optional. scroll: scroll the page to trigger lazy-loaded content, optional.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | – | – | – |
| scroll | boolean | – | – |
| url | string | yes | – |
| wait_for_selector | – | – | – |
No output schema declared.
No examples provided.
register ~157
Create a pagewatch api key for yourself. Free, no signup and no human form. Returns a bearer token that starts with a small free trial so your first read_page, screenshot or pdf works right away. When the trial runs out, hand the returned verification_uri_complete to your human, who confirms one email to unlock 200 more free credits (still free, nothing to pay). Reuse the token by passing it as api_key, or set PAGEWATCH_API_KEY. Nothing is ever charged: pagewatch has no payment processor connected. label: a short name for this key, optional. purpose: why you want web access, shown to your human on the activation page.
| Name | Type | Req | Description |
|---|---|---|---|
| label | – | – | – |
| purpose | – | – | – |
No output schema declared.
No examples provided.
screenshot ~198
Take a screenshot of a web page rendered in a real browser and return it as base64 image data (png by default, jpeg optional), with the final url and pixel size. Consent overlays are hidden so the shot shows the page. Respects robots.txt. Pass api_key if you have a pagewatch key, otherwise a free trial key is created for you and returned. url: the page to capture. api_key: an existing pagewatch bearer token, optional. full_page: capture the entire scrollable page, not just the viewport. width, height: viewport size in pixels. format: png or jpeg. wait_for_selector: css selector to wait for before capturing, optional.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | – | – | – |
| format | string | – | – |
| full_page | boolean | – | – |
| height | integer | – | – |
| url | string | yes | – |
| wait_for_selector | – | – | – |
| width | integer | – | – |
No output schema declared.
No examples provided.
What is the Pagewatch MCP server?
Pagewatch is an MCP server listed in the public MCP registry as dev.pagelens/pagewatch. Read a URL as clean markdown, screenshot a website, url to PDF. Web access for agents, no signup. This page covers its npm package (pagewatch-mcp).
Is the Pagewatch MCP server safe to use?
Pagewatch scores 77 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. 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 MCP server expose?
Pagewatch exposes 5 tools: read_page, screenshot, pdf, register, balance. Their descriptions and schemas cost roughly 760 tokens of context every time the server is loaded.
Is the Pagewatch MCP server still maintained?
Pagewatch is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Pagewatch MCP server under?
Pagewatch declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.