Is the Pay Transparency Rules for Job Posts MCP server down?

mcp-registry/io.github.nero-engine/pay-transparency-rules · v1.0.0

One MCP connection for every live tool. Your agent finds the right tool and calls it through Glimind, and skips servers that are down. Free, no signup.Add to CursorVS CodeAdd to Claude Code copies a terminal command claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server. Other clients
healthy
Last checked 2026-11-22 21:12 UTC · handshake 115ms

As of 2026-11-22 21:12 UTC, the Pay Transparency Rules for Job Posts MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

uptime (30d checks)
100%
checks observed
862
outages (90d)
0
tools
4

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

Point your MCP client at this streamable-http endpoint: https://pay-transparency-rules.nerolabs.workers.dev/mcp

Agent-readiness: B (85/100)

B (85/100): 0 error(s), 1 warning(s) across 4 tool(s); ~766 tokens of tool definitions.
Scores higher than 37% of 27,664 MCP servers Glimind has audited.
Its tool list costs an agent ~766 tokens per session — lighter than 80% of servers.
85 → 85 since 2026-11-16
no tool-poisoning patterns
Descriptions100
Safety hints30
Schemas100
Protocol100
Stability100
Token cost100
Reliability100
Client compatibility70

What to fix (2)

4 of 4 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: check_job_post, list_capabilities, list_pay_transparency_laws, list_upcoming_pay_transparency_changes

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 4 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.nero-engine%2Fpay-transparency-rules/fixes

check_job_post 1 change
{
  "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. C",
  "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
  },
  "annotations": {
    "readOnlyHint": true
  }
}
list_capabilities 1 change
{
  "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
  },
  "annotations": {
    "readOnlyHint": true
  }
}
list_pay_transparency_laws 1 change
{
  "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
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.nero-engine/pay-transparency-rules"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.nero-engine/pay-transparency-rules"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live.

Badge for your README

Shows whether the server is live and its agent-readiness score; it updates within the hour.

MCP server status

Markdown
[![MCP server status](https://glimind.com/badge/mcp-registry%2Fio.github.nero-engine%2Fpay-transparency-rules.svg)](https://glimind.com/server/mcp-registry%2Fio.github.nero-engine%2Fpay-transparency-rules?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.github.nero-engine%2Fpay-transparency-rules?ref=badge"><img src="https://glimind.com/badge/mcp-registry%2Fio.github.nero-engine%2Fpay-transparency-rules.svg" alt="MCP server status"></a>

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:8981316e42e5b49c…, first seen 2026-11-16, included at leaf 300172 of 385,232. Version history · verify what your client received.

Tools (4)

Compare: most reliable knowledge servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp?ref=install-server"
    }
  }
}

FAQ

Is the Pay Transparency Rules for Job Posts MCP server down right now?

As of 2026-11-22 21:12 UTC, the Pay Transparency Rules for Job Posts MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does Pay Transparency Rules for Job Posts MCP server provide?

Pay Transparency Rules for Job Posts MCP server advertises 4 tools, including check_job_post, list_capabilities, list_pay_transparency_laws, list_upcoming_pay_transparency_changes.

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

Point your MCP client at this streamable-http endpoint: https://pay-transparency-rules.nerolabs.workers.dev/mcp

Is the Pay Transparency Rules for Job Posts MCP server safe to connect to an AI agent?

Glimind scanned all 4 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Pay Transparency Rules for Job Posts MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve