Pagerender MCP server

Read from the package source without running it. The installed server may list more.

• 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 nee

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

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

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

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

• list_plans

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

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

• service_health

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

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

• Code scan6 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitystatic API keys via environment variables6/15
• Maintenancelast push 10 days ago15/15
• Maintainer identitynamespace and repository owner differ; GitHub account older than a year5/10

Safety score

78/100

higher than 52% of 866 Scraping and browsing servers

Tools

9

the typical Scraping and browsing server has 6

Tools that change things

0%

typical: 0%. Fewer write tools means less an agent can break

Downloads a week

35

more than 17% of 309 Scraping and browsing servers with a package

Pagerender: common questions

Is Pagerender MCP server safe?

Mostly: it is graded B (78/100). Read the Pagerender safety report

How do I install Pagerender?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does Pagerender need an API key?

Yes. The registry entry asks for PAGERENDER_TOKEN.

Is Pagerender maintained?

The last commit was 31 days ago (2026-10-04). The latest release is v1.2.0.

What can I use instead of Pagerender?

Servers from other publishers that do the same job: Public Browser MCP server, OpenBrand MCP server and Video Extract MCP server.

How does Pagerender compare with other Scraping and browsing MCP servers?

safety score 78/100 (higher than 52% of 866 Scraping and browsing servers); tools 9 (the typical Scraping and browsing server has 6); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.