Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
Workers' Rights is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
96/100
tool-list score
9
tools declared
remote
at its publisher
—
calls last 7d
What it does
Read-only employment-law research: 140K+ rulings, employer track records, rights & EEOC guides.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http workers-rights-mcp https://www.workers-rights.com/api/mcp
# 2 — ask your agent for something these tools do
# search_rulings, find_similar_cases, get_employer_track_record and 6 more
Workers' Rights costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
WRAll 1 server
workers-rights1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http workers-rights-mcp https://www.workers-rights.com/api/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
9 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Search published employment-law rulings from our research corpus by keyword, law, court, federal circuit, state, outcome, and date. Returns published opinions with citations, outcomes, procedural stage, employers, claim types, recorded monetary amounts, and links to the full opinion. Use this to ground any claim about how employment cases have been decided. Results are quality-filtered (low-confid
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | Free-text search across case name and opinion snippet (e.g. "pregnancy discrimination retaliation"). |
| law | string | no | Filter by a related law id, e.g. "title-vii", "adea", "ada", "fmla", "flsa". |
| court | string | no | Filter by CourtListener court id, e.g. "scotus", "ca11" (11th Circuit). |
| circuit | string | no | 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- |
| state | string | no | Two-letter US state code the case was filed in, e.g. "FL", "CA". |
| outcome | string | no | Filter to a specific case outcome. |
| date_from | string | no | Earliest filing date (YYYY-MM-DD). |
| date_to | string | no | Latest filing date (YYYY-MM-DD). |
| limit | integer | no | Max rulings to return (1–25). |
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 topics courts discussed most in opinions employees won vs. lost, and a few representative example cases. Counts are returned at three levels (nationwid
| Parameter | Type | Required | Notes |
|---|---|---|---|
| claim_types | array | no | Claim types alleged, snake_case, e.g. ["retaliation","wrongful_termination","discrimination","harassment"]. The single highest-value signal. |
| protected_classes | array | no | Protected classes at issue, e.g. ["sex","race","age","disability","pregnancy","national_origin"]. |
| employer_name | string | no | Employer / defendant name, e.g. "Union Pacific Railroad". Used for a fuzzy match. |
| state | string | no | Two-letter US state code the situation arose in, e.g. "FL", "CA". |
| industry | string | no | Employer industry, e.g. "healthcare", "retail", "transportation". |
| law_ids | array | no | Related law ids, federal or state, e.g. ["title-vii","adea","ada","fmla","flsa","fl-fcra","ca-feha"]. |
| level | string | no | Which level the detailed breakdown and examples describe: "national" (default), "circuit" (federal courts of the state's region), or "state". All three levels' counts are returned either way. |
| narrow_to_laws | boolean | no | Only count opinions that mention one of law_ids (a federal law or its state analogue). Default false: every opinion sharing the claim type, under any law. |
Given an employer/company name, return distinct federal cases and trusted published opinions that involve that employer, the breakdown of outcomes (employee wins, employer wins, settlements, dismissals), the most notable recent opinions, AND the count of federal docket records on file (cases that may not have a written opinion). Use this when a user names their employer and wants that company's li
| Parameter | Type | Required | Notes |
|---|---|---|---|
| employer | string | yes | Employer/company name to look up, e.g. "Walmart", "Acme Corporation". Common suffixes like Inc/Corp/LLC are ignored when matching. |
| limit | integer | no | Number of example published opinions to return (1–25). The total count and outcome breakdown reflect the full corpus, not just these examples. |
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 match
| Parameter | Type | Required | Notes |
|---|---|---|---|
| attorney | string | yes | Employment attorney full name (e.g. "Jane Doe") or their workers-rights.com profile slug. |
| limit | integer | no | Number of example cases to return (1–25). Counts reflect all cases on file, not just these. |
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 availa
| Parameter | Type | Required | Notes |
|---|---|---|---|
| employer_sector | string | no | Whether the employer is private, state/local government, or a federal agency. |
| issue | string | no | Type of workplace issue, e.g. "discrimination", "harassment", "retaliation", "wrongful termination", "unpaid wages", "disability accommodation". |
| protected_class | string | no | Protected characteristic involved, e.g. "race", "sex", "age", "disability", "religion", "national origin", "pregnancy". |
| state | string | no | US state (2-letter code or full name) to include state-specific protections and the correct EEOC filing deadline. |
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,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| stage | integer | no | Stage number 1-9 for a deep-dive on one stage. Omit for an overview of all nine stages. |
Concrete checklist for a worker who senses termination coming or is in a deteriorating work situation: what to write down, which records are already theirs to gather (pay records, documents they were given), and how to list everything else so an attorney can ask the employer to preserve it. It does not advise copying or forwarding material from an employer’s systems. Use this whenever someone says
| Parameter | Type | Required | Notes |
|---|---|---|---|
| group | string | no | 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 public-source employment-law attorney listings near a US location. 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. Listings are not state-bar verification or an endorsement
| Parameter | Type | Required | Notes |
|---|---|---|---|
| state | string | no | US state — 2-letter code or full name (e.g. "FL" or "Florida"). Required unless lat/lng given. |
| city | string | no | Optional city to tighten the search center (e.g. "Tampa"). |
| lat | number | no | Optional precise latitude. Overrides city/state when paired with lng. |
| lng | number | no | Optional precise longitude. Overrides city/state when paired with lat. |
| language | string | no | Filter on attorney-supplied language data. Most listings are public office records that do not publish it; when none in range do, the tool returns total 0 with unsupported_filters rather than silently |
| min_rating | number | no | Minimum individual-profile rating. Office/business ratings are never treated as an attorney rating, so this matches only hand-managed profiles and returns nothing where none exist. |
| free_consultation | boolean | no | Filter on attorney-supplied fee data. Most listings are public office records that do not publish it; when none in range do, the tool returns total 0 with unsupported_filters rather than implying no a |
| contingency_fee | boolean | no | Filter on attorney-supplied fee data. Most listings are public office records that do not publish it; when none in range do, the tool returns total 0 with unsupported_filters rather than implying no a |
| radius_miles | integer | no | Search radius. Defaults to 100mi for broad statewide coverage. |
| limit | integer | no | Max attorneys to return (1–25). |
Return live statistics about the Workers' Rights corpus: total number of collected court records in the research corpus, number of public attorney listings, number of monitored legal data sources, the date the corpus was last updated, and the distribution of reportable outcomes before the employment browse filter. Use this to establish scale/credibility or to answer 'how much data do you have / ho
No parameter schema on file.
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Workers' Rights or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 96 / 100
Release 1.0.0 · scanned 20 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score96
Findings0 threat · 0 capability
Capabilityminimal
Coveragemanifest
Verificationnot in this report
Surface digest72437406085f5c3459fe028d9abc7ddb01a9e40dee370528d76f67713b449e06
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| search_rulings | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| find_similar_cases | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_employer_track_record | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_attorney_track_record | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| explain_my_rights | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_eeoc_process | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_evidence_preservation_checklist | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| find_employment_attorney | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_corpus_stats | untrusted-input | untrusted-input: keyword "browse", declares openWorldHint: true (interacts with entities outside the server) |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest72437406085f5c34
Scanned2026-10-20
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Workers' Rights can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.