H-1B Sponsor
PYPI · H1B-SPONSOR-MCP
Is this company still sponsoring H-1Bs and green cards? Trends from DOL and USCIS filings.
Available components
Last scanned (1 hour ago)
Scores higher than 65% of PyPI servers
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 30 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability64
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 725 tokens (~120/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +30
- Injection markers: unverified → pass ▲ security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Stability: unverified → 0.23 ▲ functional
- 4 Nov 26 −27
- Tool safety: pass → unverified ▼ security
- Malware scan: pass → unverified ▼ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 0.1.0 → 0.1.1 functional
- 3 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
- 2 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- 30 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 29 Oct 26 51
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed pypi/h1b-sponsor-mcp@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 30 packages
| Packages resolved | 30 |
|---|---|
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
company_sponsorship ~232
Is a company still sponsoring H-1Bs, and how much? Returns trend tables. Shows certified H-1B LCA filings for the last 6 months, the fiscal year so far and the last full fiscal year (each vs the same period a year earlier), split into new employment and transfers; green-card (PERM) certifications; USCIS petition approvals/denials by fiscal year; and a denial-rate flag (Normal / Elevated / High) relative to the national rate. Point out a High or Elevated flag to the user. Args: company: Employer name as people say it, e.g. "Microsoft", "Amazon", "JPMorgan". role: Optional job filter, e.g. "data scientist", "machine learning", "software engineer". Matches job title and occupation title. state: Optional two-letter worksite state, e.g. "GA". city: Optional worksite city, e.g. "Atlanta".
| Name | Type | Req | Description |
|---|---|---|---|
| city | – | – | – |
| company | string | yes | – |
| role | – | – | – |
| state | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
compare_companies ~109
Compare employers side by side: filings, trend, green cards, denial-rate flag, verdict. Args: companies: Two or more employer names, e.g. ["Stripe", "Databricks", "Snowflake"]. role: Optional job filter, e.g. "data scientist". state: Optional two-letter worksite state. city: Optional worksite city.
| Name | Type | Req | Description |
|---|---|---|---|
| city | – | – | – |
| companies | array | yes | – |
| role | – | – | – |
| state | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
data_info ~24
Which data the answers come from, the dates covered, and the caveats.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
find_employer ~57
List the legal employer entities a name matches, so you can pick an exact one. Args: query: Start of the employer name, e.g. "Deloitte" or "Amazon Web Services".
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
salary_range ~97
Offered H-1B wages for a role (percentiles and by experience level), last 12 months. Args: role: Job, e.g. "data scientist", "software engineer". state: Optional two-letter worksite state. city: Optional worksite city. company: Optional employer to restrict to.
| Name | Type | Req | Description |
|---|---|---|---|
| city | – | – | – |
| company | – | – | – |
| role | string | yes | – |
| state | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
top_sponsors ~141
Rank employers by certified H-1B filings (with denial-rate flags), for a role and place. Args: role: Optional job filter, e.g. "data scientist", "data engineer". state: Optional two-letter worksite state, e.g. "GA". city: Optional worksite city, e.g. "Atlanta". months: Look-back window in whole months ending at the latest data (1-21). limit: Number of employers to return (max 100).
| Name | Type | Req | Description |
|---|---|---|---|
| city | – | – | – |
| limit | integer | – | – |
| months | integer | – | – |
| role | – | – | – |
| state | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the H-1B Sponsor MCP server?
H-1B Sponsor runs locally as a PyPI package, launched with uvx h1b-sponsor-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · h1b-sponsor-mcp
claude mcp add janishkumar-h1b-sponsor-mcp -- uvx h1b-sponsor-mcp
What is the H-1B Sponsor MCP server?
H-1B Sponsor is an MCP server listed in the public MCP registry as io.github.janishkumar/h1b-sponsor-mcp. Is this company still sponsoring H-1Bs and green cards? Trends from DOL and USCIS filings. This page covers its PyPI package (h1b-sponsor-mcp).
Is the H-1B Sponsor MCP server safe to use?
H-1B Sponsor scores 69 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the H-1B Sponsor MCP server expose?
H-1B Sponsor exposes 6 tools: company_sponsorship, compare_companies, top_sponsors, salary_range, find_employer, data_info. Their descriptions and schemas cost roughly 660 tokens of context every time the server is loaded.
Is the H-1B Sponsor MCP server still maintained?
H-1B Sponsor is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the H-1B Sponsor MCP server under?
H-1B Sponsor declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.