Crossref Scholarly Data

io.github.Taru0208Published by GitHub account Taru0208v1.1.0Updated Oct 24, 2026

Search 150M+ academic works, journals, and funders via Crossref API.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingKnowledge & Memory

Overview

AI-generated overview

Lets an assistant search over 150 million scholarly works, journals, and funders through the Crossref API.

What you can do
This remote MCP server exposes the Crossref scholarly metadata service to an assistant. According to its description, it searches more than 150 million academic works, journals, and funders. It is hosted as a remote endpoint, so the assistant connects to it directly rather than running anything locally.
When to use it
Use it when you need to look up academic publications, journal records, or research funders while working in an assistant. It suits literature checks, citation lookups, and scholarly metadata questions.
Requirements
A remote MCP client that supports streamable HTTP, plus network access to the hosted endpoint. No packages, environment variables, headers, or authentication are declared.
Before you install
The server is a third-party hosted endpoint, so queries are sent to that operator and to the Crossref API. No credentials are declared, but avoid sending confidential or unpublished research details in queries.

Installation

In SourceWeft

  1. Open Crossref Scholarly Data in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Taru0208%2Fcrossref-mcp-server/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "crossref-scholarly-data": {
      "type": "http",
      "url": "https://aligned-kettledrum--crossref-mcp-server.apify.actor/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.1.0LatestSep 16, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.