AI 에이전트가 ChatGPT, Claude, Perplexity와 같은 AI 봇이 웹사이트를 읽고 인용할 수 있는지 확인합니다.
다른 이름 genzagents/citable, citable-cli
- 스타
- 0
- Tools
- —
- 다운로드, 30일
- —
- 최신 버전
- 0.4.2
- 마지막 커밋
- 2026년 11월 5일
- 라이선스
- MIT
citable MCP란?
AI 에이전트가 ChatGPT, Claude, Perplexity와 같은 AI 봇이 웹사이트를 읽고 인용할 수 있는지 확인합니다.
프로젝트 README에서 생성된 요약
citable MCP server 정보
citable은 웹사이트가 AI 에이전트가 접근하기 용이하고 적절한 형식으로 구성되어 있는지 검증합니다. 개발자와 사이트 소유자는 OpenAI, Anthropic, Perplexity의 봇이 콘텐츠를 성공적으로 크롤링하고 읽고 인용할 수 있는지 테스트할 수 있습니다. robots.txt만 확인하는 일반적인 검사기와 달리, 이 도구는 실시간 fetch를 수행하여 Cloudflare, WAF 규칙 또는 rate limiter가 에지에서 AI 봇을 차단하고 있는지 확인합니다.
사용자는 이를 로컬 MCP server로 실행하여 stdio를 통해 Claude Desktop, Cursor 또는 Claude Code와 같은 client와 통합할 수 있습니다. 이 server는 audit을 자동화하기 위해 check_site 및 draft_llms_txt와 같은 특정 tool을 제공합니다. llms.txt 존재 여부, JavaScript 의존성, JSON-LD 구조화 데이터, sitemap 상태 등 광범위한 기술적 요소를 평가합니다. 시스템은 100점 만점의 점수를 제공하며, AI 가시성을 높이기 위한 수정 제안과 함께 구체적인 실패 원인을 식별합니다.
활용 사례
- 1문서 파일 생성AI client를 사용하여 홈페이지 콘텐츠를 기반으로 초기 llms.txt 파일을 생성합니다.
- 2회귀 발생 모니터링배포 시 실수로 AI 봇을 차단하거나 중요한 파일을 삭제하는 경우 알림을 받도록 주간 모니터링을 설정합니다.
- 3인용 성능 추적어떤 특정 프롬프트가 경쟁사가 아닌 귀하의 브랜드를 인용하게 만드는지 파악합니다.
프로젝트의 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를 열고 mcpServers 아래에 서버를 추가합니다. 위 설치 섹션에 표시된 Cursor 구성을 사용합니다.
MCP server로 사용할 수 있나요?
네, stdio를 통해 Claude Desktop 또는 Cursor와 같은 모든 MCP client에서 사용할 수 있습니다.