MCP server for the Pagerender API: analyze a URL, verify an integration, read render stats, check service health, list plans
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
PAGERENDER_TOKENAPI keyoptionalA read-only Pagerender API key. Five of the nine tools work without it, and three of those make no network call to Pagerender at all.
Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.
analyze_urlShow 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.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.
No input schema was published for this tool.
analyze_siteSample 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 r…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 r…
No input schema was published for this tool.
check_ai_crawlersRead 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.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.
No input schema was published for this tool.
verify_integrationConfirm 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.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.
No input schema was published for this tool.
render_statsRender 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.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.
No input schema was published for this tool.
service_healthQueue depth, cache and renderer health for the Pagerender service. Works with no token.Queue depth, cache and renderer health for the Pagerender service. Works with no token.
No input schema was published for this tool.
list_plansPlans and prices published by Pagerender. Works with no token.Plans and prices published by Pagerender. Works with no token.
No input schema was published for this tool.
index_statusWhat 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.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.
No input schema was published for this tool.
indexing_overviewThe 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.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.
No input schema was published for this tool.
9 of 9 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
MCP server for the Pagerender API: analyze a URL, verify an integration, read render stats, check service health, list plans
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
The crawl stopped at the 60-package limit. The rest of the tree was never resolved.
36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)
56 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.
+44 more not listed. The counts by reason above cover all of them.
Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.