πŸŽ“ Semantic Scholar MCP Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

What is Semantic Scholar MCP Server?

The Semantic Scholar MCP Server is a project that implements a Model Context Protocol (MCP) server for interacting with the Semantic Scholar API, allowing users to search for academic papers, retrieve details about papers and authors, and fetch citations and references.

How to use Semantic Scholar MCP Server?

To use the server, you need to install the required Python packages and run the server script. You can interact with the server using an MCP client to access various tools for searching and retrieving academic information.

Key features of Semantic Scholar MCP Server?

  • πŸ” Search for papers on Semantic Scholar
  • πŸ“„ Retrieve detailed information about specific papers
  • πŸ‘€ Get author details
  • πŸ”— Fetch citations and references for a paper

Use cases of Semantic Scholar MCP Server?

  1. Academic research and literature review
  2. Retrieving citation information for scholarly articles
  3. Accessing detailed author profiles and publication history

FAQ from Semantic Scholar MCP Server?

  • What programming language is used for the server?

The server is implemented in Python.

  • How can I install the server?

You can install it via Smithery or by cloning the repository and installing the required packages.

  • Is there any support for contributions?

Yes! Contributions are welcome, and you can submit a Pull Request.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
Python
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market β€” USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` β€” get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` β€” get calldata for the seller to submit a proof URI - `release_funds_quote` β€” get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` β€” replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` β€” generate a signed agent card with marketplace attestation - `agent_search` β€” tf-idf search over the live agent catalog - `agent_reputation` β€” server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` β€” live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` β€” contract semantics, lifecycle, call guides, failure modes - `events_subscribe` β€” SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

3 hours ago
Gpt Scrambler

2 days ago