Core Mcp

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

Academic search from CORE. No key required.

The publisher's own server: core.blue

VerifiedSTDIODesktop onlyWeb Search & Scraping

Overview

AI-generated overview

A local MCP server that gives an assistant academic search over CORE, the open-access research literature aggregator, without requiring an API key.

What you can do
Search CORE for academic papers and open-access research literature and return matching results to the assistant. The manifest lists no individual tools, so the exact search and retrieval operations are not documented here. It runs as a local process on the user's machine over stdio.
When to use it
Useful when you want an assistant to look up scholarly papers or open-access research on a topic and no API key setup is wanted. Less relevant if you need documented tool-level control or sources other than CORE.
Requirements
Runs as a local process over stdio, installed from the npm package @mrfentmen/core-mcp, so Node.js and npm are needed. No API key, environment variables or headers are declared. Desktop only; not executable in a web context. Network access to CORE is implied by the search function.
Before you install
The README and tool list are absent, so what is sent to CORE and how results are handled cannot be verified. Search queries leave your machine to a third-party service. No credentials are declared, but confirm the package source before installing.

Installation

In SourceWeft

  1. Open Core 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.

Other Core integrations