mcp server
hr-compensation-mcp-server
H1B visa salary disclosures + compensation benchmarks — real numbers, not estimates.
Description as published by the maintainer. Source
- version 1.0.0
- slowing
- evaluation
slowing — Registry entry last updated 2026-04-26. Dashed tags are derived by ZBS Index from the published description, not stated by the maintainer.
What this server can do
2 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
search_h1b_salaries(company, location, job_title)- Search the U.S. H1B visa salary database for sponsored employment data. Returns employer name, job title, approved salary, visa year, work location (city/state), and visa status. Use for understanding visa compensation trends, benchmarking tech salaries, or researching employer sponsorship patterns.
search_salaries(location, job_title)- Query general salary data by job title and geographic location. Returns average salary, salary range, number of data points, and median compensation. Use for career planning, negotiation benchmarking, or compensation analysis across roles and regions. Required: job_title.
Last successful function declaration observed on . Source: https://nexgendata-mcp-proxy.steve-corbeil.workers.dev/hr-compensation-mcp-server/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://nexgendata-mcp-proxy.steve-corbeil.workers.dev/hr-compensation-mcp-server/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 1.0.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-04-26 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-04-26 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 2 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | nexgendata-mcp-proxy.steve-corbeil.workers.dev | |
| mcp endpoint status | ok | The server listed 2 functions when asked. | as of probe | nexgendata-mcp-proxy.steve-corbeil.workers.dev |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json