ChatGPT、Claude、PerplexityなどのAIボットが、ウェブサイトを読み取り、引用できるかどうかをAIエージェントが確認できるようにします。
別名 genzagents/citable, citable-cli
- スター
- 0
- ツール
- —
- ダウンロード数(30日間)
- —
- 最新バージョン
- 0.4.2
- 最終コミット
- 2026年11月5日
- ライセンス
- MIT
citable MCPとは
ChatGPT、Claude、PerplexityなどのAIボットが、ウェブサイトを読み取り、引用できるかどうかをAIエージェントが確認できるようにします。
プロジェクトのREADMEから生成された概要
citable MCP server について
citableは、ウェブサイトがAIエージェントにとってアクセス可能で、適切にフォーマットされているかを検証します。これにより、開発者やサイト所有者は、OpenAI、Anthropic、Perplexityのボットがコンテンツを正常にクロール、読み取り、引用できるかどうかをテストできます。robots.txtのみを確認する標準的なチェッカーとは異なり、このツールはライブフェッチを実行して、Cloudflare、WAFルール、またはレートリミッターがエッジでAIボットをブロックしていないかを確認します。
ユーザーは、stdioを介したローカルのMCP serverとして実行し、Claude Desktop、Cursor、Claude Codeなどのクライアントと統合できます。このサーバーは、監査を自動化するためにcheck_siteやdraft_llms_txtなどの特定のツールを提供します。llms.txtの有無、JavaScriptへの依存性、JSON-LD構造化データ、サイトマップの健全性など、幅広い技術的要因を評価します。システムは100点満点のスコアを提供し、AIの視認性を向上させるための具体的な修正案とともに、特定されたエラーを特定します。
できること
- 1ドキュメントファイルの生成AIクライアントを使用して、ホームページのコンテンツに基づいた初期のllms.txtファイルを作成します。
- 2リグレッションの監視デプロイによって誤ってAIボットがブロックされたり、重要なファイルが削除されたりした場合に通知を受け取るよう、週次での監視を設定します。
- 3引用パフォーマンスの追跡どの特定のプロンプトによって、AIエンジンが競合他社ではなく自社ブランドを引用するかを判断します。
プロジェクトの README から作成されています。すべてのユースケースは、その引用と照らし合わせて確認されています。
citable MCPのインストール方法
フォーマット検証日 2026年11月10日Cursor に追加Gooseに追加Claude Codeにcitable MCPをインストール
$ claude mcp add citable -- uvx citable-cliCursorにcitable MCPをインストール
~/.cursor/mcp.json
{
"mcpServers": {
"citable": {
"command": "uvx",
"args": [
"citable-cli"
]
}
}
}VS Codeにcitable MCPをインストール
.vscode/mcp.json
{
"servers": {
"citable": {
"type": "stdio",
"command": "uvx",
"args": [
"citable-cli"
]
}
}
}VS Code CLIにcitable MCPをインストール
$ code --add-mcp '{"name":"citable","type":"stdio","command":"uvx","args":["citable-cli"]}'Claude Desktopにcitable MCPをインストール
claude_desktop_config.json
{
"mcpServers": {
"citable": {
"command": "uvx",
"args": [
"citable-cli"
]
}
}
}Codexにcitable MCPをインストール
$ codex mcp add citable -- uvx citable-cliCodex config.tomlにcitable MCPをインストール
~/.codex/config.toml
[mcp_servers.citable] command = "uvx" args = ["citable-cli"]
Gemini CLIにcitable MCPをインストール
$ gemini mcp add -s user citable uvx -- citable-cliGemini settings.jsonにcitable MCPをインストール
~/.gemini/settings.json
{
"mcpServers": {
"citable": {
"command": "uvx",
"args": [
"citable-cli"
]
}
}
}自動チェック
実行日 2026年11月14日完全なレポート →自動チェックに合格しました。これはセキュリティ監査ではありません。コードを読み、サーバーに必要最小限のアクセス権を与えてください。 チェックの仕組み
- ソースリポジトリがリンクされており、アクセス可能genzagents/citable is public and reachablegithub.com/genzagents/citable ↗合格
- パッケージがこのリポジトリをソースとして指定citable-cli names genzagents/citable as sourcepypi.org/project/citable-cli/ ↗合格
- ビルドの来歴 (Sigstore 証明)Sigstore attestation for citable-clipypi.org/project/citable-cli/ ↗合格
- オープンソースライセンス (OSI)MITspdx.org/licenses/MIT.html ↗合格
- 過去1年以内にコミットまたはリリースありLast commit or release 2026-11-05github.com/genzagents/citable ↗合格
- OpenSSF Scorecard未チェック
- パッケージ名が有名なパッケージに酷似していないNo popular package one edit away from citable-cli合格
- パッケージおよびその依存関係に重大な勧告なし1 resolved dependencies checked; no critical advisoryosv.dev ↗合格
- モデルへの隠れた指示がない0 tool descriptions and the README read; no override phrases, credential paths or hidden characters合格
- 破壊的なツールがラベル付けされている未チェック
- リモートエンドポイントが MCP ハンドシェイクに応答未チェック
README
GitHubで見るcitable
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のよくある質問
citable MCPをClaude Codeに追加するには
ターミナルでclaude mcp add citable -- uvx citable-cliを実行します。すべてのプロジェクトで利用するには--scope userを追加します。
citable MCPをCursorに追加するには
~/.cursor/mcp.jsonを開き、上記のインストールセクションに示すCursor設定を使ってmcpServersの下にサーバーを追加します。
MCP serverとして使用できますか?
はい、stdioを介してClaude DesktopやCursorなどのあらゆるMCPクライアントで使用可能です。