io.pagerender/pagerender
NPM · @PAGERENDER/MCP
What search and AI crawlers extract from any public URL. Five of nine tools need no token.
Available components
Last scanned (1 hour ago)
Scores higher than 61% of npm servers
Category Web Scraping
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 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 31 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 676 tokens (~75/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 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
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 0
- Stability: 0.97 → pass security
- Security disclosure: unverified → fail ▼ functional
- 2 Nov 26 +1
- Security disclosure: fail → unverified ▼ functional
- 30 Oct 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.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 −4
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 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 5 Nov 2026 · Analysed npm/@pagerender/mcp@1.2.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 →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 30 |
| 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 →
analyze_site Analyze site ~123
Sample up to 7 pages of a site, starting from the given URL and following its links, and report what a crawler extracts from each one: a verdict, word count, crawlable links versus JavaScript-only links, and whether the page is an empty app shell. Also reports which AI crawlers the site blocks in robots.txt. This samples pages, it does not crawl the whole site. Fetches from this machine, so it needs no token and has no rate limit.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The public URL to start from, usually the home page. |
No output schema declared.
No examples provided.
analyze_url Analyze URL ~78
Show what a crawler extracts from a public URL: title, canonical, heading count, word count, crawlable links versus JavaScript-only links, and whether the response is an empty app shell. Fetches the page from this machine, so it needs no token and has no rate limit.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The public URL to analyze. |
No output schema declared.
No examples provided.
check_ai_crawlers Check AI crawlers ~92
Read a domain's robots.txt and report which AI crawlers it blocks sitewide and which it allows, out of the 21 Pagerender tracks. A domain with no reachable robots.txt blocks none of them. Reads robots.txt from this machine, so it needs no token and has no rate limit.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The domain to check, as a hostname, e.g. example.com. |
No output schema declared.
No examples provided.
index_status Index status ~85
What happened to one URL in the indexing agent: its current state, its last Google verdict, and the events that led there. The response includes guidance, a plain sentence describing what the agent does next for this URL. Needs a token; a read-only API key is sufficient and recommended.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The URL to look up. Must be on a connected domain. |
No output schema declared.
No examples provided.
indexing_overview Indexing overview ~89
The indexing agent for one domain: its last runs, its recent submit and skip decisions, the index rate for pages it finished working on, remaining Google Indexing API quota, and any URL patterns it keeps submitting without an outcome. Needs a token; a read-only API key is sufficient and recommended.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The connected domain, as a hostname, e.g. example.com. |
No output schema declared.
No examples provided.
list_plans List plans ~22
Plans and prices published by Pagerender. Works with no token.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
render_stats Render stats ~109
Render volume and cache hit rate for the account, optionally filtered by period and domain. Accepted periods are 1h, 24h, 7d, 30d and 90d; omit for the API default. Needs a token; a read-only API key is sufficient and recommended.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | Restrict stats to one domain. |
| period | string | – | One of 1h, 24h, 7d, 30d, 90d. |
No output schema declared.
No examples provided.
service_health Service health ~26
Queue depth, cache and renderer health for the Pagerender service. Works with no token.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
verify_integration Verify integration ~52
Confirm a URL is served rendered HTML by Pagerender rather than the raw JavaScript shell. Needs a token; a read-only API key is sufficient and recommended.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The URL to verify. |
No output schema declared.
No examples provided.
How do I install the io.pagerender/pagerender MCP server?
io.pagerender/pagerender runs locally as an npm package, launched with npx -y @pagerender/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 · @pagerender/mcp
claude mcp add io-pagerender-pagerender -- npx -y @pagerender/mcp
What is the io.pagerender/pagerender MCP server?
io.pagerender/pagerender is an MCP server listed in the public MCP registry as io.pagerender/pagerender. What search and AI crawlers extract from any public URL. Five of nine tools need no token. This page covers its npm package (@pagerender/mcp).
Is the io.pagerender/pagerender MCP server safe to use?
io.pagerender/pagerender scores 79 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 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 io.pagerender/pagerender MCP server expose?
io.pagerender/pagerender exposes 9 tools: analyze_url, analyze_site, check_ai_crawlers, verify_integration, render_stats, and 4 more. Their descriptions and schemas cost roughly 676 tokens of context every time the server is loaded.
Is the io.pagerender/pagerender MCP server still maintained?
io.pagerender/pagerender is still listed as active in the MCP registry. We last reached this channel on 5 November 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 io.pagerender/pagerender MCP server under?
io.pagerender/pagerender declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.