Pay Transparency Rules for Job Posts is an MCP server published by io.github.Nero-Engine, hosted at pay-transparency-rules.nerolabs.workers.dev. When last checked on 2026-11-21 it was working: it answers and lists its tools. It declares 4 tools, including list_capabilities, check_job_post, list_pay_transparency_laws, list_upcoming_pay_transparency_changes.
Must a job post show pay? Rules for US states and cities, Canada and all 27 EU countries. Sourced.
117 connections through 4 shared values. Tap any node.
Inferred from the host name and headers: what a server runs on, not who runs it.
Lists coverage (laws by country and status), the date the data was last checked, and related Nero Labs Rules servers. Free.
No parameters.
{
"name": "list_capabilities",
"description": "Lists coverage (laws by country and status), the date the data was last checked, and related Nero Labs Rules servers. Free.",
"inputSchema": {
"type": "object",
"properties": {},
"additionalProperties": false
}
}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.
None yet. Changes appear after a server's second daily check.
Squares are this server's values; dots are other servers sharing them. A shared address or publisher is a lead, not proof of a common operator.
| Parameter | Type | Description |
|---|---|---|
| date | string | Posting date, YYYY-MM-DD. Defaults to today. Future dates include laws already enacted with a later start. |
| 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. |
| locations * | array | 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_scope | string | If remote, where from: "US", "EU", "Canada" or "anywhere". Default: the countries of the locations given. |
| employer_employees | integer | Total employees. Several laws only cover employers above a size. Optional. |
{
"name": "check_job_post",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"locations"
],
"properties": {
"date": {
"type": "string",
"description": "Posting date, YYYY-MM-DD. Defaults to today. Future dates include laws already enacted with a later start."
},
"remote": {
"type": "boolean",
"description": "True if the job can be done remotely. Many US laws then apply to remote jobs that could be done in their state."
},
"locations": {
"type": "array",
"items": {},
"description": "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_scope": {
"type": "string",
"description": "If remote, where from: \"US\", \"EU\", \"Canada\" or \"anywhere\". Default: the countries of the locations given."
},
"employer_employees": {
"type": "integer",
"description": "Total employees. Several laws only cover employers above a size. Optional."
}
},
"additionalProperties": false
}
}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.
| Parameter | Type | Description |
|---|---|---|
| status | string | Optional: in_force, enacted_not_yet_in_force, pending, transposition_overdue. |
| country | string | Optional: "US", "CA", "EU", or a country name such as "Germany". |
{
"name": "list_pay_transparency_laws",
"description": "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.",
"inputSchema": {
"type": "object",
"properties": {
"status": {
"type": "string",
"description": "Optional: in_force, enacted_not_yet_in_force, pending, transposition_overdue."
},
"country": {
"type": "string",
"description": "Optional: \"US\", \"CA\", \"EU\", or a country name such as \"Germany\"."
}
},
"additionalProperties": false
}
}Lists pay transparency laws and amendments starting in a date window, soonest first, so a recruiter or HR agent can prepare. Free.
| Parameter | Type | Description |
|---|---|---|
| days | integer | 1 to 730, default 365. |
| from_date | string | YYYY-MM-DD, default today. |
{
"name": "list_upcoming_pay_transparency_changes",
"description": "Lists pay transparency laws and amendments starting in a date window, soonest first, so a recruiter or HR agent can prepare. Free.",
"inputSchema": {
"type": "object",
"properties": {
"days": {
"type": "integer",
"description": "1 to 730, default 365."
},
"from_date": {
"type": "string",
"description": "YYYY-MM-DD, default today."
}
},
"additionalProperties": false
}
}Before publishing a job post, call check_job_post with the job locations (and remote: true if it can be done remotely), the employer headcount and the posting date. It returns which pay transparency laws apply, a merged checklist of what the post must say, salary history bans, penalties and the official source for each law.
Names, descriptions and schemas were written by the server and are shown as data.
Shared addresses on big platforms (Cloudflare, Vercel and the like) put unrelated servers together; those are marked shared_infrastructure. A match is a pivot, not a link between operators.