S
Synectic-Research/research-scan
Research Scan finds and ranks recent scientific papers that matter most for a specific research question,…
在 GitHub 查看 ↗链接已于 2026-11-12 核查 · HTTP 200 · 打开的是厂商自己的官网
安装与配置
客户端配置(取自该仓库的安装命令)
{
"mcpServers": {
"synectic-research-research-scan": {
"command": "uvx",
"args": ["research-scan"]
}
}
}解析自我们于 2026-11-02 抓取的该仓库 README;我们未执行过。
command/args 来自仓库写明的安装命令;不确定时请以该项目 README 为准。
VS Code(.vscode/mcp.json —— 键名是 servers)
{
"servers": {
"synectic-research-research-scan": {
"command": "uvx",
"args": ["research-scan"]
}
}
}VS Code 顶层键是 <code>servers</code>,其余与上面那份相同。
Claude Code(命令行)
claude mcp add --transport stdio synectic-research-research-scan -- uvx research-scan
Claude Code 不收 JSON 文件,用这条命令直接加。
配置项的键名以你的客户端为准:客户端与 CLI
- ★ 数取值
- 1 ★ · Synectic-Research/research-scan · 取自 GitHub 搜索 API · (2026-11-13 20:00:50 核对)
- 来源明细
- 从该仓库的 GitHub 页面直接读取 · 条目类型:开源项目
- 收录与活跃
- 收录于 2026-11-03 · 最近见到 2026-11-14 · 共见到 12 次 · 被 1 个来源列出
- 评分构成
- 综合分 103 · 1 ★ · 1 个来源 · repo
- 安装
uvx research-scan
常见问题(答案都来自我们的记录)
怎么安装?
该仓库给出的安装命令是
uvx research-scan。我们的记录里它是仓库自己提供的;不保证在你的客户端上直接可用。它适合谁 / 用来做什么?
我们把它归在这些标签下: Agent 技能。标签来自条目自身,不是我们强加的分类。
谁维护它、还在更新吗?
仓库
Synectic-Research/research-scan;我们收录于 2026-11-03;最近见到 2026-11-14。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。# research-scan
以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →
Research Scan finds and ranks recent scientific papers that matter most for a specific research
question, project, or decision. Starting from a brief or a single question, it retrieves the
literature, expands through citation graphs, measures coverage, verifies every DOI against the live
record, and emits evidence objects — while the agent driving it plans the queries, screens the
candidates and ranks the shortlist. It is an evidence pipeline for a reasoning agent, not an
assistant that answers questions.
Documentation:
The work is split in two, deliberately.
The CLI is deterministic and model-free. It retrieves across OpenAlex, Semantic Scholar and
arXiv, walks the citation graph, dedups, counts coverage per criterion, shortlists, verifies every
DOI against the live record, applies the selection rules and renders the result. It contains no LLM
SDK and makes no judgement about a paper.
The agent supplies the cognition. Planning the queries, scoring each candidate 0–3, writing gap
queries when coverage is thin, and reranking the shortlist are all model decisions. The skill
packages the rubrics they are made against, as plain Markdown in skills/research-scan/references/;
whatever agent hosts it executes them.
Files are the interface between the two halves: the filesystem is the protocol boundary between
reasoning and execution, not a storage detail. That is what lets Claude Code, Codex, Cursor or a
plain Python loop drive the same chain over the same artifacts.
brief ─▶ [plan queries] ─▶ retrieve ─▶ [screen 0–3] ─▶ expand ─▶ [screen] ─▶ coverage
─▶ [gap round, if coverage is thin] ─▶ shortlist ─▶ [rerank] ─▶ verify ─▶ emit
Bracketed steps are the agent's; the rest are CLI stages.
Two things bound the result. A purpose — build, research or orient — decides what a paper
has to do to earn a slot. A profile — quick, standard or deep — decides how much the scan
costs. Both are described under How it works.
Output is a run directory of validated JSON plus a Markdown brief you can hand to a human, in which
every paper's DOI, title, year and first author were checked against the live record.
## Install
Python ≥ 3.11 and uv.
bash
uvx research-scan doctor # run any command without installing
uv tool install research-scan # or put it on PATH permanently
## Configure
configure asks for each credential, shows what is already set, writes
~/.config/research-scan/.env with mode 0600 inside a 0700 directory, and finishes by running
doctor.
bash
research-scan configure # setup is an alias for the same command
Keys are read without echo. Re-running is safe: every variable shows its current value masked to the
last four characters, Enter keeps it, typing replaces it. Anything already in the file that
configure does not ask about — comments included — is left exactly as it was. If stdin is not a
terminal it prints the file to write and exits 2 rather than hanging, which is the behaviour you
want in a Dockerfile or a provisioning script.
| Variable | Needed for |
| OPENALEXAPIKEY | OpenAlex, the primary source. Required; doctor exits 3 without it. |
| OPENALEXMAILTO | Strongly recommended. Raises OpenAlex to 5 req/s and joins the Crossref polite pool. |
question, project, or decision. Starting from a brief or a single question, it retrieves the
literature, expands through citation graphs, measures coverage, verifies every DOI against the live
record, and emits evidence objects — while the agent driving it plans the queries, screens the
candidates and ranks the shortlist. It is an evidence pipeline for a reasoning agent, not an
assistant that answers questions.
Documentation:
The work is split in two, deliberately.
The CLI is deterministic and model-free. It retrieves across OpenAlex, Semantic Scholar and
arXiv, walks the citation graph, dedups, counts coverage per criterion, shortlists, verifies every
DOI against the live record, applies the selection rules and renders the result. It contains no LLM
SDK and makes no judgement about a paper.
The agent supplies the cognition. Planning the queries, scoring each candidate 0–3, writing gap
queries when coverage is thin, and reranking the shortlist are all model decisions. The skill
packages the rubrics they are made against, as plain Markdown in skills/research-scan/references/;
whatever agent hosts it executes them.
Files are the interface between the two halves: the filesystem is the protocol boundary between
reasoning and execution, not a storage detail. That is what lets Claude Code, Codex, Cursor or a
plain Python loop drive the same chain over the same artifacts.
brief ─▶ [plan queries] ─▶ retrieve ─▶ [screen 0–3] ─▶ expand ─▶ [screen] ─▶ coverage
─▶ [gap round, if coverage is thin] ─▶ shortlist ─▶ [rerank] ─▶ verify ─▶ emit
Bracketed steps are the agent's; the rest are CLI stages.
Two things bound the result. A purpose — build, research or orient — decides what a paper
has to do to earn a slot. A profile — quick, standard or deep — decides how much the scan
costs. Both are described under How it works.
Output is a run directory of validated JSON plus a Markdown brief you can hand to a human, in which
every paper's DOI, title, year and first author were checked against the live record.
## Install
Python ≥ 3.11 and uv.
bash
uvx research-scan doctor # run any command without installing
uv tool install research-scan # or put it on PATH permanently
## Configure
configure asks for each credential, shows what is already set, writes
~/.config/research-scan/.env with mode 0600 inside a 0700 directory, and finishes by running
doctor.
bash
research-scan configure # setup is an alias for the same command
Keys are read without echo. Re-running is safe: every variable shows its current value masked to the
last four characters, Enter keeps it, typing replaces it. Anything already in the file that
configure does not ask about — comments included — is left exactly as it was. If stdin is not a
terminal it prints the file to write and exits 2 rather than hanging, which is the behaviour you
want in a Dockerfile or a provisioning script.
| Variable | Needed for |
| OPENALEXAPIKEY | OpenAlex, the primary source. Required; doctor exits 3 without it. |
| OPENALEXMAILTO | Strongly recommended. Raises OpenAlex to 5 req/s and joins the Crossref polite pool. |
收录徽章(可选)
想把收录标记放进 README 就复制这行,可选,不影响收录。
[](https://anclum.com/zh/s/synectic-research-research-scan/)
- 来源
- github · https://github.com/Synectic-Research/research-scan
- 按领域浏览
- Agent 技能
- Traction
- 1 ★
- 收录于
- 今天
同类推荐
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。