Skip to main content
Glama
ebiyu

crossref-mcp

by ebiyu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to crossref-mcp

No user-submitted related servers found.

    Related Servers

    • mcp-crossref

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables searching academic papers, journals, and citations via the Crossref API, and resolving DOIs to canonical metadata with authors, references, and citation graphs.
      283 npm
      MIT

    • crossref-mcp

      dam2452
      F
      license
      A
      quality
      B
      maintenance
      Enables searching and retrieving scholarly metadata from Crossref's public REST API, including works, journals, funders, and members, without requiring an API key.
      10
      1
      -

    • Crossref MCP Server

      JackKuo666
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to search academic literature and retrieve detailed metadata for papers, journals, and funding organizations via the Crossref database. It supports DOI-based lookups and keyword searches to facilitate programmatic access to scholarly research data.
      7
      -

    • crossref-mcp

      jtl-neo
      A
      license
      A
      quality
      C
      maintenance
      Enables scholarly metadata lookups from the Crossref REST API, including works, members, journals, funders, types, licenses, and prefixes, as tools for LLM clients.
      18
      36 PyPI
      MIT

    • genpark-canonical-doi-bibtex

      alphaparkinc
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables resolving academic DOIs to canonical identifiers and generating BibTeX records via CrossRef, and can be integrated into MCP-compliant clients for automated research workflows.
      8
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.4/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools are clearly distinct: one retrieves a specific work by DOI, the other searches for works using query parameters. There is no overlap in their purposes, making it easy for an agent to select the appropriate tool.

    Naming Consistency5/5

    Both tools follow a consistent verb_noun pattern: 'get_work_by_doi' and 'search_works'. The naming clearly indicates the action and the resource, and there is no mixing of conventions.

    Tool Count3/5

    With only two tools, the server feels thin for a general Crossref API, but for the narrow purpose of retrieving works by identifier or search, it is minimally sufficient. The count is at the low end of what is reasonable.

    Completeness4/5

    The core workflows of looking up a work by DOI and searching for works are covered. Minor gaps exist, such as no support for other identifiers or listing all works of an author directly, but the primary use cases are addressed.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources