Log inSubmit server
CrazySEO logo

CrazySEO

Audit AI-search visibility, site readiness, buyer questions, and citation gaps across ChatGPT, Gemini, and Perplexity.

InstallRepository
Full README Compare alternatives Embed widget Claim this listing

Install CrazySEO

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "crazyseo-2": {
      "command": "npx",
      "args": [
        "-y",
        "crazyseo"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y crazyseo

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 7d ago.

Overview

CrazySEO MCP server audits whether ChatGPT, Gemini, and Perplexity recommend a site, while identifying cited alternatives. It provides keyless readiness checks and agent-assisted audit planning and scoring, plus cross-engine visibility audits when API keys are configured. Use it to inspect technical AI-readiness, measure blind brand visibility, or find sources cited instead of your site.

Use cases

  • Run a keyless readiness audit before deploying a site
  • Measure whether AI engines mention a brand in buyer questions
  • Compare competitors recommended instead of a target site
  • Find third-party sources cited when a site loses visibility

Key features

  • 11-point AI-readiness audit
  • Blind multi-engine visibility testing
  • Verbatim prompts and model answers
  • Citation-gap reporting
  • Keyless audit planning and scoring
  • JSON output for deployment pipelines

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

4/4 checks healthy over the last 35d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 16d ago via OSV.dev · crazyseo (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars4Stargazers on the source repository.
npm downloads439Package downloads in the last 30 days.
Last commit2mo agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Directory activity2 viewsConfig copies, upvotes, and views on AllMCPs.

How CrazySEO works

What CrazySEO MCP server does

CrazySEO MCP server evaluates how likely a website is to appear in AI-generated recommendations. It separates technical readiness from model visibility: readiness checks inspect the site directly, while visibility audits ask buyer-style questions without naming the target brand.

The project can report whether configured engines mention the site, which competing brands appear instead, and which third-party sources are cited on questions the site loses. Results retain the question and raw model response so findings can be checked manually.

How it works

A readiness audit fetches the target site and runs 11 checks covering HTTPS, crawler access in robots.txt, schema.org markup, title and meta description, JavaScript-independent readability, canonical URLs, Open Graph tags, H1 structure, image alt text, sitemap references, and sampled internal links. llms.txt is displayed as additional information but is not scored.

For visibility testing, the software reads the site, derives what it offers, creates questions likely to be asked by buyers, and sends those questions to configured engines. The target brand is excluded from the questions to avoid forcing a mention. If an engine fails or is rate-limited, the report identifies the missing coverage rather than treating the remaining results as complete.

Setup and configuration

The readiness command needs no account, API key, or configuration:

Terminal
npx crazyseo readiness example.com

Source installation is also supported through Git, npm, and the project build command. JSON output is available for automation, and readiness exits with a non-zero status when checks fail, allowing it to gate a deployment.

Cross-engine visibility requires whichever provider keys are available: OPENAI_API_KEY, GOOGLE_API_KEY, and PERPLEXITY_API_KEY. Any one key can be used, with additional keys increasing engine coverage. The MCP server can be registered over stdio with the crazyseo mcp command. A Claude Code plugin is also provided.

Tools and capabilities

The CrazySEO MCP server exposes these tools:

  • readiness_check: Runs the 11-point site audit without keys.
  • audit_plan: Produces site facts and unbranded buyer questions.
  • audit_score: Scores supplied findings for visibility, rankings, and citation gaps.
  • audit_visibility: Runs blind visibility checks across configured engines and preserves answers.
  • citation_gap: Finds sources cited on questions the site does not win.
  • engine_status: Reports which engines the installation can query.

The package can also be used as a library through its checkReadiness function, which returns a score and individual checks.

Limitations and notes

Keyless planning and scoring can use the agent's own site access and web-search capabilities, but cross-engine comparisons require provider keys. Readiness is not the same as visibility, and a score based on only some engines must be interpreted as partial coverage. The audit declines to score an unreachable site rather than estimating a result. The project is self-hosted, provides no telemetry or account system, and is licensed under AGPL-3.0.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about CrazySEO

CrazySEO is an MCP server that connects an agent to website readiness checks and AI-search visibility audits for ChatGPT, Gemini, and Perplexity. Its main tools cover readiness, audit planning, scoring, blind visibility checks, citation gaps, and engine status. Readiness and planning work without provider API keys.

Install it by registering the stdio command `claude mcp add --transport stdio crazyseo -- npx -y crazyseo mcp`. You can also clone the repository, install dependencies, build it, or install the provided Claude Code plugin.

No, readiness checks, audit planning, and audit scoring do not require API keys. Cross-engine visibility checks use optional `OPENAI_API_KEY`, `GOOGLE_API_KEY`, and `PERPLEXITY_API_KEY` variables for the providers you want to query.

It generates buyer-oriented questions without naming the audited brand, sends them to configured engines, and records whether the brand is recommended. Reports also show competitors, cited sources, raw answers, and any engine that failed to respond.

Yes, readiness can run in CI and exits with a failure status when checks do not pass. Use the `--json` option to write machine-readable results such as `npx crazyseo readiness example.com --json > report.json`.

Related MCP servers

All in Marketing All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewCrazySEO AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/crazyseo-2?style=directory)](https://allmcps.com/mcp/crazyseo-2)
HTML Embed
<a href="https://allmcps.com/mcp/crazyseo-2"><img src="https://allmcps.com/api/badge/crazyseo-2?style=directory" alt="CrazySEO on AllMCPs" /></a>