Skip to main content
Glama

graphrag-ts citation provenance

Server Details

Source-tiered retraction and citation judgments for DOIs; abstains when evidence is thin.

Ownership verified
Status
Healthy
Uptime
95.5% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
sadofriod/graphrag-ts
GitHub Stars
9
Server Listing
graphrag-ts MCP Server
ChatGPT
–
Claude
–

TDQS

A4.3/5.0

Scored across 3 tools

Disambiguation4/5

The three tools target distinct questions: status lookup (is it retracted?), propagation judgment (does it reach this citing paper?), and evidence audit (justify or challenge a verdict). Descriptions explicitly cross-reference each other (audit points to integrity_paper_status for one-line status; propagation says to use it after status). There is residual overlap between integrity_evidence_audit and retraction_propagation, since both weigh source tiers and expose evidence, but the audit/verdict split is well explained.

Naming Consistency4/5

All three names are snake_case and verb/noun-shaped with readable subjects. Two share an 'integrity_' prefix while the third uses 'retraction_', a minor deviation that arguably groups by domain concept (integrity of a paper vs. retraction propagation). Not a flaw that would confuse an agent.

Tool Count4/5

Three tools is minimal but well matched to a narrow query-and-judge service; each maps to a distinct question an agent would ask. It sits at the thin end of the ideal range, with no filler tools padding the surface.

Completeness3/5

The core lifecycle (identify paper, get retraction records, judge propagation, audit evidence) is covered with a sensible tiering model. However, discovery is a gap: lookup requires a known DOI or OpenAlex id, with no search-by-title/author, no batch lookup, and no way to enumerate citations of a paper to find candidates for the other tools.

Publisher details

Operator
Ashes Born Trade and Services Limited (Hong Kong SAR) · Publisher source
Operator website
https://ashesborn.cloud/
Vendor relationship
Independent
Privacy policy
Not provided
Trust center
Unknown
Restrictions
Not available

Available Tools

3 tools
integrity_evidence_auditAInspect

Audit the evidence behind a paper's retraction picture: every source record with its tier and URI, the dates involved, conflicts between sources (an official registry and an aggregator disagreeing, or a citation acknowledging a retraction the graph does not propagate) and the coverage gaps that bound the conclusion. Use it when you must justify or challenge a verdict; for a one-line status use integrity_paper_status. Returns: evidence records with source tiers and URIs, detected conflict flags with codes and details, and the coverage that limits how strong the conclusion can be. Paid: $0.10 per call (x402 on Base, POST /api/v1/judge); a keyed MCP session also unlocks it.

Inputs: doi, paper_id.

integrity_paper_statusAInspect

Look up one paper by DOI or OpenAlex id and return its identity (title, year, venue) plus every retraction record the graph holds for it, each with its source and source tier: A is an official registry, B an authoritative index, C an aggregator. Use it to check whether a paper is retracted and which sources assert it; use retraction_propagation to judge whether that retraction reaches a specific citing paper. Free in the public tier. Returns: paper identity and statuses[] with source, source_tier, is_retracted, retraction_date and source_uri; abstention_reason when the paper is not in the snapshot.

Inputs: doi, paper_id.

retraction_propagationAInspect

Judge whether a retraction propagates to a paper through its citation graph: retraction evidence is weighted by source tier, the citing context is checked for an acknowledgement, and the tool returns CONTESTED, SUPPORTED or ABSTAINED with the evidence path behind the verdict. Use it after integrity_paper_status when the question is "does this retraction reach this paper". It abstains instead of guessing when reference coverage is thin. Returns: verdict, confidence, the evidence path that produced it, and abstention details when the verdict is ABSTAINED. Paid: $0.02 per call (x402 on Base, POST /api/v1/judge); a keyed MCP session also unlocks it.

Inputs: doi, paper_id.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      C
      maintenance
      Checks whether a citation has been retracted, corrected, or flagged with an expression of concern by querying Crossref — including retractions that Crossref backfills from the Retraction Watch database, which publishers often never record in their own metadata. Lets an AI agent verify a DOI, or every DOI in a reference list, before using it in research or writing.
      2
      1
      MIT
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to verify bibliographic records and BibTeX metadata consistency by resolving DOI, PMID, PMCID, and arXiv identifiers and scoring candidates across multiple scholarly sources with explainable, multi-signal matching. It reports structured provider outcomes and metadata conflicts without destructively editing the source bibliography.
      -
    • F
      license
      Not graded
      quality
      D
      maintenance
      Fabrication-free, DOI-backed citations for AI content and agents, using openAlex public-domain data with resolvable DOIs. Includes an API and planned MCP server for agent-native citation retrieval.
      -
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables researchers and AI assistants to verify bibliographic existence and metadata consistency, resolve DOI, PMID, PMCID, and arXiv identifiers, and perform explainable multi-source matching without destructive edits.
      -
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.