Thoth MCP Server

Read-only MCP over an agentic SLR workspace with per-claim citation verification. Exposed over MCP by the thoth mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

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.

• 🔎 cite_check — verifiable citations. — Every [paper_id] in the draft is
• 🌐 Outbound web search (v2 — under active evaluation). — An outbound
• 🔌 Authenticated, registered MCP server. — OAuth 2.1 + PKCE + Dynamic Client
• 📊 Public eval dashboard. — Recall / precision / faithfulness / coverage over a
• 💸 6 LLM providers, $0/mo by default. — Swap providers with one env var; the Mistral

Its toolset

Everything the assistant can do here goes through one of these:

• 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
• Tests — 676 unit/integration + 22 live e2e against the deployed instance (MCP transport, real-browser, authenticated walkthroughs, full agent runs) — all

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Configuration

You will need one environment variable: MISTRAL_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

When to reach for it

Plenty of browser automation servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Thoth's toolset — list_reviews, get_review_draft, get_citation_audit and 1 more — is a fair guide to whether it matches your workflow. It is maintained by ahmedEid1; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the thoth mcp server does with a few real requests.