# Pay Transparency Rules for Job Posts (remote · pay-transparency-rules.nerolabs.workers.dev)

Must a job post show pay? Rules for US states and cities, Canada and all 27 EU countries. Sourced.

- Trust score: 59/100 (low)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-18

## Components

- remote · `pay-transparency-rules.nerolabs.workers.dev`: 59/100 (this document), [markdown](https://verifymcp.io/servers/nero-engine-pay-transparency-rules/pay-transparency-rules.md), [page](https://verifymcp.io/servers/nero-engine-pay-transparency-rules/pay-transparency-rules)

## Channel facts

- Endpoint: `https://pay-transparency-rules.nerolabs.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-10-18.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 72/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 609 tokens (~152/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "list_pay_transparency_laws" implies "pay" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Pay Transparency Rules for Job Posts MCP server?

Pay Transparency Rules for Job Posts is a hosted endpoint at https://pay-transparency-rules.nerolabs.workers.dev/mcp, so there is nothing to install locally. 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 --transport http nero-engine-pay-transparency-rules 'https://pay-transparency-rules.nerolabs.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "nero-engine-pay-transparency-rules": {
      "url": "https://pay-transparency-rules.nerolabs.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "nero-engine-pay-transparency-rules": {
      "type": "http",
      "url": "https://pay-transparency-rules.nerolabs.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.nero-engine-pay-transparency-rules]
url = "https://pay-transparency-rules.nerolabs.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "nero-engine-pay-transparency-rules": {
      "type": "remote",
      "url": "https://pay-transparency-rules.nerolabs.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add nero-engine-pay-transparency-rules --url 'https://pay-transparency-rules.nerolabs.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  nero-engine-pay-transparency-rules:
    url: "https://pay-transparency-rules.nerolabs.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "nero-engine-pay-transparency-rules": {
      "Transport": "http",
      "Url": "https://pay-transparency-rules.nerolabs.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add nero-engine-pay-transparency-rules -t streamable-http -u 'https://pay-transparency-rules.nerolabs.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "nero-engine-pay-transparency-rules": {
      "type": "http",
      "url": "https://pay-transparency-rules.nerolabs.workers.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-10-16 (score 59, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-14 (score 58, +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-10-12 (score 57, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-11 (score 56)

First indexed and scored.

## MCP tools (4)

### `list_capabilities` (~35 tokens)

Lists coverage (laws by country and status), the date the data was last checked, and related Nero Labs Rules servers. Free.

### `check_job_post` (~313 tokens)

Checks a job post against pay transparency laws before it is published. Give every location the job is based in or could be done from, whether it can be done remotely, the employer headcount and the posting date. Returns each law that applies (or may apply, with the reason), a merged checklist of what the post must include (for example a good-faith minimum and maximum pay range and a description of benefits), salary history question bans, penalties and the official source and citation per law. Covers US states and cities, Canadian provinces and the EU Pay Transparency Directive (EU) 2023/970 country by country, including countries that have not transposed it yet. Free.

Input parameters:

- `date` (string): Posting date, YYYY-MM-DD. Defaults to today. Future dates include laws already enacted with a later start.
- `employer_employees` (integer): Total employees. Several laws only cover employers above a size. Optional.
- `locations` (array, required): Where the job is based or could be done. Each item is a string like "Denver, CO", "New York City", "Ontario, Canada", "Germany", or an object {country, state, city}.
- `remote` (boolean): True if the job can be done remotely. Many US laws then apply to remote jobs that could be done in their state.
- `remote_scope` (string): If remote, where from: "US", "EU", "Canada" or "anywhere". Default: the countries of the locations given.

### `list_pay_transparency_laws` (~122 tokens)

Lists pay transparency laws with status (in force, enacted not yet in force, pending, EU transposition overdue), start date, who is covered and what a posting must include. Filter by country ("US", "CA", "EU" or an EU country name) and status. Free.

Input parameters:

- `country` (string): Optional: "US", "CA", "EU", or a country name such as "Germany".
- `status` (string): Optional: in_force, enacted_not_yet_in_force, pending, transposition_overdue.

### `list_upcoming_pay_transparency_changes` (~70 tokens)

Lists pay transparency laws and amendments starting in a date window, soonest first, so a recruiter or HR agent can prepare. Free.

Input parameters:

- `days` (integer): 1 to 730, default 365.
- `from_date` (string): YYYY-MM-DD, default today.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/nero-engine-pay-transparency-rules/pay-transparency-rules#diagnostics

## Score history

- 2026-10-18: 59
- 2026-10-17: 59
- 2026-10-16: 59
- 2026-10-15: 58
- 2026-10-14: 58
- 2026-10-13: 57
- 2026-10-12: 57
- 2026-10-11: 56

## Common questions

### What is the Pay Transparency Rules for Job Posts MCP server?

Pay Transparency Rules for Job Posts is an MCP server listed in the public MCP registry as io.github.Nero-Engine/pay-transparency-rules. Must a job post show pay? Rules for US states and cities, Canada and all 27 EU countries. Sourced. This page covers its hosted endpoint (https://pay-transparency-rules.nerolabs.workers.dev/mcp).

### Is the Pay Transparency Rules for Job Posts MCP server safe to use?

Pay Transparency Rules for Job Posts scores 59 out of 100 on VerifyMCP. 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 Transparency Rules for Job Posts MCP server expose?

Pay Transparency Rules for Job Posts exposes 4 tools: list_capabilities, check_job_post, list_pay_transparency_laws, list_upcoming_pay_transparency_changes. Their descriptions and schemas cost roughly 540 tokens of context every time the server is loaded.

### Does the Pay Transparency Rules for Job Posts MCP server require authentication?

No. We connected to Pay Transparency Rules for Job Posts without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Pay Transparency Rules for Job Posts MCP server still maintained?

Pay Transparency Rules for Job Posts is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://pay-transparency-rules.nerolabs.workers.dev/mcp
- Website: https://pay-transparency-rules.nerolabs.workers.dev/
- Changelog RSS feed: https://verifymcp.io/servers/nero-engine-pay-transparency-rules/pay-transparency-rules.xml
- Changelog JSON feed: https://verifymcp.io/servers/nero-engine-pay-transparency-rules/pay-transparency-rules.json
- HTML version of this page: https://verifymcp.io/servers/nero-engine-pay-transparency-rules/pay-transparency-rules