MCP Refchecker MCP Server

Returns JSON: ```json { "verified": true, "url": "https://...", "matched_paper": { "title": "...", "authors": [...], "year": 2023, "venue": "..." }

Local serverstdio

What is the MCP Refchecker MCP server?

Most developer tooling work still happens through a UI a human drives. MCP Refchecker MCP server moves it into the conversation instead. Returns JSON: json { "verified": true, "url": "https://...", "matched_paper": { "title": "...", "authors": [...], "year": 2023, "venue": "..." }, "possible_match": null, "errors": null, "warnings": null, "info": null } .

Getting it running

Installation goes through your MCP client rather than a global install: point it at mcp-refchecker on PyPI and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

The tools it exposes

The server publishes 6 tools. What each one is for:

  • title — string
  • authors — string[]
  • year — integer
  • doi — string
  • arxiv_id — string
  • url — string

What it needs from you

Configuration is passed through the environment: SEMANTIC_SCHOLAR_API_KEY, CROSSREF_MAILTO. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Things to watch

  • 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.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

How it compares

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. MCP Refchecker's toolset — title, authors, year and 3 more — is a fair guide to whether it matches your workflow. It is maintained by jonasbaath; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against MCP Refchecker's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Available tools

ToolWhat it does
titlestring
authorsstring[]
yearinteger
doistring
arxiv_idstring
urlstring

How to install the MCP Refchecker MCP server

{
  "mcpServers": {
    "refchecker": {
      "command": "uvx",
      "args": ["mcp-refchecker"]
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
SEMANTIC_SCHOLAR_API_KEYCredential the server authenticates with.Yes
CROSSREF_MAILTOConfiguration value read at startup.Optional

Example prompts to try

  • Use MCP Refchecker to title.
  • Use MCP Refchecker to authors.
  • Use MCP Refchecker to year.

Frequently asked questions

It connects MCP Refchecker to MCP-compatible AI assistants such as Claude and Cursor, exposing 6 tools (title, authors, year, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with MCP Refchecker directly.