# io.pagerender/pagerender (npm · @pagerender/mcp)

What search and AI crawlers extract from any public URL. Five of nine tools need no token.

- Trust score: 79/100 (medium)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `@pagerender/mcp`: 79/100 (this document), [markdown](https://verifymcp.io/servers/io-pagerender-pagerender/pagerender-mcp.md), [page](https://verifymcp.io/servers/io-pagerender-pagerender/pagerender-mcp)

## Channel facts

- Registry: `npm`
- Package: `@pagerender/mcp`
- Version: `1.2.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 81/100
  - No malware found by supply-chain analysis.
  - CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available.
  - No install/post-install scripts declared.
  - 30 of 95 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 31 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 78/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 676 tokens (~75/item across 9 items; 9 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add io-pagerender-pagerender -- npx -y @pagerender/mcp
```

### Cursor

```json
{
  "mcpServers": {
    "io-pagerender-pagerender": {
      "command": "npx",
      "args": [
        "-y",
        "@pagerender/mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-pagerender-pagerender": {
      "command": "npx",
      "args": [
        "-y",
        "@pagerender/mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add io-pagerender-pagerender -- npx -y @pagerender/mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-pagerender-pagerender": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pagerender/mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-pagerender-pagerender --command npx --arg -y --arg @pagerender/mcp
```

### Hermes

```yaml
mcp_servers:
  io-pagerender-pagerender:
    command: "npx"
    args: ["-y", "@pagerender/mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "io-pagerender-pagerender": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pagerender/mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-pagerender-pagerender -t stdio -c npx -a -y @pagerender/mcp
```

### Other

```json
{
  "mcpServers": {
    "io-pagerender-pagerender": {
      "command": "npx",
      "args": [
        "-y",
        "@pagerender/mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-03 (score 79, 0)

- [security] Stability: 0.97 → pass
- [functional regression] Security disclosure: unverified → fail

### 2026-11-02 (score 79, +1)

- [functional regression] Security disclosure: fail → unverified

### 2026-10-30 (score 78, +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.

### 2026-10-28 (score 77, +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.

### 2026-10-26 (score 76, +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.

### 2026-10-24 (score 75, −4)

- [security regression] CVE-2023-54404 affects this package: high
- [security regression] Known CVEs: pass → fail

### 2026-10-22 (score 79, +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.

### 2026-10-20 (score 78, +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.

## MCP tools (9)

### `analyze_url` (~78 tokens)

Analyze URL

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.

Input parameters:

- `url` (string, required): The public URL to analyze.

### `analyze_site` (~123 tokens)

Analyze site

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.

Input parameters:

- `url` (string, required): The public URL to start from, usually the home page.

### `check_ai_crawlers` (~92 tokens)

Check AI crawlers

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.

Input parameters:

- `domain` (string, required): The domain to check, as a hostname, e.g. example.com.

### `verify_integration` (~52 tokens)

Verify integration

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.

Input parameters:

- `url` (string, required): The URL to verify.

### `render_stats` (~109 tokens)

Render stats

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.

Input parameters:

- `domain` (string): Restrict stats to one domain.
- `period` (string): One of 1h, 24h, 7d, 30d, 90d.

### `service_health` (~26 tokens)

Service health

Queue depth, cache and renderer health for the Pagerender service. Works with no token.

### `list_plans` (~22 tokens)

List plans

Plans and prices published by Pagerender. Works with no token.

### `index_status` (~85 tokens)

Index status

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.

Input parameters:

- `url` (string, required): The URL to look up. Must be on a connected domain.

### `indexing_overview` (~89 tokens)

Indexing overview

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.

Input parameters:

- `domain` (string, required): The connected domain, as a hostname, e.g. example.com.

## Diagnostics

Captured diagnostic sections: Provenance, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/io-pagerender-pagerender/pagerender-mcp#diagnostics

## Score history

- 2026-11-05: 79
- 2026-11-04: 79
- 2026-11-03: 79
- 2026-11-02: 79
- 2026-11-01: 78
- 2026-10-31: 78
- 2026-10-30: 78
- 2026-10-29: 77
- 2026-10-28: 77
- 2026-10-27: 76
- 2026-10-26: 76
- 2026-10-25: 75
- 2026-10-24: 75
- 2026-10-23: 79
- 2026-10-22: 79
- 2026-10-21: 78
- 2026-10-20: 78
- 2026-10-19: 77
- 2026-10-18: 77
- 2026-10-17: 76
- 2026-10-16: 76
- 2026-10-15: 76
- 2026-10-14: 75
- 2026-10-13: 70
- 2026-10-12: 70
- 2026-10-08: 70
- 2026-10-04: 70

## Common questions

### 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.

### What did VerifyMCP test on the io.pagerender/pagerender MCP server?

VerifyMCP ran 16 checks on io.pagerender/pagerender, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@pagerender/mcp
- Socket report: https://socket.dev/npm/package/@pagerender/mcp
- Repository: https://github.com/nmbrthirteen/pagerender-tools
- Changelog RSS feed: https://verifymcp.io/servers/io-pagerender-pagerender/pagerender-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-pagerender-pagerender/pagerender-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/io-pagerender-pagerender/pagerender-mcp.json
- HTML version of this page: https://verifymcp.io/servers/io-pagerender-pagerender/pagerender-mcp