Skip to content

graphrag-ts citation provenance MCP server

io.github.sadofriod/graphrag-tssadofriodstreamable-httpv0.1.25Scanned

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

3 tools: 2 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 2 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Sign-in required, OAuth metadata published. Remote posture

Anlyon alternative

2 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the graphrag-ts citation provenance MCP server can do

The graphrag-ts citation provenance MCP server is published by the GitHub account sadofriod. It has 3 tools. It can create or change data (2 tools: retraction_propagation and integrity_evidence_audit), but cannot delete data. 1 tool only reads.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 17, 2026, version 0.1.25.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

3 tools

Changes things 2Claude Code: ask
  • integrity_evidence_auditAudit 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 aggreg…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • retraction_propagationJudge 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, a…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
Only reads 1Show 1 read-only tool
  • integrity_paper_statusLook 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…No findings

    Why it is in this group

    • The name "integrity_paper_status" says "status": a word for reading.
    Description, as the server wrote it
    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.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Sign-in required, OAuth metadata published

Looked at Nov 19, 2026, 17:24 UTC, unchanged since Nov 19, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://mcp.ashesborn.cloud/.well-known/oauth-protected-resource/mcp
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: The operation was aborted due to timeout

Posture changes

  1. Nov 19, 2026
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 2 to 0
    • Protocol version: 2025-06-18 to none

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 2 -> 0; Protocol version: 2025-06-18 -> none.View diff
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 2 to 0
    • Protocol version: 2025-06-18 to none
  2. Tools3 changed.~3 changedView diff

Install

Pinned to version 0.1.25. Values in angle brackets are yours to fill in.

claude mcp add --transport http graphrag-ts https://mcp.ashesborn.cloud/mcp
claude mcp add --transport http graphrag-ts https://mcp.ashesborn.cloud/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__graphrag-ts__integrity_paper_status"
    ],
    "ask": [
      "mcp__graphrag-ts__retraction_propagation",
      "mcp__graphrag-ts__integrity_evidence_audit"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as graphrag-ts. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.sadofriod/graphrag-ts/verify?hash=bc5ef94da7b1d9cb1c33988a1c6293b0129a0a8a1898e4d5e5bf40cad35056b7" | jq -e '.changed == false'

Pinned hash bc5ef94da7b1, from Nov 17, 2026, 10:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.sadofriod/graphrag-ts/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.sadofriod/graphrag-ts
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.sadofriod/graphrag-ts.svg)](https://radar.anlyon.com/servers/io.github.sadofriod/graphrag-ts)

Source: MCP Registry · repository. Synced Nov 3, 2026, 20:18 UTC.

graphrag-ts citation provenance MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the graphrag-ts citation provenance MCP server safe?

No scan can promise that. What its definitions show: 3 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the graphrag-ts citation provenance MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the graphrag-ts citation provenance MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the graphrag-ts citation provenance MCP server have?

3 tools: 2 write, 1 read. retraction_propagation, integrity_evidence_audit and integrity_paper_status.

Does the graphrag-ts citation provenance MCP server need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the graphrag-ts citation provenance MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the graphrag-ts citation provenance MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 3, 2026. Every change is on this page and in its Atom feed.