bib-enrich-mcp
Related Servers
Alternatives to bib-enrich-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables AI assistants to verify BibTeX citations and URLs against academic databases like Semantic Scholar and DBLP. It allows users to ensure bibliography accuracy and link accessibility directly within their research workflows.1MIT
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants to verify BibTeX records against multiple bibliographic sources, resolve DOI/PMID/PMCID/arXiv identifiers, and inspect explainable metadata matches without destructive edits.-
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants to verify bibliographic existence and metadata consistency, convert DOI/PMID/PMCID/arXiv identifiers to BibTeX, and check .bib files against multiple sources without destructive edits.-
- AlicenseAqualityCmaintenanceEnables AI agents and LLM tools to verify academic citations against real literature, detect hallucinated references, retrieve authoritative metadata and DOIs, generate BibTeX/APA/IEEE citations, and search over 200M+ scientific publications via MCP tools.317 npmMIT
- AlicenseNot gradedqualityAmaintenanceA multi-platform BibTeX reference verification and update tool with DOI-first lookup, dynamic source ranking, MCP tools, and skill export for AI assistants.38 PyPI98MIT
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants to verify bibliographic records and BibTeX metadata consistency by resolving DOI, PMID, PMCID, and arXiv identifiers and scoring candidates across multiple scholarly sources with explainable, multi-signal matching. It reports structured provider outcomes and metadata conflicts without destructively editing the source bibliography.-
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one enriches a single bibliography entry by accepting specific identifiers, while the other enriches all entries in a BibTeX file. No overlap in functionality.
Both tools follow a consistent naming pattern with the prefix 'mcp_enrich_bib_' followed by a specific suffix ('entry' and 'file'). The naming is uniform and predictable.
The server has only 2 tools, which is on the low end. For a focused enrichment task, this may be acceptable, but it feels slightly under-scoped compared to typical MCP servers that often offer 3-15 tools.
The server covers the core enrichment functionality but lacks additional tools for operations like searching for entries, validating BibTeX, or undoing enrichments. The surface is minimal and may leave agents with dead ends.