Pay Transparency Rules for Job Posts MCP server
online · 100% uptimeio.github.Nero-Engine/pay-transparency-rules·v1.0.0Must a job post show pay? Rules for US states and cities, Canada and all 27 EU countries. Sourced.
Little public usage data yet
Reviews
Write oneNobody has reviewed Pay Transparency Rules for Job Posts yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Pay Transparency Rules for Job Posts tools (4, 3 write)
write = sends, deletes, buys or postscheck_job_postwrite actionFreeChecks 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.
list_capabilitiesFreeLists coverage (laws by country and status), the date the data was last checked, and related Nero Labs Rules servers. Free.
list_pay_transparency_lawswrite actionFreeLists 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.
list_upcoming_pay_transparency_changeswrite actionFreeLists pay transparency laws and amendments starting in a date window, soonest first, so a recruiter or HR agent can prepare. Free.
Public scan report
scanner v0.1.10 · 2026-10-13 · same rubric, same numbers if you re-run it
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote reachable in 411ms20/20
- Tool poisoning4 tool descriptions checked15/15
- Auth qualityopen endpoint exposes 3 write-action tools with no auth3/15
- Maintenanceno repository listed3/15
- Maintainer identityno repository or website to verify2/10
Findings (2)
- highWrite-action tools reachable without authentication
auth.open-write - lowNo source repository listed
maint.no-repo
How Pay Transparency Rules for Job Posts compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 57/100
- higher than 12% of 48,255 servers
- Tools
- 4
- the typical server has 7
- Tools that change things
- 75%
- typical: 0%. Fewer write tools means less an agent can break
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 249 ms
- faster than 55% of 30,031 servers
What its tools let an agent do: 1 read · 3 change
Install Pay Transparency Rules for Job Posts in Claude Code, Cursor or VS Code
claude mcp add --transport http pay-transparency-rules https://pay-transparency-rules.nerolabs.workers.dev/mcp
Pay Transparency Rules for Job Posts: common questions
- Is Pay Transparency Rules for Job Posts MCP server safe?
- With care: it is graded C, so read the findings first (57/100). Read the Pay Transparency Rules for Job Posts safety report
- How do I install Pay Transparency Rules for Job Posts?
- It runs remotely at pay-transparency-rules.nerolabs.workers.dev. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does Pay Transparency Rules for Job Posts need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Pay Transparency Rules for Job Posts maintained?
- The latest release is v1.0.0.
- Is Pay Transparency Rules for Job Posts up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does Pay Transparency Rules for Job Posts compare with other MCP servers?
- safety score 57/100 (higher than 12% of 48,255 servers); tools 4 (the typical server has 7); tools that change things 75% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.