Figshare Mcp

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

Search research articles and datasets on Figshare. No key required.

VerifiedSTDIODesktop onlyWeb Search & ScrapingKnowledge & Memory

Overview

AI-generated overview

Lets an assistant search Figshare for research articles and datasets, with no API key required.

What you can do
This MCP server exposes Figshare, a public research data repository, to an assistant. According to its registry description, it lets the assistant search research articles and datasets on Figshare. No further tools are documented in the supplied material.
When to use it
Worth adding when an assistant needs to look up scholarly articles or research datasets hosted on Figshare, for example during literature or data discovery. It is not intended for general web search or for repositories other than Figshare.
Requirements
Runs as a local process on the user's machine over stdio, installed from the npm package figshare-mcp, so a Node.js runtime is needed. The description states no key is required, and no environment variables or headers are declared. Network access to Figshare is implied by the search capability.
Before you install
The supplied material declares no credentials, no environment variables and no headers, and describes only searching public content. No write, send or delete actions are documented. Because the README is unavailable, the exact tools and any data sent to Figshare cannot be verified from this input.

Installation

In SourceWeft

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