io.github.Nero-Engine/pay-transparency-rules

Est-ce que io.github.Nero-Engine/pay-transparency-rules est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.github.Nero-Engine/pay-transparency-rules » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 4 outils

• check_job_post≈ 422 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.

  Paramètres, retour & exemple (5)

  Paramètres

  • date · string · optionnel
    Posting date, YYYY-MM-DD. Defaults to today. Future dates include laws already enacted with a later start.
  • remote · boolean · optionnel
    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 · requis
    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 · optionnel
    If remote, where from: "US", "EU", "Canada" or "anywhere". Default: the countries of the locations given.
  • employer_employees · integer · optionnel
    Total employees. Several laws only cover employers above a size. Optional.

  Exemple d'appel

  {"name": "check_job_post", "arguments": {"locations": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_capabilities≈ 64 tokens

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

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "list_capabilities", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_pay_transparency_laws≈ 160 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.

  Paramètres, retour & exemple (2)

  Paramètres

  • status · string · optionnel
    Optional: in_force, enacted_not_yet_in_force, pending, transposition_overdue.
  • country · string · optionnel
    Optional: "US", "CA", "EU", or a country name such as "Germany".

  Exemple d'appel

  {"name": "list_pay_transparency_laws", "arguments": {"status": "texte", "country": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_upcoming_pay_transparency_changes≈ 107 tokens

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

  Paramètres, retour & exemple (2)

  Paramètres

  • days · integer · optionnel
    1 to 730, default 365.
  • from_date · string · optionnel
    YYYY-MM-DD, default today.

  Exemple d'appel

  {"name": "list_upcoming_pay_transparency_changes", "arguments": {"days": 1, "from_date": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://pay-transparency-rules.nerolabs.workers.dev/mcp