What it does
Is this company still sponsoring H-1Bs and green cards? Trends from DOL and USCIS filings.
- Connects 在你的电脑上运行
- Account or key No key needed
- Category 营销与社交媒体
可搭配使用
教 AI 做这类工作的 Skill,可与本项一起使用
为什么排在这里
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 11/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 12/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 0/8 | 上次检查时云端端点有响应 |
| 使用分 | 23/100 |
质量: 基础检查通过 3/3 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
安装
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 H-1B Sponsor。按照 https://mcp.popnx.com/i/janishkumar-h1b-sponsor-mcp.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 3/3 项检查 · 在你的电脑上运行 · ✓ 命令已检查 2026年11月14日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude,但需要先准备
需要先在电脑上安装 Python (uv)(只需一次) · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
让 AI 帮你安装
把这段话复制到 Claude 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Claude 安装 MCP server H-1B Sponsor,按顺序:1) 用 uv --version 检查是否有 uv。没有的话,请让我从 https://docs.astral.sh/uv/getting-started/installation/ 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "h1b-sponsor": { "command": "uvx", "args": [ "h1b-sponsor-mcp" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 H-1B Sponsor 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
安装 uv(如果还没有)
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
uv --version- 显示版本号(例如 uv …)= 已安装,可跳过这一步
- 显示 "command not found"(Windows 显示 "is not recognized")= 还没安装,或刚装好但需要关掉终端再重新打开
怎么打开终端
Mac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: uv 没有点选式安装程序。从 uv 官方页面复制适合你系统(macOS 或 Windows)的一行命令,粘贴到终端 · 不需要单独安装 Python,uv 会在需要时自动下载
装好后关掉终端再打开,重新运行同一条命令,应显示版本号:
uv --version安装一次,所有需要 uv 的工具都能用
打开电脑版 Claude 应用的设置文件
SettingsDeveloperEdit Config
粘贴这些设置并保存文件
{ "mcpServers": { "h1b-sponsor": { "command": "uvx", "args": [ "h1b-sponsor-mcp" ] } } }退出 Claude 再重新打开
试一试
用 H-1B Sponsor 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 H-1B Sponsor,或回答中出现 H-1B Sponsor 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
ChatGPT 暂时无法连接 H-1B Sponsor
H-1B Sponsor 需要安装在你的电脑上,而 ChatGPT 只能连接在网上运行的服务器
你可以改用这些方式
A · 使用能连接 H-1B Sponsor 的应用
- 需要先在电脑上安装 Python (uv)(只需一次) · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
- 需要先在电脑上安装 Python (uv)(只需一次)
- 需要先在电脑上安装 Python (uv)(只需一次)
- 需要先在电脑上安装 Python (uv)(只需一次)
B · 营销与社交媒体 类中能连接 ChatGPT 的其他服务器
从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的
- Google Ads + Meta Ads + SEO/GEO MCP✓ ChatGPT
- Cargo✓ ChatGPT
- NotFair✓ ChatGPT
可连接 Claude Code,但需要先准备
需要先在电脑上安装 Python (uv)(只需一次)
让 AI 帮你安装
把这段话复制到 Claude Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Claude Code 安装 MCP server H-1B Sponsor,按顺序:1) 用 uv --version 检查是否有 uv。没有的话,请让我从 https://docs.astral.sh/uv/getting-started/installation/ 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):claude mcp add --scope user h1b-sponsor -- uvx h1b-sponsor-mcp 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 H-1B Sponsor 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
安装 uv(如果还没有)
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
uv --version- 显示版本号(例如 uv …)= 已安装,可跳过这一步
- 显示 "command not found"(Windows 显示 "is not recognized")= 还没安装,或刚装好但需要关掉终端再重新打开
怎么打开终端
Mac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: uv 没有点选式安装程序。从 uv 官方页面复制适合你系统(macOS 或 Windows)的一行命令,粘贴到终端 · 不需要单独安装 Python,uv 会在需要时自动下载
装好后关掉终端再打开,重新运行同一条命令,应显示版本号:
uv --version安装一次,所有需要 uv 的工具都能用
打开终端
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
粘贴这条命令并按 Enter
claude mcp add --scope user h1b-sponsor -- uvx h1b-sponsor-mcp在 Claude Code 中输入 /mcp
应能看到 H-1B Sponsor 在列表中并显示已连接
试一试
用 H-1B Sponsor 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 H-1B Sponsor,或回答中出现 H-1B Sponsor 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor,但需要先准备
需要先在电脑上安装 Python (uv)(只需一次)
让 AI 帮你安装
把这段话复制到 Cursor 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Cursor 安装 MCP server H-1B Sponsor,按顺序:1) 用 uv --version 检查是否有 uv。没有的话,请让我从 https://docs.astral.sh/uv/getting-started/installation/ 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "h1b-sponsor": { "command": "uvx", "args": [ "h1b-sponsor-mcp" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 H-1B Sponsor 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
安装 uv(如果还没有)
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
uv --version- 显示版本号(例如 uv …)= 已安装,可跳过这一步
- 显示 "command not found"(Windows 显示 "is not recognized")= 还没安装,或刚装好但需要关掉终端再重新打开
怎么打开终端
Mac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: uv 没有点选式安装程序。从 uv 官方页面复制适合你系统(macOS 或 Windows)的一行命令,粘贴到终端 · 不需要单独安装 Python,uv 会在需要时自动下载
装好后关掉终端再打开,重新运行同一条命令,应显示版本号:
uv --version安装一次,所有需要 uv 的工具都能用
在 Cursor 中以 Agent 模式打开 AI 聊天
试一试
用 H-1B Sponsor 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 H-1B Sponsor,或回答中出现 H-1B Sponsor 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code,但需要先准备
需要先在电脑上安装 Python (uv)(只需一次)
让 AI 帮你安装
把这段话复制到 VS Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 VS Code 安装 MCP server H-1B Sponsor,按顺序:1) 用 uv --version 检查是否有 uv。没有的话,请让我从 https://docs.astral.sh/uv/getting-started/installation/ 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "servers": { "h1b-sponsor": { "type": "stdio", "command": "uvx", "args": [ "h1b-sponsor-mcp" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 H-1B Sponsor 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
安装 uv(如果还没有)
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
uv --version- 显示版本号(例如 uv …)= 已安装,可跳过这一步
- 显示 "command not found"(Windows 显示 "is not recognized")= 还没安装,或刚装好但需要关掉终端再重新打开
怎么打开终端
Mac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: uv 没有点选式安装程序。从 uv 官方页面复制适合你系统(macOS 或 Windows)的一行命令,粘贴到终端 · 不需要单独安装 Python,uv 会在需要时自动下载
装好后关掉终端再打开,重新运行同一条命令,应显示版本号:
uv --version安装一次,所有需要 uv 的工具都能用
在 VS Code 中以 Agent 模式打开 AI 聊天
试一试
用 H-1B Sponsor 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 H-1B Sponsor,或回答中出现 H-1B Sponsor 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
开发者专用:终端命令和 JSON 设置
安装在电脑上
Claude Code
claude mcp add --scope user h1b-sponsor -- uvx h1b-sponsor-mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"h1b-sponsor": {
"command": "uvx",
"args": [
"h1b-sponsor-mcp"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"h1b-sponsor": {
"command": "uvx",
"args": [
"h1b-sponsor-mcp"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"h1b-sponsor": {
"type": "stdio",
"command": "uvx",
"args": [
"h1b-sponsor-mcp"
]
}
}
}这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
一览
哪些应用可以使用它
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
在你的电脑上运行,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
它能做什么
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
基础检查i
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日
- ✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 janishkumar 验证,该账户拥有此仓库
- ✓ 通过
仍在维护
代码最后更新于14天前
- ✓ 通过
有许可证
使用 MIT
- – 不适用
端点有响应
它在你的电脑上运行,没有互联网端点
- – 不适用
使用 OAuth 登录
在你的电脑上运行,改用本地设置
- … 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行;我们只能读取互联网端点的工具列表
已公开的漏洞(OSV.dev)
OSV.dev 中没有 h1b-sponsor-mcp@0.1.1 的记录
只检查这个版本的包本身,不包括所有依赖 · 检查于 2026年11月15日
作者:申请重新检查或报告信息错误
给作者:在 README 中加徽章
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/janishkumar-h1b-sponsor-mcp)讨论
提问、分享技巧或报告无法使用。按“有帮助”数量排序。
用户评价
还没有评价
与“营销与社交媒体”中的其他服务器比较i
- 星标数多于此分类中其他 4196 个服务器的 96%
- 发布到注册中心的时间比此分类中其他 4196 个服务器的 69% 更新
- 基础检查结果等于或优于此分类中其他 4196 个服务器的 99%
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
常见问题
H-1B Sponsor 安全吗?
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
它需要哪些密钥或代码?
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在我的电脑上运行还是在云端?
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
它还在维护吗?
GitHub 仓库最后更新于14天前,最新版本(0.1.1)于14天前进入注册中心。
哪些应用可以使用它?
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv)。
有什么可以替代它?
同一分类中有:Relaticle, ChatbotX, X (Twitter) MCP Server by Xquik, Betterlytics, BibiGPT YouTube Video Summarizer
功能相近的其他选择
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Relaticle
Open-source CRM your AI agents can write to: companies, people, opportunities, tasks and notes.
ChatbotX
Omnichannel customer messaging, CRM contacts, flows, sequences, broadcasts, and AI automation.
X (Twitter) MCP Server by Xquik
Xquik is the world's fastest and cheapest X (Twitter) data API with the most complete X data.
Betterlytics
Query your Betterlytics web analytics from AI agents: traffic, funnels, journeys, errors, uptime.
BibiGPT YouTube Video Summarizer
AI video summarizer: summarize and transcribe YouTube, Bilibili, TikTok and podcast videos.
| 本项 H-1B Sponsor | Relaticle | ChatbotX | X (Twitter) MCP Server by Xquik | Betterlytics | BibiGPT YouTube Video Summarizer | |
|---|---|---|---|---|---|---|
| 运行位置 | 需要安装在电脑上 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 |
| 需要密钥 | 否 | 否 | 否 | 否 | 是 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 否 | 否 | 否 |
| 基础检查 | 3/3 | 4/4 | 4/4 | 4/4 | 4/4 | 4/4 |
| 许可证 | MIT | AGPL-3.0 | NOASSERTION | MIT | AGPL-3.0 | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
作者的 README
打开 README
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
h1b-sponsor-mcp
Ask Claude "is this company still sponsoring H-1Bs?" and get a straight answer in tables, built from 1.28 million public government filings plus USCIS approval records.
An MCP server for job seekers who'll need visa sponsorship. It combines all three public sponsorship signals for each employer, shows how they've moved over the last six months against the same months a year earlier, and runs locally on a database that updates each quarter.
You: Compare Microsoft, Amazon, Google, Meta, Apple, Nvidia and TCS for data scientist sponsorship.
Claude: (calls compare_companies)
| Company | LCAs Jan–Jun 2026 | of which new employment | vs a year earlier | PERM certified, last 12 mo | USCIS new-employment approvals FY2025 | USCIS denial rate FY2025–FY2026 to Q3 | Still sponsoring? |
|---|---|---|---|---|---|---|---|
| Microsoft Corporation | 351 | 152 | -15% | 147 | 1,394 | 🟢 2.6% | 🟢 Yes, active |
| Amazon.com Services LLC | 616 | 334 | +32% | 1 | 4,637 | 🟢 1.3% | 🟢 Yes, active |
| Google LLC | 240 | 150 | +8% | 0 | 1,042 | 🟢 1.2% | 🟢 Yes, active |
| Meta Platforms, Inc | 386 | 210 | +2% | 9 | 1,554 | 🟢 1.3% | 🟢 Yes, active |
| Apple Inc. | 137 | 67 | +69% | 3 | 827 | 🟢 1.1% | 🟢 Yes, active |
| NVIDIA Corporation | 7 | 0 | +75% | 8 | 560 | 🟢 0.7% | 🟢 Yes, active |
| TATA CONSULTANCY SERVICES LIMITED | 1 | 0 | — | 0 | 846 | 🟡 6.1% Elevated | 🟡 Occasional |
Real output, data through Jun 30, 2026. LCA and PERM columns are filtered to data-scientist roles; the USCIS columns are company-wide.
That one table answers three questions most sponsorship sites can't. Is the company still filing *this year*, and in which direction? And will it take you through to a green card? Amazon and Google are filing plenty of H-1Bs for data scientists, but certified almost no green-card (PERM) cases for them in the last 12 months. And how often does USCIS turn this employer down? TCS's 6.1% denial rate is more than twice the national 2.5%, so it's flagged.
What it can answer
| Tool | Example question |
|---|---|
company_sponsorship | "Is Stripe still sponsoring? Just data roles in New York." |
compare_companies | "Compare Databricks, Snowflake and Stripe." |
top_sponsors | "Who sponsors machine learning engineers in Georgia?" |
salary_range | "What do H-1B data scientists get offered in Atlanta, by level?" |
find_employer | "Which Deloitte entities file separately?" |
data_info | "What data is this based on, and how current is it?" |
Every answer is a markdown table that names its date window ("Jan–Jun 2026", never just "last 6 months") and says what the numbers do and don't mean.
Every verdict and flag starts with a signal, so a table reads at a glance: 🟢 good · 🟡 caution · 🔴 warning · ⚪ not enough data. The word after the signal says the same thing, for anyone reading without emoji.
Install
You need uv. The package is on PyPI. The first run downloads the database (about 61 MB compressed) and caches it; after that everything is local and offline.
Claude Desktop: add to claude_desktop_config.json:
{
"mcpServers": { "h1b-sponsor": { "command": "uvx", "args": ["h1b-sponsor-mcp"] } } }
Claude Code:
claude mcp add h1b-sponsor -- uvx h1b-sponsor-mcp
Any other MCP client works the same way: run uvx h1b-sponsor-mcp over stdio. To run the newest code from GitHub instead of the PyPI release, use uvx --from git+https://github.com/janishkumar/h1b-sponsor-mcp h1b-sponsor-mcp.
Where the numbers come from
| Signal | Source | What it tells you | Coverage |
|---|---|---|---|
| H-1B LCAs | DOL Labor Condition Application disclosures | The freshest signal: an employer is preparing H-1B petitions. Split into new employment (e.g. from F-1/OPT) and transfers from other employers. | Decisions Oct 2024 – Jun 2026 (1.02M filings) |
| Green cards | DOL PERM disclosures | Whether the company sponsors permanent residence | Decisions Oct 2024 – Jun 2026 (259K cases) |
| Confirmed petitions | USCIS H-1B Employer Data Hub | Approvals and denials by petition type, per fiscal year | FY2023 – FY2026 Q3 |
How current is it? DOL publishes each quarter about 5–6 weeks after it ends, so the data is between 1.5 and 5 months old at any time. Every H-1B site uses these same files, so none can be fresher. Windows are anchored on the newest decision in the data, not today, so "last 6 months" is always a fully covered window.
What an LCA is not. An LCA is a filing an employer makes *before* an H-1B petition. It covers new hires, renewals and transfers, and some never become petitions. Treat LCA counts as an upper bound on sponsorship activity. The USCIS columns are the confirmed side.
Denial-rate flags. Each employer's USCIS denial rate over the last full fiscal year plus the current one is compared with the national rate over the same years (2.5% for FY2025–FY2026 Q3):
| Flag | Rule | Where that sits |
|---|---|---|
| 🔴 High | 3× national or more (7.6%+) | 5.5% of the 5,159 employers with 20+ decisions |
| 🟡 Elevated | 2× national or more (5.1%+) | a further 3.1% |
| 🟢 Normal | below 2× | the median employer is 1.6% |
Both flags need at least 20 decisions and 3 denials, so a single denial at a small firm doesn't produce a scary flag. New-employment petitions (the F-1/OPT → H-1B route) get their own rate in company_sponsorship. USCIS doesn't publish job titles, so denial rates are company-wide even when you filter by role.
"Still sponsoring?" is a rule, not a model. It looks at certified LCAs in the last 6 months against the same months a year earlier:
| Verdict | Rule |
|---|---|
| 🟢 Yes, active | 5+ filings, and not down by half or more |
| 🟡 Slowing sharply (−x%) | at least 10 filings a year earlier, and down 50% or more |
| 🟡 Occasional | 1–4 filings |
| 🔴 No filings in last 6 months | none in 6 months, some in the last 12 |
| 🔴 No recent sponsorship | none in 12 months |
How it's built
flowchart LR
A[DOL LCA xlsx 5 files, 1 GB] --> C[Standardise de-duplicate by case number drop contact details] B[DOL PERM xlsx] --> C U[USCIS crosstab UTF-16 export] --> C C --> E[Employer resolution names + federal tax IDs] E --> D[(sponsors.duckdb 111 MB)] D -->|gzip, GitHub release| R[Release asset] R -->|downloaded once, update check daily| S[MCP server stdio, read-only]
- Employer names are messy. Names that file under a shared federal tax ID are merged: "Amazon.com Services LLC", "AMAZON.COM SERVICES LLC", "Amazon Web Services, Inc." and "Amazon Development Center U.S., Inc." count as one employer. Two guards stop bad merges. A tax ID shared by more than 12 names is almost always a payroll provider, so it's ignored. And a name only joins a tax ID's cluster if its first word matches the main filer's. 1.28M filings resolve to 156,896 employers.
- Search matches whole leading words. "Amazon" finds Amazon.com Services, Amazon Web Services and Amazon Data Services, and lists them, so you can see exactly what was counted. If a name catches something unrelated ("Apple" also matches Apple Tree Dental),
find_employergives you the exact name to pass instead. - No personal data ships. The source files include employer contact names, emails and phone numbers, plus attorneys and preparers. The build drops all of it, and a test checks that the published database contains none of those columns.
- Lean runtime. The server installs only
mcp,duckdbandplatformdirs. Answers take under a second.
What didn't work (and what replaced it)
- Tax IDs alone over-merge. The first build merged everything that ever shared a tax ID, and "Amazon" came back with TechCorp Solutions Inc. in it: a small firm whose 21 filings list one of Amazon's tax IDs, almost certainly a keying error. A name now joins a tax ID's cluster only if its first word matches the main filer's. A regression test covers it.
- "Last 6 months" was off by a day. Subtracting six months from June 30 lands on December 30, so the first window read "Dec 2025–Jun 2026". Windows are now whole calendar months (Jan–Jun 2026 vs Jan–Jun 2025), with tests for month-end and mid-month anchors.
- Prefix search catches neighbours. "Apple" also matches Apple Tree Dental. Fuzzy brand matching would hide that rather than fix it, so every answer lists the entities it counted, and
find_employergives you the exact name to narrow it. - The government sites block scripts. The plan was a scheduled GitHub Action that refreshed the data every quarter. DOL and USCIS both return 403 to automated downloads, and DOL's official data API (45 datasets) doesn't carry LCA or PERM. So the download stays a two-minute browser step, and everything around it is automated: a watcher that says when and what to download, a gated
make refresh, and a weekly health check of the published release.
Compared with other H-1B MCP servers
I checked what already existed before building this. As of October 2026:
| This server | h1b-job-search-mcp | h1b-mcp | Hosted connectors (Pipeworx, MCPBundles) | |
|---|---|---|---|---|
| LCA filings | ✅ 21 months | ✅ one quarter at a time | via H1BGrader | ✅ |
| USCIS approvals and denials | ✅ by petition type | — | — | — |
| Green-card (PERM) filings | ✅ | — | — | — |
| Trend vs. a year earlier | ✅ | — | — | — |
| Employer names merged via tax ID | ✅ | — | — | — |
| Runs locally and offline | ✅ | downloads raw files on demand | scrapes a third-party site | hosted |
Keeping the data fresh
DOL publishes a new quarter about six weeks after it ends. DOL and USCIS refuse scripted downloads, and DOL's data API doesn't include these datasets, so one step stays human: about two minutes in a browser each quarter. Everything else is automated:
flowchart LR
W[Watcher 1st and 15th of release months] -->|new data found| N[Notification with exact files to get] N --> H[You: download 2-3 files into ~/Downloads] H --> R[make refresh] R --> C[collect, retire old years] C --> B[rebuild] B --> G{quality gates} G -->|fail| X[stop, nothing published] G -->|pass| D[before/after diff, confirm] D --> P[GitHub release] P --> U[users' servers update within a day] P --> HC[weekly health check in CI]
| Piece | What it does |
|---|---|
| Watcher (scheduled task) | Twice a month in release months, reads the DOL and USCIS pages in a browser and compares them with the published release. Says exactly which files to download, or that nothing's new. |
| `make refresh` | Moves recognised files from ~/Downloads into data/raw/ (archiving anything replaced, and handling DOL's "Dislclosure" filename typo), keeps the latest three fiscal years, rebuilds, runs the gates, prints a before/after diff, and publishes only after you confirm. make refresh-check stops after the gates. |
| Quality gates | The data must move forward. Filings in the period both builds cover must change by less than 2% (a bigger drop means a file went missing). Employer count stays plausible, Microsoft, Amazon and Google are all present, nothing has columns that look like contact details, filings resolve to employers, and all six tools answer. |
| Weekly health check (data-health.yml) | Downloads the published release the way users do and runs the same checks, plus