Skip to main content

PageCritic

app.pagecritic/pagecriticVersion 1.0.0

Audit a landing page's conversion (score, top issues, fixes) and check if AI crawlers can read it.

Status

Responds432 msAnswered our handshake without sign-in.

Registry data may be out of date

We could not refresh it, so this page shows the last copy.
Last checked
Nov 14, 2026, 13:38 UTC
Latency
432 ms
Remotes responding
1 of 1
Sign-in
No sign-in
Hosting
Hosted outside the EU (detected)
Registry data as of
Nov 14, 2026, 22:14 UTC

Data from the official MCP Registry, checked by run.zero. How we check

Connect

Streamable HTTP
https://pagecritic.app/mcpResponds432 ms
No sign-in

Claude Code

claude mcp add --transport http pagecritic https://pagecritic.app/mcp

Claude Desktop and claude.ai

Settings > Connectors > Add custom connector
Name: pagecritic
Remote MCP server URL: https://pagecritic.app/mcp

Cursor

{
  "mcpServers": {
    "pagecritic": {
      "url": "https://pagecritic.app/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"pagecritic","type":"http","url":"https://pagecritic.app/mcp"}'

Built your own server? run.zero hosts MCP servers on European infrastructure.

Host your own MCP server on run.zero

Tools

4 tools

Tools of PageCritic
Read-only
Idempotent
Open world
audit_landing_pageLoads a public landing page in a real browser (desktop and mobile), and returns a conversion score from 0 to 100, seven sub-scores (clarity, value proposition, CTA, trust, design, mobile, SEO basics), the top 3 issues with concrete fixes, what already works, a short AI-readiness score, and fix_prompt: a Markdown prompt that hands the fixes to a coding agent such as Claude Code or Cursor. Use it when someone wants feedback on why a homepage, landing page or pricing page does not convert, wants a second opinion before a launch, or wants to compare their page with a competitor's. Do not use it for pages behind a login, for non-HTML files, or for general SEO keyword research. It takes 30 to 90 seconds; if it returns status "running", call get_audit_result with the audit_id. The free result is complete on its own. The full report (every other issue ranked by the points it costs, the 36-check list, 3 headline and 3 CTA rewrites, 5 quick wins, mobile review, full AI-readiness fixes) costs $5 USD one-time, paid by a human at report_url. Set language to "pt" for a report in Brazilian Portuguese. Without usable credits, results for the same URL and language are normally reused for 24 hours; selected well-known sites can reuse reports for up to 7 days. Paid-credit audits run fresh within the daily spend cap; idempotent REST retries return their original audit without another charge. The free web report shows issue titles and a prompt preview; this agent result includes the top-3 fixes and prompt. The 3 included web rechecks are not API credits. Limit: 5 new audits per hour per client, 20 with an API key. With an API key that has credits (Authorization: Bearer header; 10 full reports for $29, see https://pagecritic.app/developers), the result includes the full report.Not declaredYesNot declaredYes
check_ai_readinessFetches a public page as a normal browser and as GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, Claude-User and PerplexityBot, then reports which AI bots are blocked or get a challenge page, the robots.txt rule for each AI bot, how much text is visible without JavaScript, JSON-LD types, sitemap, Markdown versions and llms.txt, with a 0-100 score and prioritized fixes. Use it when someone asks whether ChatGPT, Claude or Perplexity can see or cite their site, or why their site does not show up in AI answers. Do not use it to judge design or copy (use audit_landing_page). It uses plain HTTP fetches, takes about 5-15 seconds, and is free (15 checks per hour per client).Not declaredYesNot declaredYes
get_audit_resultReturns the current result of an audit started with audit_landing_page, by its audit_id. Use it only when audit_landing_page returned status "running"; wait about 20 seconds between calls. Returns the same fields as audit_landing_page.Not declaredYesNot declaredNo
recheck_landing_pageRuns a fresh capture of the page behind an earlier full report bought with the same API key, then returns the new result plus `comparison`: every check marked cleared, improved_still_failing, unchanged, regressed, newly_failing or unable_to_verify against that baseline. Use it after the fixes from fix_prompt are published. It needs an API key (Authorization header) and an idempotency_key you reuse on retries. Call it first without confirm to see the quote (the baseline's included re-checks are used first, at 0 credits; after those, 1 credit); nothing runs or is charged until you call again with confirm: true. A failed capture gives the re-check or credit back. Reading results with get_audit_result is always free.NoNoYesYes

Details

Registry status
Active
Published
Oct 18, 2026
Updated
Oct 18, 2026
Repository
Not given
Categories (suggested)
Search and webSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
GDPR
Not declared

Are you the operator? Claim this listing