timesfm
TimesFM (Time Series Foundation Model) is a pretrained time-series foundation model developed by Google Research for time-series forecasting.
MCP server for academic papers, citations, authors, ECOS dossiers, and Federal Register text.
作者提供的原文
教 AI 做这类工作的 Skill,可与本项一起使用
TimesFM (Time Series Foundation Model) is a pretrained time-series foundation model developed by Google Research for time-series forecasting.
Open-source intelligence for the global theater. Track everything from the corporate/private jets of the wealthy, and spy satellites, to seismic events in one unified interface. Hook an AI agent up to have it parse through data and find previously unseen correlations. The knowledge is available to…
scrape data from Google Maps. Extracts data such as the name, address, phone number, website URL, rating, reviews number, latitude and longitude, reviews,email and more for each place
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 0/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 3/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 0/8 | 上次检查时云端端点有响应 |
| 使用分 | 3/100 |
质量: 基础检查通过 3/3 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 Paper Chaser MCP。按照 https://mcp.popnx.com/i/joshuasundance-swca-paper-chaser-mcp.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 3/3 项检查 · 在你的电脑上运行 · ✓ 命令已检查 2026年11月14日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude,但需要先准备
需要先在电脑上安装 Docker(只需一次) · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
把这段话复制到 Claude 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Claude 安装 MCP server Paper Chaser MCP,按顺序:1) 用 docker --version 检查是否有 Docker。没有的话,请让我从 https://www.docker.com/products/docker-desktop/ 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "paper-chaser": { "command": "docker", "args": [ "run", "-i", "--rm", "ghcr.io/joshuasundance-swca/paper-chaser-mcp:0.2.2" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 Paper Chaser MCP 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
docker --versionMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: 安装 Docker Desktop:Mac 打开 Docker.dmg,把图标拖到“应用程序”(按电脑选择 Apple silicon 或 Intel 版本)· Windows 双击 Docker Desktop Installer.exe · 装好后打开 Docker Desktop 应用并保持运行。不需要 curl 命令
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: docker --version
安装一次,所有需要 Docker 的工具都能用
SettingsDeveloperEdit Config
{
"mcpServers": {
"paper-chaser": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/joshuasundance-swca/paper-chaser-mcp:0.2.2"
]
}
}
}用 Paper Chaser MCP 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 Paper Chaser MCP,或回答中出现 Paper Chaser MCP 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
ChatGPT 暂时无法连接 Paper Chaser MCP
Paper Chaser MCP 需要安装在你的电脑上,而 ChatGPT 只能连接在网上运行的服务器
可连接 Claude Code,但需要先准备
需要先在电脑上安装 Docker(只需一次)
把这段话复制到 Claude Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Claude Code 安装 MCP server Paper Chaser MCP,按顺序:1) 用 docker --version 检查是否有 Docker。没有的话,请让我从 https://www.docker.com/products/docker-desktop/ 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):claude mcp add --scope user paper-chaser -- docker run -i --rm ghcr.io/joshuasundance-swca/paper-chaser-mcp:0.2.2 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 Paper Chaser MCP 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
docker --versionMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: 安装 Docker Desktop:Mac 打开 Docker.dmg,把图标拖到“应用程序”(按电脑选择 Apple silicon 或 Intel 版本)· Windows 双击 Docker Desktop Installer.exe · 装好后打开 Docker Desktop 应用并保持运行。不需要 curl 命令
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: docker --version
安装一次,所有需要 Docker 的工具都能用
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --scope user paper-chaser -- docker run -i --rm ghcr.io/joshuasundance-swca/paper-chaser-mcp:0.2.2应能看到 Paper Chaser MCP 在列表中并显示已连接
用 Paper Chaser MCP 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 Paper Chaser MCP,或回答中出现 Paper Chaser MCP 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor,但需要先准备
需要先在电脑上安装 Docker(只需一次)
把这段话复制到 Cursor 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Cursor 安装 MCP server Paper Chaser MCP,按顺序:1) 用 docker --version 检查是否有 Docker。没有的话,请让我从 https://www.docker.com/products/docker-desktop/ 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "paper-chaser": { "command": "docker", "args": [ "run", "-i", "--rm", "ghcr.io/joshuasundance-swca/paper-chaser-mcp:0.2.2" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 Paper Chaser MCP 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
docker --versionMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: 安装 Docker Desktop:Mac 打开 Docker.dmg,把图标拖到“应用程序”(按电脑选择 Apple silicon 或 Intel 版本)· Windows 双击 Docker Desktop Installer.exe · 装好后打开 Docker Desktop 应用并保持运行。不需要 curl 命令
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: docker --version
安装一次,所有需要 Docker 的工具都能用
用 Paper Chaser MCP 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 Paper Chaser MCP,或回答中出现 Paper Chaser MCP 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code,但需要先准备
需要先在电脑上安装 Docker(只需一次)
把这段话复制到 VS Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 VS Code 安装 MCP server Paper Chaser MCP,按顺序:1) 用 docker --version 检查是否有 Docker。没有的话,请让我从 https://www.docker.com/products/docker-desktop/ 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "servers": { "paper-chaser": { "type": "stdio", "command": "docker", "args": [ "run", "-i", "--rm", "ghcr.io/joshuasundance-swca/paper-chaser-mcp:0.2.2" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 Paper Chaser MCP 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
docker --versionMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: 安装 Docker Desktop:Mac 打开 Docker.dmg,把图标拖到“应用程序”(按电脑选择 Apple silicon 或 Intel 版本)· Windows 双击 Docker Desktop Installer.exe · 装好后打开 Docker Desktop 应用并保持运行。不需要 curl 命令
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: docker --version
安装一次,所有需要 Docker 的工具都能用
用 Paper Chaser MCP 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 Paper Chaser MCP,或回答中出现 Paper Chaser MCP 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
Claude Code
claude mcp add --scope user paper-chaser -- docker run -i --rm ghcr.io/joshuasundance-swca/paper-chaser-mcp:0.2.2Claude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"paper-chaser": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/joshuasundance-swca/paper-chaser-mcp:0.2.2"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"paper-chaser": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/joshuasundance-swca/paper-chaser-mcp:0.2.2"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"paper-chaser": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/joshuasundance-swca/paper-chaser-mcp:0.2.2"
]
}
}
}这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
在你的电脑上运行,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月20日
注册名称已通过 GitHub 账户 joshuasundance-swca 验证,该账户拥有此仓库
代码最后更新于4个月前
使用 MIT
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/joshuasundance-swca-paper-chaser-mcp)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于4个月前,最新版本(0.2.2)于8个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Docker。
同一分类中有:OpenSEO, Exa, Microsoft Learn MCP, Docs, COTAL actions (cotal.ai)
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Keyword research, site audits, rank tracking and AI visibility for your AI agent.
Official Exa MCP for web search, content fetching, and multi-step research.
Official Microsoft Learn MCP Server – real-time, trusted docs & code samples for AI and LLMs.
cotal.ai actions: product overview, site search, build log, feedback, Cloud waitlist, updates, calls
| 本项 Paper Chaser MCP | OpenSEO | Exa | Microsoft Learn MCP | Docs | COTAL actions (cotal.ai) | |
|---|---|---|---|---|---|---|
| 运行位置 | 需要安装在电脑上 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 |
| 需要密钥 | 否 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 是 | 是 | 是 | 否 | 否 |
| 基础检查 | 3/3 | 5/5 | 2/4 | 4/4 | 4/4 | 4/4 |
| 许可证 | MIT | MIT | MIT | CC-BY-4.0 | NOASSERTION | Apache-2.0 |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Release status: The repository, CLI, Docker image metadata, and public
MCP identity are now aligned on
paper-chaser-mcp. GHCR images and GitHub
Release assets are the primary public distribution channels; PyPI remains
intentionally gated until account recovery and trusted-publisher setup are
complete.
An MCP server for academic research — search papers, chase citations, look up authors, repair broken references, explore species dossiers, and retrieve regulatory text, all from one FastMCP server that AI assistants can call directly.
Providers: Semantic Scholar · arXiv · OpenAlex · CORE · SerpApi Google Scholar (opt-in, paid) · Crossref · Unpaywall · ECOS · FederalRegister.gov · GovInfo
Paper Chaser MCP is now guided-first: the default public surface is designed to be hard to misuse and explicit about trust.
research handles discovery, known-item recovery, citation repair, and regulatory routing in one trust-graded path, with a server-owned quality-first policy for guided use.follow_up_research answers against one saved searchSessionId; if you omit it, the server only infers a session when the choice is unique. Saved-session follow-up can classify mixed source sets into on-topic evidence, weaker context, and off-target leads when the stored metadata is already sufficient.executionProvenance, and ambiguous follow-up or source-inspection flows return structured sessionResolution / sourceResolution payloads instead of opaque errors.resolve_reference handles DOI/arXiv/URL, citation fragments, and regulatory-style references, and exact DOI/arXiv/ paper-URL inputs resolve as exact anchors rather than falling through to fuzzy repair. Ambiguous title-only or conflicting metadata matches can now return multiple_candidates or needs_disambiguation; treat those as candidate anchors, not citation-ready resolutions.research leads with a short recommendation-first summary, while keeping the structured evidence, leads, and provenance fields available below it.inspect_source exposes one sourceId with provenance, trust state, weak-match rationale, and quality-aware direct-read next steps; omitted searchSessionId is only accepted when one compatible saved session exists.get_runtime_status surfaces active profile/transport and provider-state warnings without requiring low-level diagnostics. configuredSmartProvider is the configured smart bundle; activeSmartProvider is the latest effective execution path, cold-start snapshots emit an explicit provisional warning instead of claiming deterministic fallback before the first smart call settles, and the top-level provider sets now split disabledProviderSet, suppressedProviderSet, degradedProviderSet, and quotaLimitedProviderSet instead of collapsing them.Use PAPER_CHASER_TOOL_PROFILE to choose the advertised surface:
| Profile | Default | Exposed surface | Intended user |
|---|---|---|---|
guided | yes | research, follow_up_research, resolve_reference, inspect_source, get_runtime_status | Low-context users and agents |
expert | no | Guided tools plus raw/provider-specific families (search_papers*, smart graph tools, regulatory direct tools, full diagnostics), subject to enabled features and disabled-tool visibility | Power users and operator workflows |
Practical default: PAPER_CHASER_TOOL_PROFILE=guided with PAPER_CHASER_HIDE_DISABLED_TOOLS=true.
If you want the fastest local path, install from source and add the server to your MCP client in stdio mode:
pip install -e .
{
"mcpServers": { "paper-chaser": { "command": "python", "args": ["-m", "paper_chaser_mcp"], "env": { "PAPER_CHASER_TOOL_PROFILE": "guided", "PAPER_CHASER_HIDE_DISABLED_TOOLS": "true", "PAPER_CHASER_ENABLE_SEMANTIC_SCHOLAR": "true", "PAPER_CHASER_ENABLE_ARXIV": "true", "PAPER_CHASER_ENABLE_CORE": "false" } } } }
Then start with one of these prompts in your MCP client:
Research retrieval-augmented generation for coding agents and return only trustworthy findings.Use my last searchSessionId to answer one grounded follow-up question.Resolve this citation fragment: Vaswani et al. 2017 Attention Is All You Need.Research the regulatory history of California condor under 50 CFR 17.95.If you want a local env template for shell runs or Docker Compose, copy .env.example to .env and fill in only the providers you use.
| Goal | Start here |
|---|---|
| Discovery, literature review, or regulatory history | research |
| Grounded follow-up over saved results | follow_up_research |
| Citation/DOI/arXiv/URL/reference cleanup | resolve_reference |
| Audit one returned source before relying on it | inspect_source |
| Explain environment/runtime differences | get_runtime_status |
| Need direct provider control or specialized pagination | switch to expert profile and use raw/provider-specific tools |
research(query="retrieval-augmented generation for coding agents", limit=5)
→ inspect resultStatus, answerability, summary, evidence, leads, routingSummary → if resultStatus=needs_disambiguation with clarification.reason=underspecified_reference_fragment: tighten the anchor or pivot to resolve_reference instead of forcing retrieval → if resultStatus=abstained and sources are suppressed: inspect suppressedSourceSummaries before rerunning or escalating → save searchSessionId for follow-up or source inspection
follow_up_research(searchSessionId="...", question="What evaluation tradeoffs show up here?")
→ inspect answerStatus → if answered: use answer + evidence (compact default: sources are identified by selectedEvidenceIds) → if abstained/insufficient_evidence: use nextActions, suppressedSourceSummaries, and inspect_source → mixed saved sessions can still answer relevance-triage questions such as which items are on-topic vs off-target → uniquely anchored recommendation asks can also return a safe start-here answer plus topRecommendation → if you omit searchSessionId and multiple saved sessions exist: provide it explicitly → for full source records pass responseMode="standard"; for diagnostics responseMode="debug" → for selection asks ("where should I start?", "most recent?"), read topRecommendation
resolve_reference(reference="10.1038/nrn3241")
→ exact DOI/arXiv/paper URL should resolve directly when supported resolve_reference(reference="Rockstrom et al planetary boundaries 2009 Nature 461 472") → inspect status and bestMatch/alternatives → only treat bestMatch as citation-ready when status=resolved → if status=multiple_candidates or needs_disambiguation: pick a candidate or add a stronger author/year/venue clue before citing it → if resolved: run research with the resolved anchor
inspect_source(searchSessionId="...", evidenceId="...")
→ inspect verificationStatus, topicalRelevance, whyClassifiedAsWeakMatch, confidenceSignals, canonicalUrl, directReadRecommendations → if searchSessionId is omitted and inference is ambiguous, rerun with an explicit saved session id
research.resultStatus is abstained or needs_disambiguation, do not invent synthesis. Narrow with a concrete anchor: DOI, exact title, species name, agency, year, or venue.research returns needs_disambiguation with clarification.reason=underspecified_reference_fragment, the server is intentionally stopping before speculative retrieval on a vague citation/reference fragment. Tighten the clue set or switch to resolve_reference.follow_up_research.answerStatus is abstained or insufficient_evidence, treat it as a safety signal. Use inspect_source and rerun research with tighter scope.PAPER_CHASER_TOOL_PROFILE=expert
→ search_papers_smart / ask_result_set / map_research_landscape / expand_research_graph → search_papers / search_papers_bulk and provider-specific families → search_federal_register / get_federal_register_document / get_cfr_text for direct regulatory primary-source control
For expert smart tools, deep is the default quality-first mode. Use balanced only when lower latency matters enough to justify a narrower pass, and reserve fast for smoke tests or debugging.
Guided research no longer accepts a public latencyProfile knob. The server owns that policy and currently applies a deep-backed quality-first path with one bounded review escalation when the first pass is too weak.
Treat these as the main guided contracts:
| Field or pattern | Where it appears | What to do with it |
|---|---|---|
resultStatus | research | succeeded, partial, needs_disambiguation, abstained, failed |
answerability | research, follow_up_research | grounded, limited, insufficient |
evidence | research, follow_up_research | Canonical grounded source records for inspection and citation |
leads | research, follow_up_research, expert smart tools | Review weak, filtered, or off-topic leads without promoting them into grounded evidence |
evidenceGaps | research, follow_up_research | Treat as explicit limits on the current answer, not hidden caveats |
routingSummary | research, follow_up_research | Check intent, anchor, provider plan, regulatory subtype or entity card when present, and why the result is partial |
coverageSummary | research, follow_up_research | Check provider coverage and completeness before relying on synthesis |
executionProvenance | guided tools | Inspect which server policy, latency defaults, and fallback path produced the result |
| confidenceSignals | research, follow_up_research, inspect_source | Inspect additive tr