Citeguard

io.github.Franksterino由 GitHub 帳號 Franksterino 發布v0.1.2更新於 Oct 24, 2026

Verify citations in AI text: fetches each cited source, returns verdicts with evidence quotes.

已驗證Streamable HTTP可網頁執行網頁搜尋與抓取知識與記憶

概覽

AI 產生的概覽

抓取 AI 文本中引用的每個來源,逐條給出論斷判定並附上原文證據引文,還能為整份文件計算引用完整性分數。

可以做什麼
  • 驗證論斷與來源配對,逐條回傳判定結果、證據引文與信心分數
  • 稽核 markdown 或純文字文件中的所有引用,並給出 0 到 100 的引用完整性分數
  • 只檢查引用連結是否存活,標出失效連結、導向首頁的連結以及 archive.org 存檔狀況,不需 LLM
  • 從行內連結、參照式連結、註腳、裸 DOI 與裸網址中擷取論斷與來源配對
適用情境
適合審閱 AI 起草的報告、文章或研究筆記:這些文本的引用連結往往真實可開,卻未必支持文中說法。它用來加快對既有引用的人工查核,既不負責尋找更好的來源,也不判斷論斷本身是否為真。
執行需求
可作為遠端 streamable HTTP 端點使用,也可作為本機 npm 套件執行(npx citeguard-mcp,需要 Node.js)。完整驗證需要判定用 LLM:設定 CITEGUARD_JUDGE_KEY,可選 CITEGUARD_JUDGE_PRESET(qwen、openai、anthropic)或自訂 OpenAI 相容端點。僅查連結不需金鑰。抓取來源需要網路存取。
安裝前請注意
判定用 API 金鑰透過 CITEGUARD_JUDGE_KEY 傳入,並用於呼叫第三方 LLM 服務,因此來源正文與論斷會傳送給該服務商。伺服器會抓取被引用的網址,若使用託管端點,這些網址也會暴露給該端點。supported 判定只表示所引來源如此陳述,並不代表論斷為真。託管端點依 IP 限流。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Citeguard,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式,或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南,先向你展示發布者、端點和登入方式,經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/io.github.Franksterino%2Fciteguard/install.md,並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前,先告訴我它的發布者、端點和登入方式,等我確認。不要把 API 金鑰寫進命令或我會提交的檔案;問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

{
  "mcpServers": {
    "citeguard": {
      "type": "http",
      "url": "https://citeguard.boundy.workers.dev/mcp"
    }
  }
}

README

CiteGuard

Per-claim citation verification for AI-generated text. CiteGuard fetches every cited source and tells you whether it actually supports the claim — with a quoted evidence span, so you can verify the verdict yourself in seconds.

Built for the age of vibe citing: AI-drafted reports full of citations that resolve to real URLs but don't say what the text claims they say.

What it does

Give CiteGuard a document (markdown or plain text) or explicit claim+URL pairs. For each claim it:

  1. Fetches the cited source — with timeout handling, redirect tracking, a 5 MB cap, and an automatic archive.org fallback for dead links.
  2. Checks source liveness — dead URLs, DOI redirects, and "soft 404s" (redirects that land on a homepage) are flagged explicitly.
  3. Extracts the real content — boilerplate-stripped article text via Readability; PDFs supported.
  4. Judges entailment — an LLM reads only the fetched source text (never its own world knowledge) and returns one of six verdicts.
VerdictMeaning
supportedSource clearly states or directly entails the claim
partially_supportedPart of the claim is there, but a material element differs or is absent
contradictedSource states the opposite
unsupportedSource is real but does not contain the claim
uncertainSource text too fragmentary/ambiguous to decide
could_not_fetchSource unreachable and no archive snapshot — never guessed

Every verdict ships with a verbatim evidence quote, a confidence score, and full source status. Document audits also return a citation integrity score (0–100).

CiteGuard never overclaims: if it can't fetch a source, it says so instead of judging blind, and borderline cases land in uncertain — the goal is to make human verification 10× faster, not to replace it.

Quick start (MCP)

Add to Claude Code / Claude Desktop / any MCP client:

json
{  "mcpServers": {    "citeguard": {      "command": "npx",      "args": ["-y", "citeguard-mcp"],      "env": {        "CITEGUARD_JUDGE_PRESET": "qwen",        "CITEGUARD_JUDGE_KEY": "sk-..."      }    }  }}

Tools exposed: verify_claims, check_document, check_links (liveness-only, needs no LLM key).

Quick start (CLI)

bash
npm install -g citeguard
citeguard extract report.md   # show extracted claim/source pairs (no network)citeguard links report.md     # dead-link check (no LLM needed)citeguard check report.md     # full audit (needs judge configured)

Judge configuration

CiteGuard is model-agnostic — anything with an OpenAI-compatible chat endpoint works:

bash
# Preset providersexport CITEGUARD_JUDGE_PRESET=qwen        # or: openai, anthropicexport CITEGUARD_JUDGE_KEY=sk-...
# Or any OpenAI-compatible endpointexport CITEGUARD_JUDGE_URL=https://your-endpoint/v1export CITEGUARD_JUDGE_MODEL=your-modelexport CITEGUARD_JUDGE_KEY=sk-...

Hosted API

A free hosted endpoint (50 requests/day/IP) runs on Cloudflare Workers:

bash
curl -X POST https://citeguard.YOUR-SUBDOMAIN.workers.dev/api/verify \  -H "content-type: application/json" \  -d '{"claims":[{"text":"The Eiffel Tower is 330 m tall.","source":"https://en.wikipedia.org/wiki/Eiffel_Tower"}]}'

Remote MCP endpoint: POST /mcp (streamable HTTP, stateless).

What CiteGuard is not

  • Not an AI-text detector. It doesn't care who wrote the text — it checks whether cited sources support claims.
  • Not a truth oracle. A supported verdict means the cited source says this, not this is true. Garbage source in, garbage support out.
  • Not a search engine. It verifies the citations you have; it doesn't find better ones (yet).

Extraction formats

Markdown inline links, reference-style links, footnotes, bare DOIs (resolved via doi.org), bare URLs. APA-style parsing and PDF input documents are on the roadmap.

Development

bash
git clone https://github.com/Franksterino/citeguardcd citeguardnpm installnpm run typechecknpx tsx src/cli.ts extract test/fixtures/sample.md

License

MIT

來源:README.md,提交 e3414fa

工具

3

verify_claims

Verify claim+source pairs: fetches each cited URL and returns a per-claim verdict (supported / partially_supported / contradicted / unsupported / uncertain / could_not_fetch) with a quoted evidence span from the source.

輸入參數claims必填

check_document

Audit every citation in a markdown/plain-text document: extracts claim+source pairs (markdown links, footnotes, DOIs, bare URLs), verifies each against the fetched source, and returns a report with a citation integrity score (0-100).

輸入參數document必填

版本歷史

1
  1. v0.1.2最新Sep 16, 2026

評分

已滿足適用檢查項的 100%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分