Home / MCP registry index / com.workers-rights/employment-law

Workers' Rights

com.workers-rights/employment-law in the official MCP registry. Endpoint https://www.workers-rights.com/api/mcp.

The registry describes it as: Read-only employment-law research: 140K+ rulings, employer track records, rights & EEOC guides.

We read its 9 tools on 2026-10-28. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Tools it advertises

search_rulings find_similar_cases get_employer_track_record get_attorney_track_record explain_my_rights get_eeoc_process get_evidence_preservation_checklist find_employment_attorney get_corpus_stats

Run this server? Show the check in your README

The badge reflects the latest weekly read: MCP tool check badge

Markdown
[![MCP tool check](https://lazaretto.dev/mcp-registry/com-workers-rights-employment-law/badge.svg)](https://lazaretto.dev/mcp-registry/com-workers-rights-employment-law)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.