MCP.Market

CiteGuard MCP server

by lonexreb·io.github.lonexreb/retractguard·v0.1.2

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

B78/100grade B
What users say
No reviews yet
Be the first
Safety scan
B78/100

full report

Adoption
New

0 stars21 downloads/wk

Reviews

Write one

Nobody has reviewed CiteGuard yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

CiteGuard tools (3)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • check_references

    Check a reference list. Provide exactly one of: `dois` (list of DOIs), `bibtex` (a .bib file's text), or `paper_doi` (a paper's DOI — its cited references are fetched from OpenAlex and checked).

  • get_editorial_status

    Editorial status of one work (retracted / corrected / expression of concern / reinstated / hijacked journal / none / unknown), with source, evidence URL, date, confidence, and any source conflicts.

  • watch_institution

    Scan an institution's works (by ROR ID, e.g. https://ror.org/02y3ad647) for papers that are flagged or that cite flagged papers. Repeat calls report only NEW flags (state kept locally). `since` is an optional YYYY-MM-DD publication-date floor — set it for large institutions.

Public scan report

scanner v0.1.9 · 2026-09-25 · same rubric, same numbers if you re-run it

no findings
  • Code scan19 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 71 days ago12/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 78/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How CiteGuard compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
78/100
higher than 57% of 48,255 servers
Tools
3
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
Downloads a week
21
more than 8% of 12,191 servers with a package

What its tools let an agent do: 3 read

Install CiteGuard in Claude Code, Cursor or VS Code

claude mcp add retractguard -- uvx retractguard
Add to Cursor

What the publisher says

From the CiteGuard repository's README, as published. We do not edit it. Read it on GitHub

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

status: retracted, corrected, expression of concern, hijacked-journal, or clean.

  • Check a reference list. Paste a DOI or upload a .bib file → get a per-reference

OpenAlex / Crossref), an evidence link, a date, and a confidence note. When sources disagree, CiteGuard surfaces the conflict instead of silently guessing.

  • Nuanced status, not a boolean. Every flag carries its source (Retraction Watch /

institution's works cites (or becomes) a newly-flagged paper.

  • Watch an institution. Point it at a ROR ID → get a digest when any of that

(checkreferences, geteditorialstatus, watchinstitution) for Claude, Cursor, and any MCP-compatible client.

  • Use it from an AI agent. An MCP server exposes the same logic as tools

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:

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

CiteGuard: common questions

Is CiteGuard MCP server safe?
Mostly: it is graded B (78/100). Read the CiteGuard safety report
How do I install CiteGuard?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does CiteGuard need an API key?
Yes. The registry entry asks for OPENALEX_API_KEY.
Is CiteGuard maintained?
The last commit was 111 days ago (2026-07-16). The latest release is v0.1.2.
How does CiteGuard compare with other MCP servers?
safety score 78/100 (higher than 57% of 48,255 servers); tools 3 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.