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.
Available components
Last scanned (13 hours ago)
Scores higher than 45% of remote servers
Reachable. Last reached 18 Oct 2026.
Category CRM and Sales
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. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability72
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 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. See how to fix → Fail
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 16 Oct 26 +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.
- 14 Oct 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.
- 12 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 11 Oct 26 56
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 18 Oct 2026 · Probed https://pay-transparency-rules.nerolabs.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=nerolabs.workers.dev | CN=YE2,O=Let's Encrypt,C=US | 12 Sept 2026 | 11 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6f7f02a43942bb2aca3c411aec703cf0dc1 |
| SANs: *.nerolabs.workers.dev, nerolabs.workers.dev | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of pay-transparency-rules.nerolabs.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://pay-transparency-rules.nerolabs.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://pay-transparency-rules.nerolabs.workers.dev/mcp | Inconclusive | 405 |
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 →
check_job_post ~313
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
No output schema declared.
No examples provided.
list_capabilities ~35
Lists coverage (laws by country and status), the date the data was last checked, and related Nero Labs Rules servers. Free.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_pay_transparency_laws ~122
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
list_upcoming_pay_transparency_changes ~70
Lists pay transparency laws and amendments starting in a date window, soonest first, so a recruiter or HR agent can prepare. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | 1 to 730, default 365. |
| from_date | string | – | YYYY-MM-DD, default today. |
No output schema declared.
No examples provided.
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.
remote · pay-transparency-rules.nerolabs.workers.dev
claude mcp add --transport http nero-engine-pay-transparency-rules 'https://pay-transparency-rules.nerolabs.workers.dev/mcp'
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.