Find what a role actually pays, including where the employer publishes nothing. MCP server reading published salary bands off Greenhouse, Ashby, Lever and Workday -- per seniority, per currency.
概览
Renamed from blind-mcp in 0.5.0. The Blind tools are still here (see below), but reading published pay bands is what this does, so the name now says so. The old GitHub URL redirects; the old PyPI package points here. BLIND_MCP_* environment variables still work — PAYBAND_* is preferred. Colorado, California, New York, Washington and Illinois require a salary range on covered job postings. India, Singapore and most of the EU require none. So the same title, at the same company, in the same week, is posted with a band in Denver and without one in Bengaluru. The band is still there. It is just attached to a different listing. Per level, because one range across seniorities is a number nobody is offered — undivided, that role reads as 140,400–320,200, a 2.3x spread covering five different jobs. typical is the modal band. : 58 postings sharing one band is one data point advertised 58 times.
README
以下为原文 README 节选，完整内容请查看原文。
payband-mcp
Find out what a role actually pays — including in markets where the employer publishes nothing.
Renamed from
blind-mcpin 0.5.0. The Blind tools are still here (see below), but reading published pay bands is what this does, so the name now says so. The old GitHub URL redirects; the old PyPI package points here.BLIND_MCP_*environment variables still work —PAYBAND_*is preferred.
Colorado, California, New York, Washington and Illinois require a salary range on covered job postings. India, Singapore and most of the EU require none. So the same title, at the same company, in the same week, is posted with a band in Denver and without one in Bengaluru.
The band is still there. It is just attached to a different listing.
pay_bands(company="Databricks", role="forward deployed")
101 matching openings · band width ratio x1.37 · 33 publish no range
LEVEL TYPICAL BAND BANDS POSTS PRECISION
mid 152,900–210,155 2 3 tight
senior 182,000–250,208 1 58 tight
lead 178,800–245,850 1 1 tight
manager 211,800–291,300 4 5 tight
senior_manager 232,900–320,200 1 1 tight
steps: mid→senior +19.1% · lead→manager +18.5% · manager→sr_mgr +9.9%
silent: Remote-India, Seoul, London, Berlin, Amsterdam
Per level, because one range across seniorities is a number nobody is
offered — undivided, that role reads as 140,400–320,200, a 2.3x spread
covering five different jobs.
typical is the modal band. distinct_bands vs postings is the honest
measure of evidence: 58 postings sharing one band is one data point
advertised 58 times. precision flags how much a band actually narrows
things — Databricks posts tight per-level bands, Figma posts a single x2.5
band spanning its whole ladder, and both are real.
That is the same employer, the same title, the same moment — a far better anchor for an unpublished number than any salary survey, and it takes one call.
The same job, in every market the employer posts it in
Employers covered by transparency law in one country often post the same role in several. That is the closest thing to a controlled experiment you can get:
安装
This server does not publish a one-line install command.
Open the repository installation guide 新手？先看 mcpskill.org 教程 →配置
{
"mcpServers": {
"payband": {
"command": "uv",
"args": ["run", "--directory", "/path/to/payband-mcp", "payband-mcp"]
}
}
}