Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Source-tiered retraction and citation judgments for DOIs; abstains when evidence is thin.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
AuthorizationValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.
Run this in your terminal
claude mcp add --transport http graphrag-ts https://mcp.ashesborn.cloud/mcp --header 'Authorization: Bearer {api_key}'Fill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"graphrag-ts": {
"url": "https://mcp.ashesborn.cloud/mcp",
"headers": {
"Authorization": "Bearer {api_key}"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"graphrag-ts": {
"type": "http",
"url": "https://mcp.ashesborn.cloud/mcp",
"headers": {
"Authorization": "Bearer {api_key}"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.
Your choice stays on this device in a cookie; no account needed.
Authorization secret HTTP headerThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Tool names and descriptions exactly as the server reported them on Nov 6, 2026. The maker wrote them, not us; we show them as plain text.
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 an official registry, B an authoritative index, C an aggregator. Use it to check whether a paper is
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, and the tool returns CONTESTED, SUPPORTED or ABSTAINED with the evidence path behind the verdict. Use
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 aggregator disagreeing, or a citation acknowledging a retraction the graph does not propagate) and the cov
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account sadofriod, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Responded in 1137 ms (HTTP 200)
No sign-in needed
Read 3 tool descriptions and found no hidden instructions to the AI
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: Authorization
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (0.1.25) reached the registry 3 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Spec Driven Development, Remote Desktop Commander, Systemdox
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Your architecture in your agents' context: checks, specs, ADRs and docs over MCP, at write time.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Attribution is stored at write time, not asserted at read time.
graphrag-ts is a GraphRAG engine in TypeScript. It builds the knowledge graph in PostgreSQL, keeps source evidence on every node and edge, and answers with retrievable citations — or returns an explicit abstention when the coverage behind an answer is too thin to support it.
Benchmarks / 基准报告
English report · 中文报告
Hosted endpoint / 托管端点
https://mcp.ashesborn.cloud/mcp(anonymous tier: freeintegrity_paper_status, the two judgments answer with an x402 payment requirement; a keyed session unlocks them) · free DOI status:https://pay.ashesborn.cloud/api/v1/judge/paper?doi=· x402 wire format
No install, no API key, no model endpoint. Two ways in:
curl -s 'https://pay.ashesborn.cloud/api/v1/judge/paper?doi=10.1016/S0140-6736(97)11096-0'
The response is the paper plus every retraction record behind it, each with its source_tier and source_uri — the evidence the graph stores, not a model's recollection of it.
Point any Streamable HTTP MCP client at the hosted endpoint (public read tier, 20 requests/minute per IP):
{
"mcpServers": { "graphrag-ts": { "url": "https://mcp.ashesborn.cloud/mcp" } } }
A bearer API key unlocks the full tool set (graph queries, index jobs, memory writes). The two judgment tools also answer per call without a key via x402 payment ($0.02 / $0.10).
| Tool | Access | What it does |
|---|---|---|
query_graph | keyed | Local hybrid retrieval against the latest published snapshot in a workspace |
query_graph_global | keyed | Corpus-wide Map-Reduce retrieval over community summaries |
submit_index_job | keyed | Queue Markdown from the configured input directory for indexing |
remember_text | keyed | Queue user-provided text explicitly; never reads chat history |
get_index_job | keyed | Status and safe error summary for an index job |
integrity_paper_status | public | Retraction status and identity for a paper |
retraction_propagation | public / x402 | Judge whether retraction evidence propagates to a paper |
integrity_evidence_audit | public / x402 | Audit the evidence path, source tiers and conflicts for a paper |
The Compose stack starts PostgreSQL/pgvector and the MCP service. You must provide reachable chat and embedding endpoints; see the MCP guide for configuration, client setup, and workspace behavior.
cp .env.example .env
docker compose up -d --build curl http://127.0.0.1:3000/healthz
Connect an MCP client to http://127.0.0.1:3000/mcp. For the optional local browser showcase, configure the models and run docker compose --profile showcase up -d --build --wait, then open http://127.0.0.1:8080. The showcase is a local demo, not an authentication layer; do not expose it to untrusted users.
pnpm install
pnpm run db:generate cp .env.example .env
pnpm run db:push bun run examples/demo.ts
The library requires Bun, PostgreSQL with pgvector, and compatible chat and embedding endpoints. See the English guide or 中文指南 for environment setup, API examples, adapters, and tuning.
See the architecture guide for the pipeline and module details.
The reported in-corpus run reached 10/12 strict hits and 95.8% combined lexical recall on 12 questions from five indexed chapters. This is a small project benchmark, not human semantic grading or a cross-project comparison. The reports include methodology, per-query results, and limitations.
The English and Chinese reports are linked at the top of this page. To run the three-question Docker smoke benchmark, use pnpm benchmark:docker:quick with the model endpoints configured and loaded. See the MCP guide for prerequisites and the report for benchmark scope.
io.github.sadofriod/graphrag-tsContributions are welcome through issues and pull requests. The project is organized around small, testable modules, so the most useful changes usually fit into one of these areas:
MIT