Skip to content

PageCritic

by pagecritic.app · remote · no sign-in to list tools · v1.0.0 · published by app.pagecritic

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

Changes · 1
CompareRegistry entry

3 tools: 1 change things and 2 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

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

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

3 tools

Changes things 1Claude Code: ask
  • 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, …No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Loads 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 (10-15 more ranked issues, 3 headline and 3 CTA rewrites, 5 quick wins, mobile review, full AI-readiness fixes) costs $19 USD one-time, paid by a human at report_url. Set language to "pt" for a report in Brazilian Portuguese. A URL audited through the API in the last 24 hours (in the same language) returns that same result. 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 $49, see https://pagecritic.app/developers), the result includes the full report.

    Annotations the server declares

    • title: Audit a landing page
    • readOnlyHint: true
    • openWorldHint: true
Only reads 2Claude Code: allow
  • 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 chal…No findings

    Why it is in this group

    • The description's first verb is "fetch": a word for reading.
    Description, as the server wrote it
    Fetches 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).

    Annotations the server declares

    • title: Check AI readiness
    • readOnlyHint: true
    • openWorldHint: true
  • get_audit_resultReturns the current result of an audit started with audit_landing_page, by its audit_id.No findings

    Why it is in this group

    • The name "get_audit_result" says "get": a word for reading.
    Description, as the server wrote it
    Returns 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.

    Annotations the server declares

    • title: Get audit result
    • readOnlyHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__pagecritic__check_ai_readiness",
      "mcp__pagecritic__get_audit_result"
    ],
    "ask": [
      "mcp__pagecritic__audit_landing_page"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as pagecritic. Review it before you use it.