原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。评价和账户功能将在后续阶段推出。
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

CiteGuard

作者:lonexreb版本 0.1.2i★ –i在你的电脑上运行
注册名称io.github.lonexreb/retractguard

安装

概览

作者提供的说明(英文原文)

Open watchdog for retracted & problematic citations: Retraction Watch, OpenAlex, Crossref.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

  • 连接方式: 在你的电脑上运行
  • 传输方式: stdio
  • 分类: 其他
  • 你需要填写:OPENALEX_API_KEY

安装

选择你使用的 AI 应用,然后复制设置。

安装之前

  • 基础检查:1 项中通过 1 项
  • 在你的电脑上运行,拥有你的用户账户的权限(文件、网络、应用)。
  • 需要你自己填写: OPENALEX_API_KEY, CITEGUARD_MAILTO

标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。

你需要

  • PyPI已安装 Python 的 uv(用于 uvx 命令)

你用的是哪个应用?

在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "retractguard": {
      "command": "uvx",
      "args": [
        "retractguard"
      ],
      "env": {
        "OPENALEX_API_KEY": "your-value",
        "CITEGUARD_MAILTO": "your-value"
      }
    }
  }
}

在终端中运行这条命令

claude mcp add retractguard --env OPENALEX_API_KEY=your-value --env CITEGUARD_MAILTO=your-value -- uvx retractguard

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "retractguard": {
      "command": "uvx",
      "args": [
        "retractguard"
      ],
      "env": {
        "OPENALEX_API_KEY": "your-value",
        "CITEGUARD_MAILTO": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "retractguard": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "retractguard"
      ],
      "env": {
        "OPENALEX_API_KEY": "your-value",
        "CITEGUARD_MAILTO": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上,无需账户。

需要你填写的值

  • OPENALEX_API_KEY 机密 env
    OpenAlex API key (required for live OpenAlex lookups and watch_institution).
  • CITEGUARD_MAILTO env
    Contact email for the OpenAlex/Crossref polite pool.

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。

它能做什么

它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月8日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 lonexreb 验证,该账户拥有此仓库

  • … 尚未检查

    仍在维护

    我们还没有从 GitHub 读取这个仓库

  • … 尚未检查

    有许可证

    我们还没有从 GitHub 读取这个仓库

  • – 不适用

    端点有响应

    它在你的电脑上运行,没有互联网端点

  • – 不适用

    使用 OAuth 登录

    在你的电脑上运行,改用本地设置

  • … 尚未检查

    工具描述中没有隐藏指令

    它在你的电脑上运行;我们只能读取互联网端点的工具列表

与“其他”中的其他服务器比较i

  • 星标数多于此分类中其他 18433 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 18433 个服务器的 15% 更新
  • 基础检查结果等于或优于此分类中其他 18433 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

CiteGuard 安全吗?

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

你需要填写:OPENALEX_API_KEY

它在我的电脑上运行还是在云端?

它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。

它还在维护吗?

GitHub 仓库最后更新于–,最新版本(0.1.2)于4个月前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv)。

有什么可以替代它?

同一分类中有:Spec Driven Development, Remote Desktop Commander, MyGroceryPal

替代选择

同一分类中其他作者的服务器,按星标数排序。

如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Spec Driven Development

作者:formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

在你的电脑上运行★ 440MIT14个月前更新
安装

Remote Desktop Commander

作者:desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

在云端运行★ 2113天前更新
安装

MyGroceryPal

作者:mygrocerypal.co.uk

UK supermarket prices: compare products and baskets across 13 stores, see price history, set alerts.

在云端运行今天更新
安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

CiteGuard

The free, open, OpenAlex-native watchdog for retracted and problematic citations.

CiteGuard tells you — and keeps telling you — when your references, your authors, or your institution's papers cite research the community has flagged as retracted, corrected, or subject to an expression of concern.

It exists because the existing options each fall short: scite is proprietary and paywalled, RetractoBot had to license Scopus (no open citation database existed at the time), and OpenAlex collapses all editorial status into a single is_retracted boolean that can't tell a retraction from a correction — and has produced false positives in the past.

Now that the Retraction Watch dataset is open (via Crossref) and the OpenAlex citation graph is CC0, CiteGuard can do this fully in the open, for free.

Status: early development. Building the MVP. See GOAL.md for the mission and

CLAUDE.md for the build guide.

What it does

  • Check a reference list. Paste a DOI or upload a .bib file → get a per-reference status: retracted, corrected, expression of concern, hijacked-journal, or clean.
  • Nuanced status, not a boolean. Every flag carries its source (Retraction Watch / OpenAlex / Crossref), an evidence link, a date, and a confidence note. When sources disagree, CiteGuard surfaces the conflict instead of silently guessing.
  • Watch an institution. Point it at a ROR ID → get a digest when any of that institution's works cites (or becomes) a newly-flagged paper.
  • Use it from an AI agent. An MCP server exposes the same logic as tools (check_references, get_editorial_status, watch_institution) for Claude, Cursor, and any MCP-compatible client.

Why it's trustworthy

Integrity tooling can do real harm if it's wrong — a false "retracted" flag damages a real author. CiteGuard is conservative by design: it corroborates before flagging, prefers the documented editorial notice, and marks a work UNKNOWN rather than guess. Every core capability ships with a published eval reporting precision and recall on a gold set.

Who it's for

  • Research-integrity officers and journal editors screening submissions
  • Academic librarians at OpenAlex-adopting institutions
  • Systematic reviewers (one retracted included study can invalidate a review)
  • Developers and meta-scientists building on the MCP server
  • Authors checking their own bibliography before submission

Architecture

One core, two surfaces.

                 ┌─────────────────────────────┐

OpenAlex ─────▶ │ (CC0 graph) │ editorial-status model │──▶ MCP server │ + resolution logic │ (check_references, Retraction ──▶│ (conservative) │ get_editorial_status, Watch (open) │ │ watch_institution) │ │──▶ reference-list checker Crossref ─────▶ │ (DOI / .bib → statuses, (DOI norm.) └─────────────────────────────┘ thin web UI)

Repository layout:

src/citeguard/

openalex.py # keyed, rate-aware, ID-lookup-first OpenAlex client retractionwatch.py # ingest + normalize the Retraction Watch dump status.py # the EditorialStatus model + resolution logic (core) checker.py # reference-list checker (DOI / .bib -> statuses) mcp_server.py # MCP server exposing the three tools tests/ # pytest unit + functional tests evals/ # gold sets + precision/recall harness data/ # local RW dump + cached lookups (gitignored)

Design constraints (important)

  • Free-tier-aware. OpenAlex API keys are required (since Feb 13, 2026); the free tier is small and search costs ~10× a record lookup. CiteGuard resolves to IDs first and looks up by ID; bulk work uses the free monthly snapshot, and the live API is reserved for incremental checks.
  • Open and reproducible. CC0 ethos, with proper attribution to Retraction Watch and OpenAlex, thorough docs, and a Zenodo DOI.

Getting started (dev)

Requires Python 3.11+ and uv.

uv sync                                   # install dependencies

export OPENALEX_API_KEY=... # your OpenAlex key export CITEGUARD_MAILTO=you@example.org # polite-pool contact

uv run pytest # run tests uv run python -m evals.run # run the eval harness (precision/recall) uv run python -m citeguard.mcp_server # launch the MCP server locally

Connect it as an MCP server

CiteGuard exposes get_editorial_status, check_references, and watch_institution to any MCP client. After pip install retractguard (or uv tool install retractguard), the retractguard-mcp command launches the stdio server.

Claude Desktop — add to claude_desktop_config.json:

{

"mcpServers": { "retractguard": { "command": "retractguard-mcp", "env": { "OPENALEX_API_KEY": "your-key", "CITEGUARD_MAILTO": "you@example.org" } } } }

Cursor / other clients — point them at the same retractguard-mcp command (stdio transport). Running from a checkout instead of an install? Use "command": "uv", "args": ["run", "retractguard-mcp"] with "cwd" set to the repo.

On first call the server downloads the Retraction Watch dump (~65 MB, free) into CITEGUARD_DATA_DIR (default ./data). Editorial-notice lookups (Retraction Watch, Crossref) need no key; OpenAlex corroboration and watch_institution do.

The web checker

A thin web UI for people who don't live in an editor — paste DOIs or drop a .bib file, get a per-reference status table.

retractguard-web            # then open http://127.0.0.1:8000

or from a checkout: uv run python -m citeguard.web

Add Accept: application/json to POST /check to get the results as JSON instead of a table. It reuses the same conservative resolution logic as the MCP server — no separate code path, no separate trust model.

Roadmap (MVP)

  1. status.py — the normalized editorial-status model (foundation)
  2. retractionwatch.py — ingest + normalize the Retraction Watch dump
  3. openalex.py — keyed, ID-first client
  4. checker.py — DOI / .bib → statuses
  5. mcp_server.py — expose the three tools
  6. evals/ — gold set + precision/recall harness (running from step 2 onward)

Credits & data

  • OpenAlex — CC0 scholarly metadata and citation graph.
  • Retraction Watch — retraction database, made openly available via Crossref.
  • Crossref — DOI infrastructure.

CiteGuard is independent and not affiliated with these projects; it builds on their open data with gratitude.

License

MIT (see LICENSE) — permissive and maximally reusable, in keeping with the open-science ethos in GOAL.md.

The code is CiteGuard's. The data it builds on is not and carries its own terms: Retraction Watch (via Crossref) and OpenAlex/Crossref metadata. CiteGuard redistributes only a tiny evaluation extract (see evals/fixtures/ATTRIBUTION.md); anything at scale should be fetched from the upstream sources under their licenses.

问 PopNx