Context7
Up-to-date docs for AI agents
Beschreibung vom Entwickler (englisches Original)
Audit whether ChatGPT, Gemini and Perplexity recommend a site. Readiness checks need no keys.
Diese drei werden nie zu einer Punktzahl zusammengefasst: Meinungen, Messungen und Beliebtheit sind verschiedene Dinge.
Für diesen Server haben wir noch keine Zusammenfassung in einfacher Sprache geschrieben. Unten stehen die Fakten, die wir aus der Registry gelesen haben.
Wähle die KI-App, die du nutzt, und kopiere die Einstellungen.
OPENAI_API_KEY, GOOGLE_API_KEY, PERPLEXITY_API_KEYAls geheim markierte Werte sind Schlüssel zu deinem Konto. Gib sie nie weiter und füge sie nie in einen Chat ein.
Du brauchst
Welche App nutzt du?
Wähle oben deine App. Wir merken sie uns, damit der Button beim nächsten Mal „In … installieren“ anzeigt.
Öffne Claude Desktop → Settings → Developer → Edit Config und füge dies in claude_desktop_config.json ein
{
"mcpServers": {
"crazyseo": {
"command": "npx",
"args": [
"-y",
"crazyseo"
],
"env": {
"OPENAI_API_KEY": "your-value",
"GOOGLE_API_KEY": "your-value",
"PERPLEXITY_API_KEY": "your-value"
}
}
}
}Führe das in deinem Terminal aus
claude mcp add crazyseo --env OPENAI_API_KEY=your-value --env GOOGLE_API_KEY=your-value --env PERPLEXITY_API_KEY=your-value -- npx -y crazyseoTrag die leeren Werte ein, bevor du ihn startest.
In .cursor/mcp.json in deinem Projekt oder in ~/.cursor/mcp.json einfügen
{
"mcpServers": {
"crazyseo": {
"command": "npx",
"args": [
"-y",
"crazyseo"
],
"env": {
"OPENAI_API_KEY": "your-value",
"GOOGLE_API_KEY": "your-value",
"PERPLEXITY_API_KEY": "your-value"
}
}
}
}Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
In .vscode/mcp.json in deinem Projekt einfügen
{
"servers": {
"crazyseo": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"crazyseo"
],
"env": {
"OPENAI_API_KEY": "your-value",
"GOOGLE_API_KEY": "your-value",
"PERPLEXITY_API_KEY": "your-value"
}
}
}
}Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
Dieser Server läuft auf deinem Computer, und ChatGPT kann sich nur mit Servern im Internet verbinden. Wähle eine andere App.
Deine Auswahl bleibt in einem Cookie auf diesem Gerät; kein Konto nötig.
Diese Einstellungen werden aus dem Registry-Eintrag des Entwicklers erzeugt. Wenn in der README etwas anderes steht, folge der README.
Läuft auf deinem Computer; die Tool-Liste erscheint nach der Installation in deiner KI-App.
Wir prüfen Informationen, die jeder sehen kann; den Code haben wir nicht gelesen. Checks, die nicht zutreffen, werden nicht mitgezählt. · Geprüft am 6. Nov. 2026
Der Registry-Name wurde mit dem GitHub-Konto bolidee bestätigt, dem das Repo gehört
Dieses Repo haben wir noch nicht von GitHub gelesen
Dieses Repo haben wir noch nicht von GitHub gelesen
Dieser Server läuft auf deinem Computer; es gibt keinen Endpunkt im Internet
Läuft auf deinem Computer und nutzt stattdessen lokale Einstellungen
Läuft auf deinem Computer; Tool-Listen können wir nur von Endpunkten im Internet lesen
Verglichen mit allen aktiven Servern dieser Kategorie in der Registry. Sterne zählen nur, wenn dem Herausgeber das Repo gehört.
Er hat 1 von 1 zutreffenden Basischecks bestanden. Den Code haben wir nicht gelesen. Bevor du einen Schlüssel oder Token hinzufügst, sieh nach, welche Zugriffe der Server verlangt, und nutze einen Schlüssel, der nur die Berechtigungen hat, die du brauchst.
Das musst du eintragen: OPENAI_API_KEY, GOOGLE_API_KEY, PERPLEXITY_API_KEY
Er läuft auf deinem Computer. Deine KI-App startet ihn bei Bedarf, und die Daten laufen nicht über die Server des Entwicklers (außer der Server ruft selbst einen Onlinedienst auf).
Das GitHub-Repo wurde zuletzt – geändert, und die neueste Version (0.1.2) kam vor 3 Monaten in die Registry.
Apps, die MCP unterstützen, etwa Claude Desktop, Claude Code, Cursor und VS Code. Außerdem brauchst du Node.js auf deinem Computer.
In derselben Kategorie: Context7, Codebase Memory, Exa
Server derselben Kategorie von anderen Entwicklern, sortiert nach Sternen.
So liest du eine Karte:★ GitHub-SterneiDrei Säulen: Bewertungen · Checks · NutzungiAktualisiert = neueste Version in der Registry veröffentlichti
Up-to-date docs for AI agents
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Connect AI agents to Exa for web search, content fetching, and multi-step research.
Unverändert aus dem Repo des Entwicklers übernommen. PopNx MCP hat den Inhalt weder geprüft noch empfiehlt es ihn. HTML, Bilder und Skripte wurden entfernt. Links führen von dieser Website weg.
Find out whether ChatGPT, Gemini and Perplexity recommend your site — and why they don't.
An open-source GEO / AEO auditor and MCP server. No account. No card. Your keys.
Your customers have stopped googling. They ask an assistant *"best CRM for small law firms?"* and buy whatever it names. If it doesn't name you, you don't exist — and no analytics tool will tell you, because there is no click to measure.
This audits it directly: it asks the questions your buyers ask, records the answers word for word, and shows you which sources the models cite instead of you.
Most tools in this space ask the model *"what do you think of Acme?"* — which tells you nothing, because naming the brand in the prompt guarantees it shows up in the answer.
This asks blind. Your brand never appears in the question, so the answer you get back is the answer a real buyer gets. That is the whole difference between a number you can act on and a number that flatters you.
Three more things a prompt wrapper can't do:
The readiness audit runs against any site with zero configuration and zero cost:
npx crazyseo readiness yourbrand.com
Nothing to install, no signup, no key. Or run it from source:
git clone https://github.com/d08m/crazyseo && cd crazyseo
npm install && npm run build node dist/cli.js readiness yourbrand.com
AI-READINESS stripe.com 82/100
✓ Served over HTTPS ✓ AI crawlers allowed ✓ Structured data (schema.org) ✓ llms.txt published (bonus) ✓ Title + meta description ✓ Readable without JavaScript ✓ Canonical URL set ✓ Social preview tags (Open Graph) ✗ Single, clear H1 2 H1 tags — ambiguous which is the main topic ✗ Images have alt text 27 of 31 images missing alt text ✓ Sitemap referenced ✓ No broken internal links
→ 2 issues to fix
*(That's real output — stripe.com, unmodified.)*
11 scored checks, all first-party fetches: HTTPS · AI crawlers (GPTBot, ClaudeBot, PerplexityBot, Google-Extended…) unblocked in robots.txt · schema.org markup · title + meta · readable without JavaScript · canonical · Open Graph · single-H1 structure · image alt-text coverage · sitemap referenced · broken internal links (sampled).
Plus llms.txt, shown but deliberately unscored: Google's own AI-optimization guidance says it has no effect in Google Search, so it can't fairly cost anyone points — but some agents do read it, so it's still worth seeing.
Exits non-zero when checks fail, so you can gate a deploy on it:
- run: npx crazyseo readiness ${{ env.SITE }}
Machine-readable output for pipelines:
npx crazyseo readiness yourbrand.com --json > report.json
To measure what the engines actually say, add whichever keys you have. Any one is enough; more engines means more coverage.
export OPENAI_API_KEY=... # optional
export GOOGLE_API_KEY=... # optional export PERPLEXITY_API_KEY=... # optional
npx crazyseo audit yourbrand.com
It reads your site, infers what you sell, generates the questions your buyers would actually ask, and asks all of them — blind — across every engine you configured.
VISIBILITY lymexa.com 0 of 8 answers · 0%
Lymexa — premium pickleball paddles and recovery gear brand, USA
"What are the best premium pickleball paddles for advanced players?" Gemini ✗ not named JOOLA, CRBN, Selkirk, Six Zero Perplexity ✗ not named JOOLA, Selkirk, CRBN, Gearbox
"Which high-performance pickleball paddle brands are manufactured in the USA?" Gemini ✗ not named Engage, Paddletek, Selkirk, Thompson Pickleball Perplexity ✗ not named Engage, Paddletek, Selkirk, GAMMA
RECOMMENDED INSTEAD Selkirk 4× named Therabody 4× named Hyperice 4× named
CITATION GAP — cited on the questions you lost reddit.com 7× Community discussion AI trusts for real opinions youtube.com 6× Video content AI pulls into answers pickleheads.com 4× Third-party source AI cites instead of you
! ChatGPT did not respond — this score covers the rest only.
*(Real output, trimmed for length. Note the last line: when an engine fails, the report says so instead of quietly averaging the rest and calling it your score.)*
Runs on your own keys — a full audit is typically a few cents.
It ships as an MCP server, so Claude, ChatGPT or any MCP-capable agent can run it directly:
claude mcp add --transport stdio crazyseo -- npx -y crazyseo mcp
It's also packaged as a Claude Code plugin, which wires up the MCP server and the skill below in one step:
/plugin marketplace add d08m/crazyseo
/plugin install crazyseo@crazyseo
Then just ask:
*"Is my site visible in AI search? What's cited instead of me?"*
| tool | what it does | keys |
|---|---|---|
readiness_check | 11-point AI-readiness audit | none |
audit_plan | site facts + buyer questions to ask, for a keyless audit | none |
audit_score | scores what the agent found: visibility, leaderboard, citation gap | none |
audit_visibility | blind multi-engine visibility + verbatim answers | BYO |
citation_gap | sources cited on the questions you lose | BYO |
engine_status | which engines this install can query | none |
You don't need an API key to get the interesting part. audit_plan and audit_score let the assistant you're already talking to be the engine: it fetches your site, writes the buyer questions, answers them with its own web search, and hands the results back for scoring. Ask *"is my site visible in AI search?"* and you get a real citation gap with no signup, no key, no billing.
The tool still does the arithmetic, and still refuses a question that names your brand — that guard is what makes the number worth having. It measures visibility in that assistant, which the report says plainly. For the cross-engine picture, use audit with your own keys.
There's also a SKILL.md so agents know *how to interpret* the numbers — that readiness isn't visibility, that 0% is a normal starting point, and that partial engine coverage must be reported as partial.
import { checkReadiness } from 'crazyseo';
const report = await checkReadiness('example.com'); console.log(report.score, report.checks);
Everything here is free forever, self-hosted, AGPL — full capability, no feature locks, no telemetry, no account, no upsell in the output.
There is no paid tier today, and this README won't pretend otherwise. If one ever appears it will be for the single thing self-hosting genuinely can't give you — scheduled re-runs, stored history and alerts, the infrastructure to watch a number move over months without running anything yourself. The auditing itself stays here, complete, under AGPL.
Which is also the answer to "what stops this going closed later": the licence. Anyone offering it as a hosted service has to open their version too, including whoever wrote it.
Issues and PRs welcome. The checks are deliberately conservative: every one has to be something an assistant or its crawler actually depends on, and verifiable by hand. If a check can't be justified that way, it doesn't belong here.
CONTRIBUTING.md covers the setup, the bar a new check has to clear, and what an engine adapter needs to get right.
AGPL-3.0. Use it, fork it, run it commercially, embed it in your own tooling. If you offer it to others as a hosted service, that service must be open too.
Built because "am I in the answer?" deserves a real measurement, not a vibe.