Ermöglicht es einem AI Agent zu prüfen, ob Websites für AI Bots wie ChatGPT, Claude und Perplexity lesbar und zitierfähig sind.
Auch bekannt als genzagents/citable, citable-cli
- Stars
- 0
- Tools
- —
- Downloads, 30 Tage
- —
- Neueste Version
- 0.4.2
- Letzter Commit
- 5. Nov. 2026
- Lizenz
- MIT
Was ist citable MCP?
Ermöglicht es einem AI Agent zu prüfen, ob Websites für AI Bots wie ChatGPT, Claude und Perplexity lesbar und zitierfähig sind.
Zusammenfassung generiert aus dem README des Projekts
Über citable MCP server
citable ermöglicht es zu verifizieren, dass Websites für AI Agents zugänglich und korrekt formatiert sind. Es erlaubt Entwicklern und Website-Betreibern zu testen, ob Bots von OpenAI, Anthropic und Perplexity deren Inhalte erfolgreich crawlen, lesen und zitieren können. Im Gegensatz zu Standard-Checkern, die nur die robots.txt prüfen, führt dieses Tool Live-Fetches durch, um zu sehen, ob Cloudflare, WAF-Regeln oder Rate Limiter AI Bots am Edge blockieren.
Nutzer können dies als lokalen MCP server via stdio ausführen, um es in Clients wie Claude Desktop, Cursor oder Claude Code zu integrieren. Der Server stellt spezifische Tools wie check_site und draft_llms_txt bereit, um Audits zu automatisieren. Er bewertet eine Vielzahl technischer Faktoren, einschließlich der Präsenz von llms.txt, JavaScript-Abhängigkeiten, JSON-LD strukturierten Daten und der Sitemap-Hygiene. Das System liefert einen Score von 100 und identifiziert spezifische Fehler mit Lösungsvorschlägen, um die AI-Sichtbarkeit zu verbessern.
Was du damit machen kannst
- 1Dokumentationsdateien generierenLass einen AI Client eine erste llms.txt Datei basierend auf dem Inhalt einer Homepage erstellen.
- 2Regressions überwachenRichte einen wöchentlichen Check ein, um Benachrichtigungen zu erhalten, falls ein Deployment versehentlich AI Bots blockiert oder kritische Dateien entfernt.
- 3Zitier-Performance trackenErmittle, welche spezifischen Prompts dazu führen, dass AI Engines deine Marke gegenüber einem Wettbewerber zitieren.
Geschrieben aus dem README des Projekts. Jeder Use Case wurde gegen ein Zitat daraus geprüft.
So installierst du citable MCP
Formate geprüft am 10. Nov. 2026Zu Cursor hinzufügenZu Goose hinzufügencitable MCP in Claude Code installieren
$ claude mcp add citable -- uvx citable-clicitable MCP in Cursor installieren
~/.cursor/mcp.json
{
"mcpServers": {
"citable": {
"command": "uvx",
"args": [
"citable-cli"
]
}
}
}citable MCP in VS Code installieren
.vscode/mcp.json
{
"servers": {
"citable": {
"type": "stdio",
"command": "uvx",
"args": [
"citable-cli"
]
}
}
}citable MCP in VS Code CLI installieren
$ code --add-mcp '{"name":"citable","type":"stdio","command":"uvx","args":["citable-cli"]}'citable MCP in Claude Desktop installieren
claude_desktop_config.json
{
"mcpServers": {
"citable": {
"command": "uvx",
"args": [
"citable-cli"
]
}
}
}citable MCP in Codex installieren
$ codex mcp add citable -- uvx citable-clicitable MCP in Codex config.toml installieren
~/.codex/config.toml
[mcp_servers.citable] command = "uvx" args = ["citable-cli"]
citable MCP in Gemini CLI installieren
$ gemini mcp add -s user citable uvx -- citable-clicitable MCP in Gemini settings.json installieren
~/.gemini/settings.json
{
"mcpServers": {
"citable": {
"command": "uvx",
"args": [
"citable-cli"
]
}
}
}Automatisierte Checks
Geluften am 14. Nov. 2026Vollständiger Bericht →Unsere automatisierten Checks bestanden. Das ist kein Security-Audit: Lies den Code und gib dem Server nur den minimal notwendigen Zugriff. Wie die Checks funktionieren
- Source Repository verknüpft und erreichbargenzagents/citable is public and reachablegithub.com/genzagents/citable ↗Bestanden
- Paket nennt dieses Repository als Quellecitable-cli names genzagents/citable as sourcepypi.org/project/citable-cli/ ↗Bestanden
- Build-Provenienz (Sigstore-Attestierung)Sigstore attestation for citable-clipypi.org/project/citable-cli/ ↗Bestanden
- Open Source Lizenz (OSI)MITspdx.org/licenses/MIT.html ↗Bestanden
- Commit oder Release im letzten JahrLast commit or release 2026-11-05github.com/genzagents/citable ↗Bestanden
- OpenSSF ScorecardNicht geprüft
- Package-Name ähnelt keinem populären PackageNo popular package one edit away from citable-cliBestanden
- Keine kritischen Advisories im Paket oder seinen Abhängigkeiten1 resolved dependencies checked; no critical advisoryosv.dev ↗Bestanden
- Keine versteckten Anweisungen an das Modell0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersBestanden
- Destruktive Tools sind markiertNicht geprüft
- Remote-Endpoint beantwortet den MCP-HandshakeNicht geprüft
README
Auf GitHub ansehencitable
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.
citable MCP Fragen
Wie füge ich citable MCP zu Claude Code hinzu?
Führe claude mcp add citable -- uvx citable-cli in deinem Terminal aus. Füge --scope user hinzu, damit der Server in jedem Projekt verfügbar ist.
Wie füge ich citable MCP zu Cursor hinzu?
Öffne ~/.cursor/mcp.json und füge den Server unter mcpServers hinzu, mit der Cursor-Config aus dem Installationsabschnitt oben.
Kann ich das als MCP server nutzen?
Ja, es kann mit jedem MCP Client wie Claude Desktop oder Cursor via stdio genutzt werden.