timesfm
TimesFM (Time Series Foundation Model) is a pretrained time-series foundation model developed by Google Research for time-series forecasting.
Job search mechanics for an AI assistant: search, fetch postings, render CVs, lint, log.
教 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 |
|---|---|---|
| 新鲜度 | 7/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 0/8 | 上次检查时云端端点有响应 |
| 使用分 | 7/100 |
质量: 基础检查通过 3/3 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 MCP Job Search。按照 https://mcp.popnx.com/i/michalper-mcp-job-search.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 3/3 项检查 · 在你的电脑上运行 · ✓ 命令已检查 2026年11月13日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude,但需要先准备
需要先在电脑上安装 Python (uv)(只需一次) · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
把这段话复制到 Claude 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Claude 安装 MCP server MCP Job Search,按顺序:1) 用 uv --version 检查是否有 uv。没有的话,请让我从 https://docs.astral.sh/uv/getting-started/installation/ 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "job-search": { "command": "uvx", "args": [ "mcp-job-search-mp" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 MCP Job Search 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
uv --versionMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: uv 没有点选式安装程序。从 uv 官方页面复制适合你系统(macOS 或 Windows)的一行命令,粘贴到终端 · 不需要单独安装 Python,uv 会在需要时自动下载
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: uv --version
安装一次,所有需要 uv 的工具都能用
SettingsDeveloperEdit Config
{
"mcpServers": {
"job-search": {
"command": "uvx",
"args": [
"mcp-job-search-mp"
]
}
}
}用 MCP Job Search 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 MCP Job Search,或回答中出现 MCP Job Search 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
ChatGPT 暂时无法连接 MCP Job Search
MCP Job Search 需要安装在你的电脑上,而 ChatGPT 只能连接在网上运行的服务器
可连接 Claude Code,但需要先准备
需要先在电脑上安装 Python (uv)(只需一次)
把这段话复制到 Claude Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Claude Code 安装 MCP server MCP Job Search,按顺序:1) 用 uv --version 检查是否有 uv。没有的话,请让我从 https://docs.astral.sh/uv/getting-started/installation/ 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):claude mcp add --scope user job-search -- uvx mcp-job-search-mp 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 MCP Job Search 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
uv --versionMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: uv 没有点选式安装程序。从 uv 官方页面复制适合你系统(macOS 或 Windows)的一行命令,粘贴到终端 · 不需要单独安装 Python,uv 会在需要时自动下载
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: uv --version
安装一次,所有需要 uv 的工具都能用
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --scope user job-search -- uvx mcp-job-search-mp应能看到 MCP Job Search 在列表中并显示已连接
用 MCP Job Search 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 MCP Job Search,或回答中出现 MCP Job Search 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor,但需要先准备
需要先在电脑上安装 Python (uv)(只需一次)
把这段话复制到 Cursor 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Cursor 安装 MCP server MCP Job Search,按顺序:1) 用 uv --version 检查是否有 uv。没有的话,请让我从 https://docs.astral.sh/uv/getting-started/installation/ 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "job-search": { "command": "uvx", "args": [ "mcp-job-search-mp" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 MCP Job Search 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
uv --versionMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: uv 没有点选式安装程序。从 uv 官方页面复制适合你系统(macOS 或 Windows)的一行命令,粘贴到终端 · 不需要单独安装 Python,uv 会在需要时自动下载
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: uv --version
安装一次,所有需要 uv 的工具都能用
用 MCP Job Search 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 MCP Job Search,或回答中出现 MCP Job Search 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code,但需要先准备
需要先在电脑上安装 Python (uv)(只需一次)
把这段话复制到 VS Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 VS Code 安装 MCP server MCP Job Search,按顺序:1) 用 uv --version 检查是否有 uv。没有的话,请让我从 https://docs.astral.sh/uv/getting-started/installation/ 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "servers": { "job-search": { "type": "stdio", "command": "uvx", "args": [ "mcp-job-search-mp" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 MCP Job Search 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
uv --versionMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: uv 没有点选式安装程序。从 uv 官方页面复制适合你系统(macOS 或 Windows)的一行命令,粘贴到终端 · 不需要单独安装 Python,uv 会在需要时自动下载
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: uv --version
安装一次,所有需要 uv 的工具都能用
用 MCP Job Search 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 MCP Job Search,或回答中出现 MCP Job Search 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
Claude Code
claude mcp add --scope user job-search -- uvx mcp-job-search-mpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"job-search": {
"command": "uvx",
"args": [
"mcp-job-search-mp"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"job-search": {
"command": "uvx",
"args": [
"mcp-job-search-mp"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"job-search": {
"type": "stdio",
"command": "uvx",
"args": [
"mcp-job-search-mp"
]
}
}
}这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
在你的电脑上运行,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日
注册名称已通过 GitHub 账户 michalper 验证,该账户拥有此仓库
代码最后更新于30天前
使用 MIT
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
OSV.dev 中没有 mcp-job-search-mp@0.2.0 的记录
只检查这个版本的包本身,不包括所有依赖 · 检查于 2026年11月15日
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/michalper-mcp-job-search)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于30天前,最新版本(0.2.0)于30天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv)。
同一分类中有: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.
Connect AI agents to Exa 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
| 本项 MCP Job Search | 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、图片和脚本已被移除。链接会离开本站。
An MCP server that automates the repetitive mechanics around job-hunting with an AI coding assistant, while deliberately not automating the parts that need a human: drafting your CV/cover letter, fact-checking claims against your real history, and submitting an application.
It answers the question that keeps eating a job search's time: *"this CV draft looks fine, but did it quietly fabricate something, and is this one specific posting even worth reading?"*
Status: early stage. Built for personal use, published because the
configurable anti-fabrication linter and application-registry tooling are
generically useful beyond one person's job search. All seven tools are
working. See
CHANGELOG.mdfor what changed and what was verified live.
A few open-source MCP servers already do job search + CV tailoring (not-boring-resume-mcp, resume-mcp, Workopia MCP, IAM MCP Server, LinkedIn MCP Server, among others). This one targets what they don't:
fetch_job_posting reads one URL you already found instead of indexing their listings, and on boards confirmed to sit behind an active Cloudflare challenge (Pracuj.pl, Indeed), it fails loudly rather than trying to solve the challenge automatically. See the verified coverage table below — this is a documented boundary, not a silent gap.lint_cv reads them from a YAML file you control, so the mechanism is reusable even though the facts it checks against are personal (see "Why a configurable linter" below).What this server doesn't pretend to be: it doesn't cover every job board — only ones with a real API, or a single posting URL a human already found. It never submits anything on your behalf. And a clean lint_cv run doesn't mean a CV is honest, only that it passes the specific rules you wrote — semantic fabrication (two true facts combined into a false-sounding one) still needs a human or an independent adversarial review to catch.
From PyPI (published as mcp-job-search-mp — mcp-job-search was already taken by an unrelated project; the command stays mcp-job-search):
pip install mcp-job-search-mp
uvx mcp-job-search-mp
From source, for development:
git clone https://github.com/michalper/mcp-job-search.git
cd mcp-job-search python3.12 -m venv .venv .venv/bin/pip install -e ".[dev]"
{
"mcpServers": { "job-search": { "command": "/absolute/path/to/mcp-job-search/.venv/bin/mcp-job-search", "env": { "LINT_RULES_PATH": "/absolute/path/to/your/lint_rules.yaml", "REGISTRY_CONFIG_PATH": "/absolute/path/to/your/registry.yaml" } } } }
Configure via environment variables — all optional, every tool degrades gracefully when something is unset:
| Variable | Used by | Default |
|---|---|---|
ADZUNA_APP_ID, ADZUNA_APP_KEY | search_jobs | unset — Adzuna skipped |
ADZUNA_COUNTRY | search_jobs | pl |
RAPIDAPI_JSEARCH_KEY | search_jobs | unset — JSearch skipped |
JSEARCH_COUNTRY | search_jobs | us (JSearch's own API default) |
LINT_RULES_PATH | lint_cv | bundled src/mcp_job_search/examples/lint_rules.example.yaml |
REGISTRY_CONFIG_PATH | log_application | bundled src/mcp_job_search/examples/registry.example.yaml |
CHROME_PATH | render_pdf | auto-detected (macOS app bundle, Linux $PATH, common Windows install dirs) |
SEARCH_CACHE_DIR | search_jobs | ~/.cache/mcp-job-search/search |
SEARCH_CACHE_TTL_SECONDS | search_jobs | 21600 (6 hours) |
Adzuna's free tier is 25 one-time test calls, then a paid plan (£8/month, 5,000 calls) — budget calls accordingly once past testing. JSearch's free tier is 200 requests/month; search_jobs caches results by query (SEARCH_CACHE_DIR/SEARCH_CACHE_TTL_SECONDS, default 6h) specifically to protect that quota from repeated identical queries — pass use_cache=False to force a fresh one when you actually need it.
fetch_job_posting will never try to solve a CAPTCHA or bot-detection challenge automatically, on any site, regardless of how narrow the request — confirmed via response headers that Pracuj.pl and Indeed (pl.indeed.com) both sit behind an active Cloudflare challenge (cf-mitigated: challenge / 401 with a Cloudflare bot-management cookie), not just a missing-JavaScript issue. A real, human-driven browser session passes both normally — for a page like this, read it with a real browser instead of this tool.
lint_cv sees itThe CV draft here (tests/fixtures/sample_cv_with_violations.html) was seeded on purpose, and lint_cv is pointed at the bundled generic example rules (src/mcp_job_search/examples/lint_rules.example.yaml), not a real person's facts:
{
"clean": false, "findings": [ {"severity": "error", "message": "generic corporate jargon — replace with a concrete claim"}, {"severity": "error", "message": "unsupported superlative — ground it in a specific result or cut it"}, {"severity": "error", "message": "example: list cloud/K8s here only if you have real production experience"}, {"severity": "error", "message": "a .gitignore edit is hygiene, not an achievement"}, {"severity": "error", "message": "a commit count is not an achievement on its own"}, {"severity": "error", "message": "example: flag a title claim that contradicts your real specialization"}, {"severity": "note", "message": "link rendered as in body (https://example.com/portfolio) — use plain text"} ] }
clean is false because real rules fired, not a guess — and every message came from the YAML file, not from code that knows anything about a specific person's career.
| Tool | Status | Description |
|---|---|---|
search_jobs | working | real search across Arbeitnow (free, no key), Adzuna and JSearch (API keys) — verified live against the Polish PHP market on both paid sources (10 real listings each, recognizable employers); results cached to protect JSearch's free quota |
fetch_job_posting | working | single-URL extraction via trafilatura — verified live, clean extraction on JustJoin.it, NoFluffJobs, Bulldogjob, theprotocol.it, Solid.Jobs, CzyJestEldorado.pl, and LinkedIn single-posting pages; confirmed, by design, not to bypass Pracuj.pl/Indeed's Cloudflare bot-detection challenge |
render_pdf | working | headless-Chrome HTML→PDF with the exact flags that avoid known hangs/silent failures; cross-platform CHROME_PATH auto-detection; page-count verification via raw PDF byte scan |
lint_cv | working | configurable mechanical linter — banned phrases, skills-section-only bans, achievement-weight overclaims, title/GDPR/link checks, page-count limits, all driven by a YAML file you control |
log_application | working | appends one row to a Markdown application registry in the correct section and date position, with a column_map for non-English headers; never invents free-text content |
list_applications | working | read-only query over the registry (filter by portal/company) — use before log_application to check for a duplicate |
update_application_status | working | rewrites one row's status cell in place; refuses to guess when more than one row matches |
fetch_job_posting, 2026-10-19)| Site | Result |
|---|---|
| JustJoin.it | ✅ clean extraction |
| NoFluffJobs | ✅ clean extraction |
| Bulldogjob | ✅ clean extraction |
| theprotocol.it | ✅ clean extraction |
| Solid.Jobs | ✅ clean extraction |
| CzyJestEldorado.pl (aggregator) | ✅ clean extraction |
LinkedIn (/jobs/view/ ) | ✅ clean extraction — the single-posting view is public |
| Jooble | N/A — redirects to the source site (e.g. JustJoin.it); nothing of its own to fetch |
| Pracuj.pl | ❌ blocked — active Cloudflare challenge, not attempted |
Indeed (pl.indeed.com) | ❌ blocked — active Cloudflare challenge, not attempted |
The original motivation: a CV draft once conflated two separate true facts into one false-sounding claim, and it shipped before anyone caught it. A grep-based mechanical check can catch a banned phrase; it can't catch semantic conflation — that still needs a human or an independent adversarial review. What a mechanical linter *can* do reliably: enforce *your own* banned-phrase list, page limits, and required clauses, consistently, every time, without you re-checking the same things by hand. lint_cv is that — generic, so anyone can point it at their own facts.
.venv/bin/python -m pytest --cov # tests + coverage
.venv/bin/ruff check . # lint .venv/bin/mypy src # types .venv/bin/bandit -c pyproject.toml -r src # security .venv/bin/pip-audit # dependency vulnerabilities
Run .venv/bin/pre-commit install once to run all of the above (except pip-audit, which needs network access and stays CI-only) on every commit.
One manual end-to-end check (not run in CI — needs live network and a real Chrome install), also documented in CHANGELOG.md:
search_jobs(keywords="PHP", remote_only=True, sources=["arbeitnow"]) against the live Arbeitnow API.fetch_job_posting(url=...) on a URL from step 1.render_pdf(html_path=...) on a sample CV, confirm success and page_count.lint_cv(html_path=...) on a file with a seeded violation, confirm it's reported.log_application(..., dry_run=True) against your own registry, confirm the previewed row and insertion point look right before dropping dry_run.See