# Workers' Rights (remote · www.workers-rights.com)

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

- Trust score: 73/100 (medium)
- Change this week: +5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-04

## Components

- remote · `www.workers-rights.com`: 73/100 (this document), [markdown](https://verifymcp.io/servers/com-workers-rights-employment-law/api-mcp.md), [page](https://verifymcp.io/servers/com-workers-rights-employment-law/api-mcp)

## Channel facts

- Endpoint: `https://www.workers-rights.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-04.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 66/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2063 tokens (~229/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http com-workers-rights-employment-law https://www.workers-rights.com/api/mcp
```

### Codex

```toml
[mcp_servers.com-workers-rights-employment-law]
url = "https://www.workers-rights.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-workers-rights-employment-law": {
      "type": "remote",
      "url": "https://www.workers-rights.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-workers-rights-employment-law --url https://www.workers-rights.com/api/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-workers-rights-employment-law:
    url: "https://www.workers-rights.com/api/mcp"
```

### Other

```json
{
  "mcpServers": {
    "com-workers-rights-employment-law": {
      "type": "http",
      "url": "https://www.workers-rights.com/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-04 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-02 (score 72, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “get_attorney_track_record” rewrote its description, which is the text the model reads
- [security] Tool “search_rulings” rewrote its description, which is the text the model reads
- [security] Tool “find_employment_attorney” rewrote its description, which is the text the model reads
- [cosmetic] “find_employment_attorney” reworded the description of “free_consultation”
- [cosmetic] “find_employment_attorney” reworded the description of “language”
- [cosmetic] “find_employment_attorney” reworded the description of “min_rating”
- [cosmetic] “find_employment_attorney” reworded the description of “contingency_fee”

### 2026-07-31 (score 71, +4)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 67, −2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 67, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 67)

First indexed and scored.

## MCP tools (9)

### `search_rulings` (~364 tokens)

Search employment-law rulings

Search a 140,000+ U.S. court-ruling research corpus by keyword, law, court, federal circuit, state, outcome, and date. Returns real cases with citations, outcomes, case stage, employers, claim types, damages, and links to the full opinion. Use this to ground any claim about how employment cases have been decided. Results are quality-filtered (low-confidence and junk rows excluded).

Input parameters:

- `circuit` (string): Filter to a federal appeals circuit (the appeals court plus its district courts). Preferred values: first-circuit, second-circuit, third-circuit, fourth-circuit, fifth-circuit, sixth-circuit, seventh…
- `court` (string): Filter by CourtListener court id, e.g. "scotus", "ca11" (11th Circuit).
- `date_from` (string): Earliest filing date (YYYY-MM-DD).
- `date_to` (string): Latest filing date (YYYY-MM-DD).
- `law` (string): Filter by a related law id, e.g. "title-vii", "adea", "ada", "fmla", "flsa".
- `limit` (integer): Max rulings to return (1–25).
- `outcome` (string): Filter to a specific case outcome.
- `query` (string): Free-text search across case name and opinion snippet (e.g. "pregnancy discrimination retaliation").
- `state` (string): Two-letter US state code the case was filed in, e.g. "FL", "CA".

### `find_similar_cases` (~280 tokens)

Find how similar cases were decided

Given the facts of an employment situation — claim types, protected class, employer, state — analyze how similar real cases in the corpus were decided. Returns the aggregate plaintiff (employee) win rate, settlement rate, typical damages range, the factors that most helped employees win vs. lose, and a few representative example cases. This is the highest-value grounding tool for 'what are my chances / what matters' questions. Educational statistics, not a prediction or legal advice.

Input parameters:

- `claim_types` (array): Claim types alleged, snake_case, e.g. ["retaliation","wrongful_termination","discrimination","harassment"]. The single highest-value signal.
- `employer_name` (string): Employer / defendant name, e.g. "Union Pacific Railroad". Used for a fuzzy match.
- `industry` (string): Employer industry, e.g. "healthcare", "retail", "transportation".
- `law_ids` (array): Related law ids, e.g. ["title-vii","adea","ada","fmla","flsa"].
- `protected_classes` (array): Protected classes at issue, e.g. ["sex","race","age","disability","pregnancy","national_origin"].
- `state` (string): Two-letter US state code the situation arose in, e.g. "FL", "CA".

### `get_employer_track_record` (~166 tokens)

Get an employer's litigation track record

Given an employer/company name, return how many employment-law rulings in the corpus involve that employer, the breakdown of outcomes (employee wins, employer wins, settlements, dismissals), the most notable recent cases, AND the count of federal docket filings on record (active/filed cases that may not have a written opinion yet). Use this when a user names their employer and wants that company's litigation history + footprint.

Input parameters:

- `employer` (string, required): Employer/company name to look up, e.g. "Walmart", "Acme Corporation". Common suffixes like Inc/Corp/LLC are ignored when matching.
- `limit` (integer): Number of example cases to return (1–25). The total count and outcome breakdown reflect the full corpus, not just these examples.

### `get_attorney_track_record` (~152 tokens)

Get an employment attorney's case track record

Given an employment attorney name (or profile slug), return the federal employment-law cases on file in which that attorney appeared — case caption, court, year, nature-of-suit, and the side they appeared for when on record. Use this when a user names an attorney and wants their public litigation history. Facts only, sourced from federal court dockets. Attorney identities are algorithmically matched; ambiguous and lower-confidence matches are excluded.

Input parameters:

- `attorney` (string, required): Employment attorney full name (e.g. "Jane Doe") or their workers-rights.com profile slug.
- `limit` (integer): Number of example cases to return (1–25). Counts reflect all cases on file, not just these.

### `explain_my_rights` (~257 tokens)

Explain applicable employment-law rights

Explain which federal (and state, if a state is given) employment laws may protect a worker based on the type of issue (e.g. discrimination, harassment, retaliation, wrongful termination) and/or the protected class involved (e.g. race, sex, age, disability, pregnancy). Returns the relevant statutes with citations, who they cover (employer-size thresholds), filing deadlines and agencies, and available remedies. Use this to ground an answer about a worker’s legal protections. Deadline guidance covers private-sector and state/local government workers; federal employees follow a separate process with a much shorter deadline (45 days to contact their agency's EEO counselor). Educational information, not legal advice.

Input parameters:

- `issue` (string): Type of workplace issue, e.g. "discrimination", "harassment", "retaliation", "wrongful termination", "unpaid wages", "disability accommodation".
- `protected_class` (string): Protected characteristic involved, e.g. "race", "sex", "age", "disability", "religion", "national origin", "pregnancy".
- `state` (string): US state (2-letter code or full name) to include state-specific protections and the correct EEOC filing deadline.

### `get_eeoc_process` (~196 tokens)

Explain the EEOC charge process

Plain-English guide to the 9 stages of an EEOC discrimination/retaliation charge, from pre-filing through resolution. Call with no arguments for an overview of all stages with typical durations; call with a stage number (1-9) for a deep-dive on that stage: what to expect, how long it takes, the key tip, and do/don't guidance. Use this whenever someone asks what happens after filing with the EEOC, how long the process takes, what a position statement or rebuttal is, or what to do at the stage they are currently in. Covers private-sector and state/local government workers; federal employees follow a separate EEO process with a much shorter deadline (45 days to contact their agency's EEO counselor).

Input parameters:

- `stage` (integer): Stage number 1-9 for a deep-dive on one stage. Omit for an overview of all nine stages.

### `get_evidence_preservation_checklist` (~200 tokens)

Evidence preservation checklist (before losing access)

Concrete checklist for a worker who senses termination coming or is in a deteriorating work situation: what to save (emails, chat DMs, performance reviews, HR records, pay records), in what order, and how to do it without crossing lines — preserving your own employment record is legal; taking company IP is not. Use this whenever someone says they think they are about to be fired, fears retaliation is escalating, mentions a PIP or sudden access changes, or asks what to do before reporting discrimination. Sections: 'today' (highest-leverage, minutes matter), 'this-week', 'quiet' (low-priority prep). Time-sensitive — employers often revoke system access during the termination call itself.

Input parameters:

- `group` (string): Checklist section for a focused list: 'today' (highest-leverage, do first), 'this-week', or 'quiet' (lower-priority quiet prep). Omit for the full checklist.

### `find_employment_attorney` (~284 tokens)

Find an employment attorney

Find employment-law attorneys near a US location from a public directory of 9,500+ attorneys. Returns source-attributed identity, firm, location, and contact data sorted by proximity. Person-specific filters and fields apply only where the underlying directory supports them; Google Places metrics are labeled as firm/office listing data, never individual ratings.

Input parameters:

- `city` (string): Optional city to tighten the search center (e.g. "Tampa").
- `contingency_fee` (boolean): Filter source-supported attorney fee data; Google office listings are excluded.
- `free_consultation` (boolean): Filter source-supported attorney fee data; Google office listings are excluded.
- `language` (string): Filter source-supported attorney language data; Google office listings are excluded.
- `lat` (number): Optional precise latitude. Overrides city/state when paired with lng.
- `limit` (integer): Max attorneys to return (1–25).
- `lng` (number): Optional precise longitude. Overrides city/state when paired with lat.
- `min_rating` (number): Minimum individual-profile rating; Google office ratings are excluded.
- `radius_miles` (integer): Search radius. Defaults to 100mi for broad statewide coverage.
- `state` (string): US state — 2-letter code or full name (e.g. "FL" or "Florida"). Required unless lat/lng given.

### `get_corpus_stats` (~87 tokens)

Get corpus size and freshness

Return live statistics about the Workers' Rights corpus: total number of employment-law court rulings, number of attorneys in the directory, number of monitored legal data sources, the date the corpus was last updated, and the distribution of case outcomes across the analyzed rulings. Use this to establish scale/credibility or to answer 'how much data do you have / how current is it'.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-workers-rights-employment-law/api-mcp#diagnostics

## Score history

- 2026-08-04: 73
- 2026-08-03: 72
- 2026-08-02: 72
- 2026-08-01: 71
- 2026-07-31: 71
- 2026-07-30: 67
- 2026-07-29: 69
- 2026-07-28: 68
- 2026-07-27: 67
- 2026-07-26: 67

## Links

- Remote endpoint: https://www.workers-rights.com/api/mcp
- Website: https://www.workers-rights.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-workers-rights-employment-law/api-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-workers-rights-employment-law/api-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/com-workers-rights-employment-law/api-mcp