# Pay Bands (pypi · payband-mcp)

What a role really pays, including markets where the employer publishes no range.

- Trust score: 65/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- pypi · `payband-mcp`: 65/100 (this document), [markdown](https://verifymcp.io/servers/dheerajjha-payband-mcp/payband-mcp.md), [page](https://verifymcp.io/servers/dheerajjha-payband-mcp/payband-mcp)

## Channel facts

- Registry: `pypi`
- Package: `payband-mcp`
- Version: `0.11.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it.
  - 1 of 32 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 2 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 57/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 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.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### 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.

### Claude

```bash
claude mcp add dheerajjha-payband-mcp -- uvx payband-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "dheerajjha-payband-mcp": {
      "command": "uvx",
      "args": [
        "payband-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dheerajjha-payband-mcp": {
      "command": "uvx",
      "args": [
        "payband-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add dheerajjha-payband-mcp -- uvx payband-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dheerajjha-payband-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "payband-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dheerajjha-payband-mcp --command uvx --arg payband-mcp
```

### Hermes

```yaml
mcp_servers:
  dheerajjha-payband-mcp:
    command: "uvx"
    args: ["payband-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "dheerajjha-payband-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "payband-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add dheerajjha-payband-mcp -t stdio -c uvx -a payband-mcp
```

### Other

```json
{
  "mcpServers": {
    "dheerajjha-payband-mcp": {
      "command": "uvx",
      "args": [
        "payband-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 65, +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.

### 2026-09-19 (score 64, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-09-18 (score 49, +1)

- [functional improvement] Stability: unverified → 0.03
- [functional] Package version: 0.10.0 → 0.11.0

### 2026-09-17 (score 48)

First indexed and scored.

## MCP tools (3)

### `job_openings` (~170 tokens)

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.

Input parameters:

- `board` (string)
- `company` (string, required)
- `limit` (integer)
- `role` (string)
- `with_pay_only` (boolean)

### `pay_bands` (~259 tokens)

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.

Input parameters:

- `board` (string)
- `company` (string, required)
- `max_lookups` (integer)
- `role` (string, required)

### `market_rate` (~245 tokens)

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.

Input parameters:

- `companies` (array, required)
- `level` (string)
- `role` (string, required)

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/dheerajjha-payband-mcp/payband-mcp#diagnostics

## Score history

- 2026-09-20: 65
- 2026-09-19: 64
- 2026-09-18: 49
- 2026-09-17: 48

## Common questions

### 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.

## Links

- PyPI project: https://pypi.org/project/payband-mcp/
- Socket report: https://socket.dev/pypi/package/payband-mcp
- Repository: https://github.com/dheerajjha/payband-mcp
- Changelog RSS feed: https://verifymcp.io/servers/dheerajjha-payband-mcp/payband-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/dheerajjha-payband-mcp/payband-mcp.json
- HTML version of this page: https://verifymcp.io/servers/dheerajjha-payband-mcp/payband-mcp