Pay Bands
PYPI · PAYBAND-MCP · SCANNED SEP 20
What a role really pays, including markets where the employer publishes no range.
Available components
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 native-build step with no shell scripting around it. View diagnostics → Pass
- 1 of 32 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 2 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability57
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 674 tokens (~224/item across 3 items; 3 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 Management10
- Stability observed for 3 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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "pay_bands" implies "pay" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 3 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
How do I install the Pay Bands MCP server?
Pay Bands runs locally as a PyPI package, launched with uvx payband-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 · payband-mcp
claude mcp add dheerajjha-payband-mcp -- uvx payband-mcp
{
"mcpServers": {
"dheerajjha-payband-mcp": {
"command": "uvx",
"args": [
"payband-mcp"
]
}
}
} {
"servers": {
"dheerajjha-payband-mcp": {
"command": "uvx",
"args": [
"payband-mcp"
]
}
}
} codex mcp add dheerajjha-payband-mcp -- uvx payband-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dheerajjha-payband-mcp": {
"type": "local",
"command": [
"uvx",
"payband-mcp"
],
"enabled": true
}
}
} openclaw mcp add dheerajjha-payband-mcp --command uvx --arg payband-mcp
mcp_servers:
dheerajjha-payband-mcp:
command: "uvx"
args: ["payband-mcp"] {
"McpServers": {
"dheerajjha-payband-mcp": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"payband-mcp"
]
}
}
} assistant mcp add dheerajjha-payband-mcp -t stdio -c uvx -a payband-mcp
{
"mcpServers": {
"dheerajjha-payband-mcp": {
"command": "uvx",
"args": [
"payband-mcp"
]
}
}
} 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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 18 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
- Package version: 0.10.0 → 0.11.0 functional
- 17 Sept 26 48
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 20 Sept 2026 · Analysed pypi/payband-mcp@0.11.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
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 32 packages
| Packages resolved | 32 |
|---|---|
| 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 →
job_openings ~170
List a company's open roles, with the pay range where one is published. Reads the company's public job-board API (Greenhouse, Ashby, Lever, SmartRecruiters or Workday). `role` filters to titles containing every word you give, so "forward deployed" matches "AI Engineer - FDE (Forward Deployed Engineer)". Not every employer is reachable: Google, Meta, Amazon and Apple self-host their careers sites and are not on these boards. Workday tenants (NVIDIA, Salesforce, Adobe, Cisco, HPE) are, and are found from the company name.
| Name | Type | Req | Description |
|---|---|---|---|
| board | string | – | – |
| company | string | yes | – |
| limit | integer | – | – |
| role | string | – | – |
| with_pay_only | boolean | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
market_rate ~245
Compare what a role pays across several companies at the same seniority. One company's band tells you what that company pays; several tell you whether an offer is competitive. Pass `level` (mid, senior, staff, lead, principal, manager, senior_manager, director) to compare like with like -- without it, each company's largest band is used, which may not be the same rung. Rows are sorted by what each band is worth in one currency, not by its raw number: a Polish band of 340,000 PLN outranks a US one of 187,200 USD numerically and is worth about half. Each row keeps its published figure and carries the converted one beside it. Companies on none of the supported boards are listed under `unreachable` rather than silently dropped. This is also the fallback when the company you actually care about is one of those: Google, Meta, Amazon and Apple publish nothing readable, but the employers competing for the same people do, and that is the band those offers are set against.
| Name | Type | Req | Description |
|---|---|---|---|
| companies | array | yes | – |
| level | string | – | – |
| role | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
pay_bands ~259
What a role pays at one company, broken down by seniority. Colorado, California, New York, Washington and Illinois require a salary range on covered postings; India, Singapore and most of the EU require none. So the same title at the same company carries a band in Denver and nothing in Bengaluru, and the published one is the best available anchor for the silent one -- same employer, same title, same week. Bands are reported per level, because a single range across seniorities is a number nobody is offered: "forward deployed" at Databricks spans 140,400-320,200 undivided, but resolves into a mid band, a senior band carried by 48 postings, and several management bands. `typical` is the modal band -- the one the most postings carry -- and is usually what you want. `distinct_bands` versus `postings` shows how much independent evidence there is: 48 postings sharing one band is one data point advertised 48 times, not 48 data points.
| Name | Type | Req | Description |
|---|---|---|---|
| board | string | – | – |
| company | string | yes | – |
| max_lookups | integer | – | – |
| role | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
What is the Pay Bands MCP server?
Pay Bands is an MCP server listed in the public MCP registry as io.github.dheerajjha/payband-mcp. What a role really pays, including markets where the employer publishes no range. This page covers its PyPI package (payband-mcp).
Is the Pay Bands MCP server safe to use?
Pay Bands scores 65 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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 Pay Bands MCP server expose?
Pay Bands exposes 3 tools: job_openings, pay_bands, market_rate. Their descriptions and schemas cost roughly 674 tokens of context every time the server is loaded.
Is the Pay Bands MCP server still maintained?
Pay Bands is still listed as active in the MCP registry. We last reached this channel on 20 September 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 Pay Bands MCP server under?
Pay Bands declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.