Semantic Scholar Mcp

io.github.mrfentmenPublished by GitHub account mrfentmenv1.0.0Updated Oct 25, 2026

Search academic papers and read citations from Semantic Scholar. No key required.

VerifiedSTDIODesktop onlyWeb Search & Scraping

Overview

AI-generated overview

A local MCP server that lets an assistant search academic papers and read citation information from Semantic Scholar, with no API key required.

What you can do
Search Semantic Scholar for academic papers by topic or query and return matching results to the assistant. Retrieve citation information for papers so the assistant can trace which works cite or are cited by a given paper. No API key is needed, so the assistant can query the service directly once the server is running.
When to use it
Useful when you want an assistant to look up scholarly literature, find papers on a research topic, or follow citation links between works during research or writing tasks.
Requirements
Runs as a local process on the user's machine, installed from the npm package semantic-scholar-mcp over stdio, so Node.js and npm are needed. No API key, environment variables or headers are declared. Network access to Semantic Scholar is required. Desktop only; not available as a web executable.
Before you install
Queries and paper lookups are sent to Semantic Scholar, a third-party service, so research topics become visible to that provider. No credentials are requested, but the server is read-only in scope and does not appear to write or change data.

Installation

In SourceWeft

  1. Open Semantic Scholar Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.0LatestSep 22, 2026

Score

25% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • 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.