Papers

Scholarly paper search with real citations for AI assistants, over MCP.

我該用這個嗎

品質與安全性

A
說明品質
100%
結構描述完整度
88%
命名品質
100%
汙染風險
100%
權限相符程度
100%
協定合規性
100%

根據工具定義與協定合規性的自動化分析。

上下文成本

~948Token(工具定義)
~1.6 KB典型回應大小
中等的注意力影響(128k 上下文的 0.74%)

這是每次將伺服器的工具載入模型上下文時所消耗的約略 token 數量。數量越高,可用於其他工作的注意力就越少。

安裝

一鍵安裝

將以下內容加入你的 `claude_desktop_config.json` 檔案:

{
  "mcpServers": {
    "papers": {
      "url": "https://papers-mcp.vercel.app/mcp"
    }
  }
}

遠端端點

https://papers-mcp.vercel.app/mcpstreamable-http

它能做什麼

工具清單

工具(4)

🟢 唯讀🟡 寫入🔴 刪除⚪ 未知
🟢search_papers(query, year_from, year_to, field, open_access, ...)

Search peer-reviewed and preprint records by question or keywords. Filters: year_from, year_to, field, open_access, and source (openalex, semantic_scholar, pubmed, crossref, arxiv, or all). Returns only works those APIs returned, each with a source link and an identifier. An empty list means the APIs returned nothing. Do not invent papers to fill a gap.

輸入結構描述

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "minLength": 2,
      "maxLength": 400,
      "description": "Question or keywords"
    },
    "year_from": {
      "type": "integer",
      "minimum": 1800,
      "maximum": 2100
    },
    "year_to": {
      "type": "integer",
      "minimum": 1800,
      "maximum": 2100
    },
    "field": {
      "type": "string",
      "minLength": 2,
      "maxLength": 80,
      "description": "Subject area, such as Medicine or Computer Science"
    },
    "open_access": {
      "type": "boolean"
    },
    "source": {
      "type": "string",
      "enum": [
        "openalex",
        "semantic_scholar",
        "pubmed",
        "crossref",
        "arxiv",
        "all"
      ],
      "description": "Index to search. Defaults to all, which mixes sources."
    },
    "limit": {
      "type": "integer",
      "minimum": 1,
      "maximum": 20,
      "description": "Maximum papers to return. Defaults to 8."
    }
  },
  "required": [
    "query"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

輸出結構描述

{
  "type": "object",
  "properties": {
    "data": {}
  },
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢get_paper(identifier)

Fetch one paper's title, authors, year, venue, and abstract by DOI, PMID, arXiv id, or OpenAlex work id. Metadata comes from the API that resolved the identifier. If no source returns a record, say so. Do not guess the abstract.

輸入結構描述

{
  "type": "object",
  "properties": {
    "identifier": {
      "type": "string",
      "minLength": 2,
      "maxLength": 300,
      "description": "DOI, PMID, arXiv id, or OpenAlex work id"
    }
  },
  "required": [
    "identifier"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

輸出結構描述

{
  "type": "object",
  "properties": {
    "data": {}
  },
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢find_related_papers(identifier, relation, limit)

List papers that cite a work (relation cited_by) or papers that work cites (relation references). Every row is an API hit. An empty list means the API returned none, not that none exist.

輸入結構描述

{
  "type": "object",
  "properties": {
    "identifier": {
      "type": "string",
      "minLength": 2,
      "maxLength": 300
    },
    "relation": {
      "type": "string",
      "enum": [
        "cited_by",
        "references"
      ]
    },
    "limit": {
      "type": "integer",
      "minimum": 1,
      "maximum": 20
    }
  },
  "required": [
    "identifier",
    "relation"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

輸出結構描述

{
  "type": "object",
  "properties": {
    "data": {}
  },
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢format_citation(identifier, style)

Format a real paper in APA, MLA, Chicago author-date, or BibTeX using metadata fetched for the identifier. Titles are kept as the source provided them. Author particles may need a human check because display names are split mechanically. If the paper cannot be resolved, do not hand-write a citation.

輸入結構描述

{
  "type": "object",
  "properties": {
    "identifier": {
      "type": "string",
      "minLength": 2,
      "maxLength": 300
    },
    "style": {
      "type": "string",
      "enum": [
        "apa",
        "mla",
        "chicago",
        "bibtex"
      ]
    }
  },
  "required": [
    "identifier",
    "style"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

輸出結構描述

{
  "type": "object",
  "properties": {
    "data": {}
  },
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

社群

為此伺服器評分

證據

近期觀測

已驗證未記錄版本4 個工具