thoth

thoth

MCP server for agentic systematic literature reviews with citation verification. Enables AI assistants to list reviews, get drafts, retrieve citation audits, and manage discovered papers.

Category
访问服务器

README

<div align="center">

<img src="docs/assets/thoth-logo.svg" alt="Thoth — sacred ibis logo" width="120" height="120" />

Thoth

Agentic systematic literature reviews — with every citation checked against the source.

Named for Thoth, ancient Egypt's ibis-headed god of writing and scribes.

Live demo Public evals MCP Registry Tests App release Deploy cost License: MIT

Try the live demo · See a sample review · Public eval dashboard · Connect via MCP

<img src="docs/assets/media/showcase-walkthrough.gif" alt="Browsing a completed Thoth review — draft, critic score, and per-claim citation audit" width="760" />

</div>


What is Thoth?

Systematic literature reviews are slow to write — and when you ask an LLM to write one, it confidently invents citations and statistics that aren't in any paper.

Thoth does both halves and checks its own work. Give it a research question and it discovers relevant papers, reads them, drafts an evidence-grounded review — then runs a verification pass (cite_check) that compares every cited claim against the source paper and flags anything unsupported before you read the draft. The result is a review with a critic score, a citation-faithfulness percentage, and a per-claim audit you can trust.

It runs as a polished web app, a public eval dashboard, and an authenticated MCP server your AI assistant can call directly.

See it work

Claude.ai catches 6 fabricated citations in a real draft — using Thoth's audit:

<div align="center"> <img src="docs/assets/m5-mcp-demo.gif" alt="Claude.ai connected to Thoth via MCP, using get_citation_audit to identify 6 unsupported claims" width="760" /> </div>

Connected to Thoth via the official MCP Registry, Claude calls get_citation_audit on one deliberately-weak review (faithfulness 0.13 for that single review) and identifies all 6 unsupported claims — every one citing the same paper, with invented percentages that aren't in the source. This is cite_check doing its job: it's a single-review audit sample, not the golden-set aggregate (see /evals).

Every claim, scored against its source — the /showcase review (no login needed). The figures on this card (critic 4.2/5, faithfulness 75%, 8/8 citations checked, 2 unsupported) are this one review's scores — a worked example, not the aggregate:

<div align="center"> <img src="docs/assets/media/02-showcase.png" alt="A completed Thoth review: critic 4.2/5, citation faithfulness 75%, 8/8 citations checked with 2 unsupported — scores for this single sample review" width="760" /> </div>

Evaluated in public — /evals tracks citation recall / precision / faithfulness / coverage over an 18-question versioned golden set (7 of 18 populated at this commit), regenerated in CI and published with the last-run date, so a regression is a public, falsifiable signal:

<div align="center"> <img src="docs/assets/media/03-evals.png" alt="Thoth's public eval dashboard — citation recall, precision, faithfulness, and coverage per golden question" width="760" /> </div>

You approve every step — three human-in-the-loop gates (review plan → review discovered papers → approve included papers); nothing runs unattended:

<div align="center"> <img src="docs/assets/media/hitl-gates.gif" alt="Thoth's three human-in-the-loop approval gates: review plan, review discovered papers, approve included papers" width="760" /> </div>

Key features

  • 🔎 cite_check — verifiable citations. Every [paper_id] in the draft is scored against the cited paper and labelled supported / unsupported / unclear, so the LLM can't quietly hallucinate a citation. On the public golden set, the citations it does surface are accurate — citation precision 97%, recall 74% — and the verdict report is published per claim, not summarised away. This is the core differentiator: the citations are measured, not asserted.
  • 🌐 Outbound web search (v2 — under active evaluation). An outbound discoverer → fetcher → screener path is wired across OpenAlex, arXiv, and Exa: it fetches open-access PDFs, OCRs them, and screens each against your plan, so you can run uploaded-only, hybrid, or fully autonomous discovery. The discovery and screening axes are v2 and still being calibrated — they're tracked openly on /evals (both currently at 0%) rather than shipped as a silent claim.
  • 🔌 Authenticated, registered MCP server. OAuth 2.1 + PKCE + Dynamic Client Registration via Clerk, SHA-256 audit logging, rate limits — listed in the official MCP Registry. Most public MCP servers ship with no auth; this one doesn't.
  • 📊 Public eval dashboard. Recall / precision / faithfulness / coverage over a versioned golden set, regenerated in CI and stamped with the last-run date, rendered at /evals — an eval regression is a public signal, not a hidden one.
  • 💸 6 LLM providers, $0/mo by default. Swap providers with one env var; the Mistral free tier runs the whole thing, and the entire stack deploys on free tiers for $0/mo.

🚀 Quickstart

Try it now (nothing to install):

Connect it to your AI assistant — paste this into claude.ai (Pro/Max), Claude Desktop, Cursor, or any MCP client (OAuth runs in your browser; no token to copy):

https://thoth-slr.vercel.app/api/mcp/mcp

<details> <summary>Read-only MCP tools (scoped to your account)</summary>

  • list_reviews — your reviews with critic + faithfulness scores
  • get_review_draft — the markdown draft of a completed review
  • get_citation_audit — the per-claim cite_check verdict report
  • list_discovered_papers (v2) — papers the discoverer surfaced, with fetch + screening status
  • get_search_queries (v2) — the queries the discoverer generated + per-provider errors

Full reference: docs/mcp/tools.md · auth + audit model: docs/mcp/security.md </details>

<div align="center"> <img src="docs/assets/m5-mcp-setup.gif" alt="Adding Thoth as a custom MCP connector in claude.ai — paste the URL, OAuth via Clerk + Dynamic Client Registration" width="760" /> <br/><em>Adding Thoth as a custom connector in claude.ai — OAuth runs in your browser (Clerk + DCR), no token to copy.</em> </div>

Run it locally:

git clone https://github.com/ahmedEid1/thoth.git && cd thoth
cp .env.example .env        # Clerk + Trigger.dev keys + MISTRAL_API_KEY
docker compose up -d        # postgres, minio, langfuse
pnpm install && pnpm prisma migrate dev
pnpm dev                    # Next.js on :3000
pnpm dev:trigger            # Trigger.dev worker (separate terminal)

Full setup, the agent pipeline, and the v2 flow: docs/architecture.md.

Proof

Live app thoth-slr.vercel.app (Clerk sign-in) · sample review at /showcase
Public evals /evals — citation precision 97%, recall 74% on a versioned 18-question golden set (7 of 18 populated at this commit; faithfulness 38% / coverage 32% tracked in the open as the set fills out; discovery/screening v2 under calibration). Regenerated in CI, published with the last-run date — a regression is a public signal.
MCP Registry io.github.ahmedEid1/thoth — status: active
Tests 676 unit/integration + 22 live e2e against the deployed instance (MCP transport, real-browser, authenticated walkthroughs, full agent runs) — all green; tsc + lint clean
Audit log Every MCP call recorded with a SHA-256 input hash; no raw input stored
Deploy cost $0/mo — Vercel + Neon + Cloudflare R2 + Langfuse + Trigger.dev, all free tiers (self-host option)

For engineers

Thoth is a LangGraph StateGraph driven by a Trigger.dev worker, with durable human-in-the-loop gates, a per-run cost cap, and exactly-once gate delivery. Next.js 16

  • TypeScript (strict), Postgres + Prisma, Clerk auth (web + OAuth 2.1 for MCP), S3-compatible storage, Mistral OCR, Langfuse tracing.

Credits

Ibis icon by Delapouite under CC BY 3.0, via game-icons.net.

License

MIT © 2026 Ahmed Hobeishy

推荐服务器

Baidu Map

Baidu Map

百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。

官方
精选
JavaScript
Playwright MCP Server

Playwright MCP Server

一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。

官方
精选
TypeScript
Magic Component Platform (MCP)

Magic Component Platform (MCP)

一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。

官方
精选
本地
TypeScript
Audiense Insights MCP Server

Audiense Insights MCP Server

通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。

官方
精选
本地
TypeScript
VeyraX

VeyraX

一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。

官方
精选
本地
graphlit-mcp-server

graphlit-mcp-server

模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。

官方
精选
TypeScript
Kagi MCP Server

Kagi MCP Server

一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。

官方
精选
Python
e2b-mcp-server

e2b-mcp-server

使用 MCP 通过 e2b 运行代码。

官方
精选
Neon MCP Server

Neon MCP Server

用于与 Neon 管理 API 和数据库交互的 MCP 服务器

官方
精选
Exa MCP Server

Exa MCP Server

模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。

官方
精选