paperscraper-MCP-Server

Created By
JackKuo666a year ago
A MCP Server for paperscraper:Tools to scrape publication metadata from pubmed, arxiv, medrxiv, biorxiv and chemrxiv.
Overview

what is paperscraper-MCP-Server?

paperscraper-MCP-Server is a tool designed to scrape publication metadata from various scientific repositories including PubMed, arXiv, medRxiv, bioRxiv, and chemRxiv.

how to use paperscraper-MCP-Server?

To use paperscraper-MCP-Server, set up the server and utilize its API to request metadata for specific publications by providing the relevant identifiers or search queries.

key features of paperscraper-MCP-Server?

  • Scrapes metadata from multiple scientific databases
  • Supports various publication types and formats
  • Easy integration with other research tools and workflows

use cases of paperscraper-MCP-Server?

  1. Collecting publication data for systematic reviews
  2. Automating the extraction of citation information for research papers
  3. Enhancing bibliographic databases with up-to-date metadata

FAQ from paperscraper-MCP-Server?

  • What databases does paperscraper-MCP-Server support?

It supports PubMed, arXiv, medRxiv, bioRxiv, and chemRxiv.

  • Is there a limit to the number of requests I can make?

The server may have rate limits depending on the configuration and usage policies.

  • Can I customize the metadata fields I want to scrape?

Yes, you can specify which metadata fields to retrieve based on your needs.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
JackKuo666
Star
0
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
Crevio

2 days ago