Context7
de upstash
Up-to-date docs for AI agents
Computadora o nube★ 64.224MITActualizado hoy
Instalar
Website Auditor
Resumen
Descripción del creador (original en inglés)
AI visibility in ChatGPT, Gemini, Claude, Perplexity, Copilot & AI Overviews, plus site audits.
Los tres pilares de PopNx MCP
Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.
- Opinión de usuariosiAún no hay reseñasLas reseñas se abrirán junto con las cuentas en una etapa posterior
- Nuestras revisiones básicasi1 de 1 superadasRevisado con información pública; el código aún no se ha escaneado
- UsoiAún sin medir★ –
Qué puedes hacer con él
Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.
- Conexión: Se ejecuta en tu computadora
- Transporte: stdio
- Categoría: Búsqueda y memoria de IA
- Debes completar: WA_API_KEY
Instalación
Elige la app de IA que usas y copia la configuración.
Antes de instalar
- Revisiones básicas: 1 de 1 superadas
- Se ejecuta en tu computadora con los permisos de tu usuario (archivos, red, apps).
- Debes completar tú:
WA_API_KEY,WA_API_BASE_URL
Los valores marcados como secretos son llaves de tu cuenta. Nunca los compartas ni los pegues en un chat.
Necesitas
- npmNode.js instalado (para el comando npx)
¿Qué app usas?
Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.
Abre Claude Desktop → Settings → Developer → Edit Config y pega esto en claude_desktop_config.json
{
"mcpServers": {
"website-auditor": {
"command": "npx",
"args": [
"-y",
"website-auditor-mcp"
],
"env": {
"WA_API_KEY": "your-value",
"WA_API_BASE_URL": "your-value"
}
}
}
}Ejecuta esto en tu terminal
claude mcp add website-auditor --env WA_API_KEY=your-value --env WA_API_BASE_URL=your-value -- npx -y website-auditor-mcpCompleta los valores vacíos antes de ejecutarlo.
O copia la configuración tú
Pégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json
{
"mcpServers": {
"website-auditor": {
"command": "npx",
"args": [
"-y",
"website-auditor-mcp"
],
"env": {
"WA_API_KEY": "your-value",
"WA_API_BASE_URL": "your-value"
}
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
O copia la configuración tú
Pégalo en .vscode/mcp.json de tu proyecto
{
"servers": {
"website-auditor": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"website-auditor-mcp"
],
"env": {
"WA_API_KEY": "your-value",
"WA_API_BASE_URL": "your-value"
}
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Este se ejecuta en tu computadora, y ChatGPT solo puede conectarse a servidores en internet. Elige otra app.
Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.
Valores que debes completar
- Optional: get_sample_audit works with no key and returns a full report in the real output format. Every other tool requires a key, and minting one requires an active Website Auditor subscription ($49…
WA_API_BASE_URLenvBase URL of the Website Auditor API this server wraps. Defaults to the public production host.
Esta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.
Qué puede hacer
Se ejecuta en tu computadora; la lista de herramientas aparece en tu app de IA después de instalarlo.
Revisiones básicasi
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 6 nov 2026
- ✓ Superada
El creador coincide con el repo
El nombre en el registro se verificó con la cuenta de GitHub SpikeyCoder, dueña del repo
- … Aún sin revisar
Sigue en mantenimiento
Todavía no hemos leído este repo en GitHub
- … Aún sin revisar
Tiene licencia
Todavía no hemos leído este repo en GitHub
- – No aplica
El endpoint responde
Este se ejecuta en tu computadora; no hay endpoint en internet
- – No aplica
Inicio de sesión con OAuth
Se ejecuta en tu computadora y usa ajustes locales en su lugar
- … Aún sin revisar
Sin instrucciones ocultas en las descripciones de herramientas
Se ejecuta en tu computadora; solo podemos leer listas de herramientas de endpoints en internet
Comparado con otros en Búsqueda y memoria de IAi
- Más estrellas que el 0% de los otros 7246 servidores de esta categoría
- Publicado en el registro más recientemente que el 95% de los otros 7246 servidores de esta categoría
- Revisiones básicas iguales o mejores que el 100% de los otros 7246 servidores de esta categoría
Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.
Preguntas frecuentes
¿Es seguro Website Auditor?
Superó 1 de 1 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.
¿Qué claves o códigos necesita?
Debes completar: WA_API_KEY
¿Se ejecuta en mi computadora o en la nube?
Se ejecuta en tu computadora. Tu app de IA lo inicia cuando hace falta, y los datos no pasan por los servidores del creador (a menos que el propio servidor llame a un servicio en línea).
¿Sigue en mantenimiento?
El repo de GitHub cambió por última vez –, y la última versión (1.0.29) llegó al registro anteayer.
¿Qué apps pueden usarlo?
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. También necesitas Node.js en tu computadora.
¿Qué puedo usar en su lugar?
En la misma categoría: Context7, Codebase Memory, Exa
Alternativas
Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.
Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi
Codebase Memory
de DeusData
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Se ejecuta en tu computadora★ 48.148MITActualizado hace 20 días
Instalar
Exa
de exa-labs
Connect AI agents to Exa for web search, content fetching, and multi-step research.
Se ejecuta en la nube★ 5213MITActualizado el mes pasado
Instalar
README del creador
Abrir el README
Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.
Website Auditor MCP
An MCP server for [website-auditor.io](https://website-auditor.io) — AI-visibility (GEO) and site-audit tools you can call from any MCP client (Claude Desktop, Claude Code, Cursor, Codex, and other agents).
Ask an agent *"does ChatGPT recommend my business?"*, *"what's my AI-visibility score?"*, *"audit example.com"*, or *"how do I stack up against my competitors?"* and it answers with real data — an overall AI-visibility score (0–100), a per-engine breakdown across ChatGPT, Perplexity, Claude, Gemini, Microsoft Copilot and Google AI Overviews, a full site audit (security, performance, crawlability and markup), competitor comparisons, and ongoing monitoring.
The server is a thin, authenticated wrapper over the Website Auditor API — the audit engine, AI-visibility scoring and monitoring live in that service; this server just makes them available to agents.
Tools
| Tool | Tier | What it does |
|---|---|---|
get_sample_audit | Free — no key | A complete sample report for example.com in the exact shape a real audit returns. Needs no API key, no subscription and no network. Try this first to see what you'd be buying. |
get_ai_visibility | Pro | Current AI-visibility score (0–100) + per-engine breakdown (ChatGPT, Perplexity, Claude, Gemini, Microsoft Copilot, Google AI Overviews) + the top competitor appearing in your place. Pro subscribers also get trend: 7- and 30-day score movement from stored snapshot history for the question this audit asked, ending at its snapshot and compared only between measured snapshots that asked it, the overall further only between endpoints the same engines answered (a window engines differed over carries its engine deltas and an overall_note saying which answered each; null, with a note, when the audit stored no measured snapshot). Also recommendation_gap (points behind the top beatable rival in the answers that *recommend* you, overall and per engine, with one sentence to read back; marketplaces, delivery apps, directories and national chains are not beatable rivals) and stance_counts (answers that recommended, mentioned or cautioned against you), each present only when measured. Also questions_asked: the questions put to the assistants for the score, when the report recorded them. |
run_audit | Pro, rate-limited | Full one-time audit → category scores (AI visibility, crawlability and markup as seo, security, performance) + top issues + a shareable report URL. Also recommendation_gap and stance_counts (see get_ai_visibility), each present only when measured. |
get_changes | Pro | What changed in the AI-visibility score — the change in the overall score and the per-engine score changes, for engines measured both times, the overall only when the same engines answered both snapshots (else it is null with an overall_note naming which answered each, and the per-engine changes stand alone); summary says the change in plain sentences; competitor_changes, new_issues and resolved_issues are always empty. Only between two snapshots that asked the same question (the same business name, market and queries), read from the domain's series: its measured weekly re-audits and any audit that asked the same question as the newest recorded one, while it has no gap longer than four weeks and a day from the newest weekly re-audit that recorded its question, through each later snapshot of the series (weekly re-audits included, recorded or not), to the newest measured snapshot. When there is no such pair it says why instead of a number, with the date the series re-baselined when it did. The domain need not be tracked: history accrues from any audit of it, tracked or not — track_site adds the weekly re-audits to the series, it is not a precondition. |
compare_competitors | Pro | Head-to-head AI-visibility ranking against named competitor domains + where each appears that you don't. Quota-aware: caps the audit fan-out to your remaining daily quota, reuses recent cached audits, and reports any competitors it had to skip rather than dropping them silently. Also recommendation_gap: how far behind the competitor you trail most you are (ties on identical counts are all named), each side as a share of its own answers, over the assistants that answered for BOTH sites; same_questions says whether both audits asked the same set of questions (null when either did not record them) and assistants which assistants the figures are over. Present only when both audits recorded stances. |
track_site | Pro | Start (or stop) weekly monitoring of a site's AI visibility. Its weekly re-audits join the history get_changes reads from, which audits accrue tracked or not — monitoring watches a site, it does not enable get_changes. |
untrack_site | Pro | Stop monitoring a site and free up a monitoring slot. Deletes the site's monitoring enrollment; past audits are kept. |
list_tracked_sites | Pro | List the sites you're monitoring, with cadence, active state, and slots used/remaining. |
get_monitoring_status | Pro | A glanceable dashboard across all tracked sites — latest score of each site's series (the series get_changes reads), the date of each one's last scheduled run and when the next runs, and the most recent like-for-like change (or a note, or the summary, saying why there is none), shown as its per-engine changes with a note naming the engines when different ones answered the two snapshots; like get_changes, its change carries competitor_changes, new_issues and resolved_issues, always empty. |
list_fixes | Pro | A tracked site's ready-made fixes ("Get this fix"), top first: whether each is needed and why, whether the site's platform can take it, and its newest request and status (live / missing). Records nothing. |
get_fix_facts | Pro | The business facts the fixes are written from, to show the owner: what the site says, what they confirmed, the business name the audits found, and seen (exactly what was shown, sent back unchanged to confirm). |
get_fix | Pro | "Get this fix": the fix served finished (structured data plus About/FAQ text, an llms.txt, or robots.txt lines that let blocked AI assistants in), the first two written only from the owner's confirmed facts, each block ready to copy, with paste steps for the site's platform and copy_all where an agent edits the site. Each call is recorded as a request. Before the facts are confirmed it answers status: "confirm_first" with the facts to show the owner; when the newest audit found nothing to change, status: "nothing_to_fix". |
confirm_facts | Pro | Confirms the facts the owner confirmed or corrected, sending back exactly the seen they were shown — never on the owner's behalf. status: "facts_changed" when the site changed since. |
check_fix | Pro | "I've added it": reads the live site for a fix request and says it's live or names what's missing. Once a minute per request (CHECKED_RECENTLY with retry_after). |
check_upgrade_status | Any valid key | Your own subscription standing — tier, status, period end, and what upgrading unlocks (starting Pro requires a payment method and accepting the Terms). Consumes no audit quota. |
Prompts
Clients that support MCP prompts (Claude Desktop, claude.ai) render these as something you can pick from a menu, so you don't have to phrase the request yourself or know which tool to ask for. In clients that don't surface prompts (Codex, currently), nothing is lost but the menu — ask in words and the same tools run.
| Prompt | Needs a key? | What it does |
|---|---|---|
| See a sample report | No | Walks through a complete report for example.com. No arguments, no setup — one click from any install. |
| Check my AI visibility | Pro | Runs get_ai_visibility for a domain you name, then explains the score, which assistants name the business, and who is named instead. |
| Run a full site audit | Pro | Runs run_audit for a domain and summarises it by category, with the three fixes that matter most. |
| Compare me to a competitor | Pro | Runs compare_competitors for your domain against a named rival, and explains where they get named and you don't. |
Each Pro prompt falls back to get_sample_audit when no API key is configured, so you always get output rather than an error.
Naming the business (optional)
get_ai_visibility and run_audit both accept two optional arguments that decide *what question* the AI-visibility check actually asks. compare_competitors accepts business_location only — see below for why it takes no name:
| Argument | Omitted | Supplied |
|---|---|---|
business_name | Detected from the site, and flagged with name_warning when it could not be verified | Taken as fact and recorded as caller-supplied — which suppresses the warning |
business_location | Detected from the site; if nothing is found the questions widen to the country, or drop the place entirely | Scopes the questions to that place |
Supply a name only when you actually know it. A supplied name overrides detection and is treated as confirmed, so a guess is scored exactly as if a human had verified it — and silences the warning that would have told you otherwise. Leaving it out is the safer default: detection is transparent about its own uncertainty.
The same applies to location, in the other direction. Omitting it is correct for a national or global business and wrong for a local one, since a local business measured without a place is measured against the wrong queries.
On `compare_competitors`: it takes business_location and applies it to your site *and every competitor*, because a comparison asks about one market — scoring you locally while scoring your rivals globally would rank the answers to two different questions. It deliberately takes no business_name: a name identifies one business, and forwarding yours to your competitors would score every one of them as you. The result names the market it used, so a scoped comparison is never mistaken for a global one.
"Check AI visibility for hawaiibackroad.com,the business is Big Island Backroad Adventures in Hilo, HI"
Install & configure
The server runs directly via npx — no clone or build required.
Try it before you buy it. Install with no API key at all and ask your agent for a *sample audit* — get_sample_audit returns a full report for example.com in the exact format a real run produces, so you can check the shape fits your needs first.
Pricing. Auditing real domains needs a Website Auditor subscription at $49/month — eligible new customers get a 7-day free trial (payment method required to start; no charge until the trial ends; customers who used a trial in the last 12 months are billed immediately). Sign up and create an API key at [api.website-auditor.io/admin_portal](https://api.website-auditor.io/admin_portal/?source=mcp), then set it as WA_API_KEY below. There is no free API tier — a key only functions with an active subscription.
Claude Desktop (claude_desktop_config.json), Cursor (~/.cursor/mcp.json), and most other clients use the same mcpServers shape:
{"mcpServers": { "website-auditor": { "command": "npx", "args": ["-y", "website-auditor-mcp"], "env": { "WA_API_KEY": "wa_your_key_here" } } } }
Claude Code — add it from the CLI:
claude mcp add website-auditor -e WA_API_KEY=wa_your_key_here -- npx -y website-auditor-mcpCodex — the CLI, IDE extension and ChatGPT desktop app all read the same ~/.codex/config.toml, so one of these covers all three:
codex mcp add website-auditor --env WA_API_KEY=wa_your_key_here -- npx -y website-auditor-mcp[mcp_servers.website-auditor]command
Solo se muestra el principio; lee el resto en el repo