Permite que un agente de IA verifique si los sitios web son legibles y citables por bots de IA como ChatGPT, Claude y Perplexity.
También conocido como genzagents/citable, citable-cli
- Stars
- 0
- Herramientas
- —
- Descargas, 30 días
- —
- Última versión
- 0.4.2
- Último commit
- 5 nov 2026
- Licencia
- MIT
¿Qué es citable MCP?
Permite que un agente de IA verifique si los sitios web son legibles y citables por bots de IA como ChatGPT, Claude y Perplexity.
Resumen generado a partir del README del proyecto
Acerca del MCP server de citable
citable permite verificar que los sitios web sean accesibles y tengan el formato adecuado para los agentes de IA. Permite a desarrolladores y propietarios de sitios probar si los bots de OpenAI, Anthropic y Perplexity pueden rastrear, leer y citar su contenido con éxito. A diferencia de los verificadores estándar que solo revisan el robots.txt, esta herramienta realiza peticiones en vivo para ver si Cloudflare, las reglas de WAF o los limitadores de tasa están bloqueando a los bots de IA en el edge.
Los usuarios pueden ejecutar esto como un MCP server local vía stdio para integrarlo con clientes como Claude Desktop, Cursor o Claude Code. El servidor proporciona herramientas específicas como check_site y draft_llms_txt para automatizar auditorías. Evalúa una amplia gama de factores técnicos, incluyendo la presencia de llms.txt, la dependencia de JavaScript, los datos estructurados JSON-LD y la higiene del sitemap. El sistema proporciona una puntuación sobre 100 e identifica fallos específicos con sugerencias de corrección para mejorar la visibilidad ante la IA.
Qué puedes hacer con él
- 1Generar archivos de documentaciónHaz que un cliente de IA cree un archivo llms.txt inicial basado en el contenido de una página de inicio.
- 2Monitorear regresionesConfigura una vigilancia semanal para recibir notificaciones si un despliegue bloquea accidentalmente a los bots de IA o elimina archivos críticos.
- 3Rastrear el rendimiento de las citasDetermina qué prompts específicos resultan en que los motores de IA citen tu marca en lugar de a un competidor.
Escrito a partir del README del proyecto. Cada caso de uso se verifica con una cita del mismo.
Cómo instalar citable MCP
Formatos verificados el 10 nov 2026Añadir a CursorAñadir a GooseInstalar citable MCP en Claude Code
$ claude mcp add citable -- uvx citable-cliInstalar citable MCP en Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"citable": {
"command": "uvx",
"args": [
"citable-cli"
]
}
}
}Instalar citable MCP en VS Code
.vscode/mcp.json
{
"servers": {
"citable": {
"type": "stdio",
"command": "uvx",
"args": [
"citable-cli"
]
}
}
}Instalar citable MCP en VS Code CLI
$ code --add-mcp '{"name":"citable","type":"stdio","command":"uvx","args":["citable-cli"]}'Instalar citable MCP en Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"citable": {
"command": "uvx",
"args": [
"citable-cli"
]
}
}
}Instalar citable MCP en Codex
$ codex mcp add citable -- uvx citable-cliInstalar citable MCP en Codex config.toml
~/.codex/config.toml
[mcp_servers.citable] command = "uvx" args = ["citable-cli"]
Instalar citable MCP en Gemini CLI
$ gemini mcp add -s user citable uvx -- citable-cliInstalar citable MCP en Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"citable": {
"command": "uvx",
"args": [
"citable-cli"
]
}
}
}Verificaciones automáticas
Ejecutado 14 nov 2026Informe completo →Pasó nuestras verificaciones automáticas. Esto no es una auditoría de seguridad: lee el código y dale al servidor el acceso más limitado que necesite. Cómo funcionan las verificaciones
- Repositorio de origen vinculado y accesiblegenzagents/citable is public and reachablegithub.com/genzagents/citable ↗Aprobado
- El paquete indica este repositorio como su origencitable-cli names genzagents/citable as sourcepypi.org/project/citable-cli/ ↗Aprobado
- Procedencia de la compilación (atestación de Sigstore)Sigstore attestation for citable-clipypi.org/project/citable-cli/ ↗Aprobado
- Licencia de código abierto (OSI)MITspdx.org/licenses/MIT.html ↗Aprobado
- Commit o lanzamiento en el último añoLast commit or release 2026-11-05github.com/genzagents/citable ↗Aprobado
- OpenSSF ScorecardNo verificado
- El nombre del paquete no es similar a un paquete popularNo popular package one edit away from citable-cliAprobado
- No hay avisos críticos en el paquete ni en sus dependencias1 resolved dependencies checked; no critical advisoryosv.dev ↗Aprobado
- Sin instrucciones ocultas para el modelo0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersAprobado
- Las herramientas destructivas están etiquetadasNo verificado
- El endpoint remoto responde al handshake de MCPNo verificado
README
Ver en GitHubcitable
Can ChatGPT, Claude and Perplexity actually read and cite your site?
Most "AI visibility" checkers read robots.txt and stop. citable fetches your homepage as each AI bot
and reports the blocks that robots.txt never mentions (Cloudflare "Block AI bots", WAF rules, rate limiters),
then checks the rest of the list: llms.txt, JSON-LD, title and description, JS-only content, sitemap, canonical.
Score out of 100, every failure with the fix. Also runs as an MCP server so your agent can check sites for you.
Zero dependencies. One file. Python 3.9+.
pipx install citable-cli # from PyPI; on a Mac: brew install pipx first. Or: uvx --from citable-cli citable
citable example.com # report
citable example.com --json # for scripts and CI (exit 1 if below --min-score=N)
citable example.com --llms-txt # a starter llms.txt built from your homepage
citable watch a.com b.com # weekly watch: GitHub issue per site, comment (email) on regressions
citable track a.com "best X" "how Y" # prompt tracking: which engines cite you, who gets cited instead
No install at all:
curl -sL https://raw.githubusercontent.com/genzagents/citable/main/citable/__init__.py | python3 - example.com
What a run looks like
citable 0.3.0: https://reddit.com/
score 13/100 grade F (final URL https://www.reddit.com/)
[FAIL] 0/15 robots.txt allows answer engines: robots.txt blocks: OAI-SearchBot, ChatGPT-User, Claude-SearchBot, ...
[FAIL] 0/20 Answer engines not blocked at the edge: Fetching the homepage as a bot: ChatGPT-User got HTTP 403; a browser got 200.
fix: Your CDN or WAF (Cloudflare 'Block AI bots', bot-fight mode, a rate limiter) is refusing them ...
[FAIL] 0/15 /llms.txt: /llms.txt returns HTTP 404.
...
Bot Vendor Role robots.txt live fetch
OAI-SearchBot OpenAI answer block HTTP 200
ChatGPT-User OpenAI answer block HTTP 403 <- BLOCKED
Claude-SearchBot Anthropic answer block HTTP 200
...
What it checks
| Check | Points | Why it matters |
|---|---|---|
| robots.txt allows the answer bots (OAI-SearchBot, ChatGPT-User, Claude-SearchBot, Claude-User, PerplexityBot, Perplexity-User, DuckAssistBot, Bingbot, Googlebot) | 15 | These fetch pages to answer live questions and cite the source. Blocked means never cited. |
| Not blocked at the edge: homepage fetched as each of those bots returns what a browser gets | 20 | CDN and WAF "block AI" toggles stop bots that robots.txt allows. Nothing else on this list matters until this passes. |
| Training crawlers (GPTBot, ClaudeBot, Google-Extended, CCBot, Applebot-Extended, meta-externalagent, Amazonbot, Bytespider) | info | Blocking them is a legitimate choice and does not affect citations. Reported, never penalised. |
/llms.txt present, plain text, with an H1, a > summary and links |
15 | The convention answer engines and agents read first. A soft-404 HTML page counts as missing. |
| Content readable without JavaScript (words in the raw HTML) | 15 | Most AI crawlers do not run JS. A client-rendered shell is invisible to them. |
| JSON-LD structured data (Organization, WebSite, Article, FAQPage...) | 10 | Entities and FAQs get quoted directly. |
| Title and meta description, sensible lengths | 8 | Quoted verbatim in answers. |
HTTPS, response time, canonical, Open Graph, sitemap, <html lang>, no noindex |
22 | Hygiene that decides which URL gets the citation. |
As an MCP server (Claude Code, Claude Desktop, Cursor, any MCP client)
Tools: check_site(url, live=true) and draft_llms_txt(url).
Claude Code plugin (includes the MCP server and a skill that knows how to act on the report):
claude plugin marketplace add genzagents/marketplace
claude plugin install citable@genzagents
Any MCP client, by hand:
{ "mcpServers": { "citable": { "command": "python3", "args": ["/path/to/citable/citable/__init__.py", "mcp"] } } }
The server speaks MCP over stdio with no dependencies, so it runs anywhere Python does.
In CI
Fail the build when a deploy breaks AI access (a new WAF rule, a lost llms.txt, a Disallow: / that slipped in):
citable yoursite.com --min-score=70 --json > citable.json
Watch
A deploy that flips a WAF toggle silently removes you from every AI answer. The watch is the alarm. It runs as a
GitHub Action in any repo you own (it need not be the site's repo), keeps one issue per site up to date, and
comments on that issue the moment an answer bot is blocked, llms.txt disappears, the site goes down or the
score drops, which GitHub emails to you. No server, no account, no dependencies. Example: issue #1 watches this project's own page.
Copy docs/watch.yml to .github/workflows/citable-watch.yml:
on:
schedule: [{ cron: "17 6 * * 1" }] # Mondays
workflow_dispatch:
permissions: { issues: write, contents: read }
jobs:
watch:
runs-on: ubuntu-latest
steps:
- uses: genzagents/citable@v0.4.2
with:
sites: |
example.com
docs.example.com
# min-score: 75
Inputs: sites (required), min-score (fail below it), live (fetch as each bot, default true), issue
(track in an issue, default true), notify (login to @mention on a regression, default repo owner),
fail-on-regression (default true). Outputs: score, regressed, changed. Same thing from a shell where gh is logged in:
citable watch example.com docs.example.com --repo=you/your-repo --notify=you
Hosted, $12/month (about £9): the same watch run by us, no repo needed, up to 5 domains, with a weekly digest. Live now through GitHub Sponsors:
- Sponsor genzagents at $12 a month →
- Open your Hosted watch issue → from the same account. Reports are posted on it (the issue is public).
Track
The watch tells you whether engines can read you. Track tells you whether they do: for the questions you want to be the answer to, does ChatGPT, Claude or Perplexity link to your site, and who gets linked instead?
citable track example.com "best tools for X" "how do I Y" --brand=Example
## citable track: example.com
**Visibility 50%**: share of prompt-and-engine pairs where an answer linked to your site.
| Prompt | anthropic | openai | perplexity |
|---|---|---|---|
| best tools for X | **cited** | mentioned | **cited** |
| how do I Y | no | no | no |
**Who gets cited instead** (answers citing them): rival.io (4), other.org (2)
Engines: anthropic (ANTHROPIC_API_KEY, the web_search tool), openai (OPENAI_API_KEY, Responses API web search),
perplexity (PERPLEXITY_API_KEY, sonar) and claude-code (the claude CLI on your machine, no key). Every engine
whose key is present runs; --engines= picks a subset. Add --issue --repo=you/repo (or run it from the Action with
a prompts: input) and it keeps a "citable track: example.com" issue up to date and comments when a citation is
lost, which is the weekly email the paid tools charge $29 to $39 a month for. Bring your own keys; a 10-prompt run on
three engines costs a few cents.
Hosted ($12/month, about £9)
No repo, no keys, no cron: sponsor genzagents at $12 a month, open a Hosted watch issue with your sites (up to 5), the prompts that matter (up to 10) and your brand, and the first report is posted on the issue within the hour. After that you get a comment the moment something regresses and a digest once a week with the prompt tracking (GitHub emails you each one). Cancel from your GitHub sponsorships page.
citable hosted run --source=github matches active sponsors to the open hosted issues they authored and comments
the reports there, so it needs only a GitHub token. The Polar + Resend mode below is for private email delivery.
The runner is in this repo (citable hosted), so you can also run the same thing yourself for your own customers:
it polls Polar for active subscriptions, keeps one small state file per subscriber, and sends
through Resend. Zero dependencies, one hourly cron. See docs/HOSTED.md.
citable hosted run --dry-run # against Polar, prints the emails instead of sending
citable hosted run --subscribers=subs.json # against a local list (no Polar), e.g. for your own clients
citable hosted launchd # a launchd plist that runs it hourly on a Mac
Notes
-
MCP registry name:
mcp-name: io.github.genzagents/citable(PyPI packagecitable-cli; the import and the command staycitable). -
Bot user agents and roles follow the vendors' published strings (OpenAI, Anthropic, Perplexity). Role "answer" = fetches to answer or cite in a live conversation; "train" = builds training corpora.
-
The edge check compares HTTP status only. A site that returns 200 with a challenge page to bots will pass; file an issue with the domain and it gets a heuristic.
-
--no-liveskips the bot fetches (faster, robots.txt only).
Development
python3 -m unittest discover -s tests -v
MIT. Built by genzagents.
Preguntas sobre citable MCP
¿Cómo agrego citable MCP a Claude Code?
Ejecuta claude mcp add citable -- uvx citable-cli en tu terminal. Añade --scope user para que esté disponible en todos los proyectos.
¿Cómo agrego citable MCP a Cursor?
Abre ~/.cursor/mcp.json y añade el servidor en mcpServers, usando la configuración de Cursor que se muestra en la sección de instalación de arriba.
¿Puedo usar esto como un MCP server?
Sí, se puede usar con cualquier cliente MCP como Claude Desktop o Cursor a través de stdio.