MCP.Market

Bibverify MCP server

by Hylouis233·io.github.Hylouis233/bibverify·v0.3.0·98 stars

Verify and repair BibTeX references with DOI-first MCP tools.

A92/100grade A
What users say
No reviews yet
Be the first
Safety scan
A92/100

full report

Adoption
Established

98 stars49 downloads/wk

Reviews

Write one

Nobody has reviewed Bibverify yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Bibverify tools (4, 1 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • doi_to_bibtex

    Fetch one DOI through Crossref and return a BibTeX entry.

  • explain_update_diffwrite action

    Compare two BibTeX-like entries and return field-level changes.

  • rank_lookup_sources

    Return the effective provider order for a reference.

  • verify_bib_file

    Verify the configured BibTeX file and return a structured summary.

Public scan report

scanner v0.1.10 · 2026-11-03 · same rubric, same numbers if you re-run it

no findings
  • Code scan38 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 6 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 92/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Bibverify compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
92/100
higher than 95% of 48,255 servers
Tools
4
the typical server has 7
Tools that change things
25%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
98
more than 95% of 28,688 servers
Downloads a week
49
more than 41% of 12,191 servers with a package

What its tools let an agent do: 3 read · 1 change

Install Bibverify in Claude Code, Cursor or VS Code

claude mcp add bibverify -- uvx bibverify
Add to Cursor

What the publisher says

From the Bibverify repository's README, as published. We do not edit it. Read it on GitHub

Bibverify

<!-- mcp-name: io.github.Hylouis233/bibverify -->

Verify bibliographic existence and metadata consistency without destructive edits.

Chinese · Install · Quick start · MCP · Development

Bibverify is a BibTeX metadata verification tool for researchers, editors, automation, and AI assistants. It starts with exact DOI, PMID, PMCID, or arXiv identifiers and then scores candidates from title, author, year, venue, and pagination evidence.

Bibverify evaluates whether a bibliographic record can be located in the queried sources and whether its metadata agrees. It does not prove that research findings are true, data is authentic, or a venue is reputable. A missing database record is not evidence that a reference is fabricated. By default, the source .bib file is never overwritten.

Highlights

  • Identifier-first lookup for DOI, PMID, PMCID, and arXiv IDs.
  • Crossref, OpenAlex, Semantic Scholar, PubMed, Europe PMC, CORE, DBLP, arXiv, bioRxiv, and more.
  • Explainable multi-signal matching across identifiers, title, authors, year, venue, and pages. A resolvable DOI with a materially different title becomes identifier_conflict instead of being hidden by title search.
  • Structured provider outcomes distinguish a genuine no-match from rate limiting, authentication, network, parsing, and provider failures.
  • Non-destructive merging preserves abstract, keywords, file, note, and custom fields that providers do not return; conflicting persistent identifiers are never overwritten automatically.
  • A shared connection pool with retries, exponential backoff, and Retry-After support for 429/5xx responses.
  • An expiring SQLite cache for successful GET responses; failures are never cached.
  • Cross-platform path, encoding, Unicode filename, UTF-8 BOM, and CRLF handling.
  • JSON output, stable exit codes, a Python API, and an MCP server built on the official SDK.
  • Atomic output writes and byte-preserving backups.

Requirements

  • Windows, macOS, or Linux
  • Network access to the enabled metadata APIs
  • Python 3.11–3.14 when using the Python distribution; npm, containers, and native packages bundle their runtime

GitHub Actions tests all three operating systems across all four supported Python versions.

Install

The current published release is v0.3.0. This branch prepares v0.4.0; commands marked v0.4.0 become usable only after their linked npm, GHCR, or GitHub Release artifact has been published.

Run without a permanent installation:

uvx bibverify --version

Starting with v0.4.0, Node.js users can use the zero-dependency npm launcher. It downloads the matching native release, verifies SHA256SUMS, and forwards every argument and exit code:

npx --yes @hylouis233/bibverify --version
pnpm dlx @hylouis233/bibverify --version
bunx --bun @hylouis233/bibverify --version

For a persistent CLI in an isolated Python environment, use uv tool or pipx:

uv tool install bibverify
pipx install bibverify

Inside a virtual environment, regular pip also works:

python -m pip install --upgrade bibverify

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Bibverify: common questions

Is Bibverify MCP server safe?
Yes, by our scan: it is graded A (92/100). Read the Bibverify safety report
How do I install Bibverify?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Bibverify need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Bibverify maintained?
The last commit was 6 days ago (2026-10-29). The latest release is v0.3.0.
How does Bibverify compare with other MCP servers?
safety score 92/100 (higher than 95% of 48,255 servers); tools 4 (the typical server has 7); tools that change things 25% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.