io.github.lonexreb/retractguard
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CITEGUARD_MAILTO | Yes | Polite-pool contact email for OpenAlex API. | |
| OPENALEX_API_KEY | Yes | Your OpenAlex API key. | |
| CITEGUARD_DATA_DIR | No | Directory for downloading Retraction Watch dump and cached lookups. | ./data |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_editorial_statusA | 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. |
| check_referencesA | Check a reference list. Provide exactly one of: |
| watch_institutionA | 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). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool targets a distinct workflow: get_editorial_status checks a single work, check_references evaluates a reference list, and watch_institution scans an entire institution. There is no meaningful overlap between them.
All tool names follow a consistent verb_noun pattern (get_, check_, watch_), making the API predictable and easy to navigate.
With only 3 tools, the server is lean but focused. The count is slightly low for a broad domain, but each tool addresses a core need (single-work status, reference-list checking, institutional monitoring) without feeling trivial.
The toolset covers the primary workflows for retraction monitoring: checking a work, a reference list, and an institution's flagged/citing papers. Minor gaps exist (e.g., no direct search across all retracted works), but the core lifecycle is well represented.