timesfm
TimesFM (Time Series Foundation Model) is a pretrained time-series foundation model developed by Google Research for time-series forecasting.
Conference & journal CFP deadlines, CCF/ICORE/QUALIS rankings, acceptance rates, research fields.
作者提供的原文
教 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
此项在“连接 AI 的应用”标签中,该标签不使用星标,按以下顺序排列
| 1. 在 Claude 连接器目录中 | 否 | |
|---|---|---|
| 2. 团队实测过 | 否 | |
| 3. 适合泰国用户 | 否 | |
| 4. 不计星标的使用量 | 20/100 | 热度 0 · 新鲜度 12 · 仍在响应 8 · 用户喜欢 +0 |
| 5. 登记日期 | 2026-10-29 |
用户喜欢: 0 · 最多加 5 分(每人 1 分),不能用钱买。
质量: 基础检查通过 3/5 项(仅展示,不用于排序)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 Conference Partner。按照 https://mcp.popnx.com/i/myhuiban-www-conference-partner.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 3/5 项检查 · 你的提问会经过开发者的服务器(www.myhuiban.com) · ✓ 命令已检查 2026年11月20日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude · 约 2 分钟
不需要密钥,不用安装程序 · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加
CustomizeConnectors
把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue
Conference Partnerhttps://www.myhuiban.com/mcp在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add
+ConnectorsConference Partner
用 Conference Partner 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 Conference Partner,或回答中出现 Conference Partner 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
能否连接 ChatGPT 取决于方案
完整 MCP:网页版 ChatGPT Business、Enterprise 或 Edu · Pro:以读取/获取权限连接,修改数据的工具可能用不了 · Plus:官方文档尚未确认,如果在插件页看到添加自定义 MCP 的选项可以试试 · 仅限网页
Plugins+Add custom MCP server
输入名称,在 Connection 下粘贴地址,勾选风险提示,然后点击 Create as a plugin
Conference Partnerhttps://www.myhuiban.com/mcp开启新聊天,输入前先从插件列表中选择 Conference Partner
用 Conference Partner 告诉我你能帮我做什么,然后做一件给我看✓ 如果 ChatGPT 说正在使用 Conference Partner,或回答中出现 Conference Partner 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 OpenAI 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Claude Code · 约 2 分钟
不需要密钥,不用安装程序
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --transport http --scope user conference-partner https://www.myhuiban.com/mcp应能看到 Conference Partner 在列表中并显示已连接
用 Conference Partner 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 Conference Partner,或回答中出现 Conference Partner 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor · 约 2 分钟
不需要密钥,不用安装程序
用 Conference Partner 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 Conference Partner,或回答中出现 Conference Partner 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code · 约 2 分钟
不需要密钥,不用安装程序
用 Conference Partner 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 Conference Partner,或回答中出现 Conference Partner 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看
通过网页连接的应用使用的地址
https://www.myhuiban.com/mcpJSON 设置在下方“开发者专用”中
Claude Code
claude mcp add --transport http --scope user conference-partner https://www.myhuiban.com/mcpCursor (~/.cursor/mcp.json)
{
"mcpServers": {
"conference-partner": {
"url": "https://www.myhuiban.com/mcp"
}
}
}VS Code (mcp.json)
{
"servers": {
"conference-partner": {
"type": "http",
"url": "https://www.myhuiban.com/mcp"
}
}
}这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
通过互联网连接,适用于
ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
工具名称和描述与服务器在 2026年11月17日 报告的完全一致。这些内容由作者撰写,不是我们写的;我们以纯文本形式显示。
search_conferencesSearch academic conferences. Every parameter is optional — combine any of keyword, CCF/CORE/QUALIS rank, research field and submission/conference date ranges. Filter-only queries work fine (e.g. field=ai plus a submission-deadline window, no keyword). Returns a paginated list.
search_journalsSearch academic journals. Every parameter is optional — combine any of keyword, CCF rank, research field and ISSN. Returns a paginated list.
list_conferencesBrowse conference lists and rankings (open CFPs, ranked venues with a call open now, popularity, most competitive, etc.), paginated. No keyword filtering — use search_conferences for that.
list_journalsBrowse journal lists and rankings (special-issue CFPs, CCF, highest impact factor, popularity, all), paginated. No keyword filtering — use search_journals for that.
get_conferenceGet full details of a conference by id: basics, CFP text, acceptance-rate history, edition history, structured ratings and comments, related conferences/journals. REQUIRES CREDENTIALS: Authorization: Bearer (free API key from https://www.myhuiban.com/account/api-keys, or a JWT fr
get_journalGet full details of a journal by id: basics, CFP text, special issues, structured ratings and comments, related journals/conferences. REQUIRES CREDENTIALS: Authorization: Bearer (free API key from https://www.myhuiban.com/account/api-keys, or a JWT from POST /api/login). response
get_researcherGet a researcher's public profile by id: name, institution, auto-generated research-interest summary, CV, tracked/attended conferences and tracked journals. REQUIRES CREDENTIALS: Authorization: Bearer (free API key from https://www.myhuiban.com/account/api-keys, or a JWT from POS
get_statisticsSite-level public statistics: conference/journal totals, how many conferences have an open call for papers, upcoming deadlines by month, open CFPs by CCF / ICORE / QUALIS tier, conference country and research-field distributions, journal impact-factor, CCF-tier, publisher and res
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月20日
发布者(www.myhuiban.com)不是仓库所有者(sundou82);可能是其他人代为上架的
代码最后更新于昨天
GitHub 无法识别许可证类型;请打开文件自行查看
在 123 毫秒内响应(HTTP 200)
无需登录
已读取 8 个工具描述,未发现针对 AI 的隐藏指令
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/myhuiban-www-conference-partner)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 5 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于昨天,最新版本(1.12.0)于22天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。
同一分类中有: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
| 本项 Conference Partner | OpenSEO | Exa | Microsoft Learn MCP | Docs | COTAL actions (cotal.ai) | |
|---|---|---|---|---|---|---|
| 运行位置 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 |
| 需要密钥 | 否 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 是 | 是 | 是 | 否 | 否 |
| 基础检查 | 3/5 | 5/5 | 2/4 | 4/4 | 4/4 | 4/4 |
| 许可证 | NOASSERTION | MIT | MIT | CC-BY-4.0 | NOASSERTION | Apache-2.0 |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Academic conference and journal data for AI agents and scripts: CFP deadlines, CCF / CORE / QUALIS rankings, the Conference Partner Index (CP-I) — a 0–100 score we compute for every conference, including the majority that carry no external rank — acceptance-rate history, edition history, journal impact factors and special issues — served by Conference Partner (会伴), a conference tracker that has been maintained since 2013.
Two surfaces over one dataset:
| Endpoint | For | |
|---|---|---|
| MCP | https://www.myhuiban.com/mcp (Streamable HTTP) | Claude, ChatGPT, Cursor, VS Code, any MCP client |
| REST | https://www.myhuiban.com/api/* | scripts, backends, OpenAPI codegen |
Both are backed by the same services and return identical payloads — the only difference is the protocol envelope.
Search, ranking lists and site statistics need no credentials at all. Point a client at the URL and the first call works.
curl "https://www.myhuiban.com/api/conferences?ccf_rank=A&field=ai&submission_date_start=2026-08-05"
Claude Code
claude mcp add --transport http conference-partner https://www.myhuiban.com/mcp
Claude.ai / Claude Desktop (Settings → Connectors → Add custom connector)
Remote MCP server URL:
https://www.myhuiban.com/mcp
To unlock the detail tools, add a static request header in the connector's advanced settings: Authorization: Bearer hb_xxx (see Credentials).
Cursor — ~/.cursor/mcp.json or .cursor/mcp.json
{
"mcpServers": { "conference-partner": { "url": "https://www.myhuiban.com/mcp" } } }
</details>
VS Code — .vscode/mcp.json
{
"servers": { "conference-partner": { "type": "http", "url": "https://www.myhuiban.com/mcp" } } }
</details>
ChatGPT (Settings → Connectors → Create)
MCP server URL https://www.myhuiban.com/mcp, authentication No authentication (or *API key* with your hb_ key to enable the detail tools).
Ready-to-copy files for each client live in examples/mcp-config/, and the per-client walkthrough — including how to attach a key — is in docs/mcp-clients.md.
Also listed on Smithery, Glama and the official MCP registry as com.myhuiban.www/conference-partner.
Eight read-only tools, each with a REST twin returning the same payload.
| Tool | REST twin | Credentials |
|---|---|---|
search_conferences | GET /api/conferences | — |
search_journals | GET /api/journals | — |
list_conferences | GET /api/conferences/rankings/{ranking} | — |
list_journals | GET /api/journals/rankings/{ranking} | — |
get_statistics | GET /api/statistics | — |
get_conference | GET /api/conferences/{id} | free account |
get_journal | GET /api/journals/{id} | free account |
get_researcher | GET /api/researchers/{id} | free account |
Search accepts any combination of keyword, ccf_rank (A/B/C), core_rank (A\*/A/B/C), qualis_rank, field (research areas, CS and beyond), submission/conference date ranges and updated_since for incremental sync. Rank parameters take several comma-separated values matched as OR — ccf_rank=A,B,C is every CCF-rated venue. Every parameter is optional — filter-only queries such as "AI conferences with a deadline in the next 90 days" are the point.
Ranking lists cover open CFPs, the three tier lists, the Conference Partner Index, popularity, lowest acceptance rate, trending, upcoming/past — and for journals, special-issue CFPs and highest impact factor. The CFP and date-ordered lists also take field.
Every venue object carries fields, the research-field slugs it is tagged with, so loaded results can be narrowed further client-side. A rank field is "" when the venue is not on that list, which for CCF is most conferences.
The MCP server also ships prompts — ready-made tasks your client offers as one-click starting points, so you are not left staring at a list of tool names:
| Prompt | What it does |
|---|---|
upcoming_deadlines | deadlines you can still submit to, by field and tier |
where_to_submit | give it a paper topic, get ranked venues whose calls are open |
venue_snapshot | everything on record for one conference or journal |
open_special_issues | journals currently running a special-issue call |
Full machine-readable definitions, refreshed from production by CI: spec/openapi.json and spec/mcp-tools.json.
| Tier | How | Limit |
|---|---|---|
| Anonymous | send nothing | 50 requests/day per source IP |
| Free account | Authorization: Bearer hb_xxx | 200 requests/day, shared across REST + MCP |
| Paid | — | *planned, not available yet* |
Create a key at myhuiban.com/account/api-keys — it never expires and can be revoked individually, which is what you want for a client that only lets you pin a fixed request header. A JWT from POST /api/login works too and draws on the same pool.
Every response carries X-Quota-Limit and X-Quota-Remaining. CORS is open, so browser JavaScript works.
401 = this endpoint needs a credential, or the one you sent is invalid. An unusable credential is never silently downgraded to the anonymous tier. 402 = account quota exhausted. 429 = anonymous per-IP quota exhausted.
Runnable, no API key required:
# upcoming CCF-A deadlines in AI, next 90 days
python examples/python/upcoming_deadlines.py --field ai --ccf A --days 90
node examples/node/upcoming-deadlines.mjs --field ai --ccf A --days 90
python examples/python/export_deadlines.py --out ./snapshot
python examples/python/incremental_sync.py --since 2026-07-01
bash examples/curl/quickstart.sh
See examples/README.md.
actions/deadline-watch is a GitHub Action that keeps one issue up to date with the deadlines you can still submit to — no API key, nothing to host. Issue #1 is this repo running it on a schedule, so you can see the output before adopting it.
- uses: sundou82/conference-partner-mcp/actions/deadline-watch@main
with: field: security days: 120
`data/` carries a snapshot refreshed daily by CI, as JSON and CSV:
upcoming-deadlines | every conference whose deadline has not passed |
ccf-conferences · core-conferences · qualis-conferences | the tier catalogues — all three ranks are columns on every row, alongside CP-I |
open-calls-by-rank | the ranked venues you can still submit to today |
ccf-journals · top-impact-factor-journals | journals by tier and by impact factor |
journal-special-issues | journals with an open special-issue call |
data/README.md renders the next 90 days as a table you can read in the browser.
The snapshot covers exactly what the anonymous tier already serves — nothing in it is gated. Per-venue detail (CFP full text, acceptance-rate history, edition history, ratings) stays behind the API, where a free key reaches it.
A file is stale the moment a deadline is extended, which in submission season is daily. Use it to browse, diff or bulk-load; call the API when it has to be right.
CI commits data/ once a day and only when something actually changed, so the commit history of that directory is a change feed. GitHub publishes it as Atom, no account needed:
https://github.com/sundou82/conference-partner-mcp/commits/main/data.atom
Point a feed reader at it, or diff two commits to see exactly which deadlines moved:
git log --oneline -- data/
git diff HEAD~1 HEAD -- data/upcoming-deadlines.csv
Watching the repo on GitHub (*Watch → Custom → Releases*, or all activity) gets you the same signal as email.
Deadline lists are easy to find. These are the parts that are hard to reproduce:
cp_index is our own 0–100 index over academic recognition, selectivity, longevity, community and how much a venue publishes about itself, so the long tail is comparable too. Every value ships with a confidence and a link to the method — a low score on a thinly documented venue means we know little about it, not that it is weak.updated_since with an updated_at watermark on every row, so a mirror is a diff rather than a re-crawl.Methodology, coverage and known limits: myhuiban.com/methodology.
This repo is the distribution entry point for the API and MCP server: client configuration, examples, and CI-synced specs. The server itself is not open source — it is a hosted service; nothing here needs to be installed or run to use it.
docs/mcp-clients.md — per-client setup, with and without a keydocs/rest-api.md — endpoints, parameters, errors, incremental syncdocs/data.md — what is in the dataset, attribution, termsexamples/ — runnable Python, Node and curl clients; MCP config filesspec/ — OpenAPI 3 document, MCP tool definitions and server card, re-fetched from production daily by CI so they cannot go staleAuthoritative reference: [myhuiban.com/developers](https://www.myhuiban.com/developers). Where this repo and that page ever d