Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add mcp/toolshedlabs-hash/pagewatch-mcp-node/pagewatchgit clone --depth 1 https://github.com/toolshedlabs-hash/pagewatch-mcp-nodeWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/toolshedlabs-hash/pagewatch-mcp-node/pagewatch)<a href="https://agentmods.dev/mcp/toolshedlabs-hash/pagewatch-mcp-node/pagewatch"><img src="https://agentmods.dev/badge/mcp/toolshedlabs-hash/pagewatch-mcp-node/pagewatch.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
pagewatch scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 5d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
This is a copy
100% identical to pagewatch — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{
"pagewatch": {
"command": "npx",
"args": [
"-y",
"pagewatch-mcp"
],
"env": {
"PAGEWATCH_API_KEY": "",
"PAGEWATCH_BASE_URL": "https://pagelens.dev"
}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 5d ago First seen · 13 lines scan A acf68f3b6e94
pagewatch is an MCP server published in the GitHub repository toolshedlabs-hash/pagewatch-mcp-node (0 stars, last pushed 1mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. It is 100% identical to pagewatch, differing in 0 lines, and is treated as a copy.
Other mcp servers, from other repositories
upapi-mcp
All public upAPI operations as MCP tools: web scraping, search, screenshots, PDF, OCR and more. Runs locally from the @upapi/mcp npm package. Needs 1 environment variable to run.
screenshot-pdf
Capture screenshots (PNG/JPEG/WebP) and generate PDFs from any URL. x402 payments. Remote server at screenshot-pdf.api.klymax402.com.
snapforge
Screenshots, PDFs and Markdown from any URL or HTML for AI agents, via the SnapForge API. Runs locally from the snapforge-mcp npm package. Needs 1 environment variable to run.
pagewatch
Read a URL as clean markdown, screenshot a website, url to PDF. Web access for agents, no signup. Runs locally from the pagewatch-mcp npm package. Needs 2 environment variables to run.
customjs-mcp
Host static HTML pages, generate PDFs, screenshots, scrape JS sites, run sandboxed JavaScript. Remote server at mcp.customjs.space.
propzapi
Render-and-verify API: HTML/CSS to image or PDF, screenshot any URL, confirm the text rendered. Remote server at api.propzapi.com.