io.github.theluckystrike/minimum-wage-mcp
REMOTE · MINIMUM-WAGE-MCP.LIPMICHAL.WORKERS.DEV
US state minimum wage 2026-2027: rates, tipped wages and scheduled increases for 50 states and DC.
Available components
Last scanned (5 hours ago)
Scores higher than 54% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Finance and Payments
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability72
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 729 tokens (~182/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +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.
- 31 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 30 Oct 26 66
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://minimum-wage-mcp.lipmichal.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=lipmichal.workers.dev | CN=WE1,O=Google Trust Services,C=US | 2 Oct 2026 | 31 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | ebf145553d5751d20e0d3cd51e3d7a94 |
| SANs: lipmichal.workers.dev, *.lipmichal.workers.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of minimum-wage-mcp.lipmichal.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://minimum-wage-mcp.lipmichal.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://minimum-wage-mcp.lipmichal.workers.dev/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
annual_income_at_minimum_wage Annual income at minimum wage ~178
Gross weekly, monthly and annual pay at a state's minimum wage on a date in 2026-2027, for given hours per week (default 40) and weeks per year (default 52). Uses the state rate in force on that date (with the federal floor where it applies). Pre-tax; ignores overtime and tips.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | Date as YYYY-MM-DD between 2026-01-01 and 2027-12-31. Defaults to today. |
| hours_per_week | number | – | Hours worked per week. Default 40. |
| state | string | yes | US state name or 2-letter code, or DC. Examples: "California", "TX", "District of Columbia". |
| weeks_per_year | number | – | Weeks worked per year. Default 52. |
No output schema declared.
No examples provided.
compare_states Compare state minimum wages ~126
Side-by-side minimum wages for 2 to 10 US states (or DC) on one date in 2026-2027: standard rate, tipped cash wage, tip credit, effective date and full-time annual pay (40 h x 52 weeks), sorted highest first, with the gap between highest and lowest. State-level only.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | Date as YYYY-MM-DD between 2026-01-01 and 2027-12-31. Defaults to today. |
| states | array | yes | 2 to 10 states, names or codes. |
No output schema declared.
No examples provided.
get_minimum_wage Get state minimum wage ~212
Minimum wage for one US state or DC on a date in 2026-2027: standard hourly rate, tipped cash wage, tip credit and the date the rate took effect. Uses the US DOL July 2026 tables and state labor department pages checked October 2026, including increases on July 1, September 30 and January 1, 2027 that postdate most model training data. Applies the $7.25 federal floor when a state has no law or a lower rate, and says so. Inflation-indexed 2027 rates not yet published are reported as not announced, never estimated. State-level only: city and county rates are not included.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | Date as YYYY-MM-DD between 2026-01-01 and 2027-12-31. Defaults to today. |
| state | string | yes | US state name or 2-letter code, or DC. Examples: "California", "TX", "District of Columbia". |
No output schema declared.
No examples provided.
list_upcoming_increases List upcoming minimum wage increases ~124
Every scheduled state minimum wage change from a date (default today) through 2027-12-31, sorted by date, with the new rate, the previous rate, the change and the tipped cash wage. Includes 2027-01-01 increases already enacted in law or announced under inflation indexing, and lists indexed changes whose number is not published yet as announced:false. Optional filter by states.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | Start date as YYYY-MM-DD (exclusive). Defaults to today. |
| states | array | – | Optional list of states to include. |
No output schema declared.
No examples provided.
How do I install the io.github.theluckystrike/minimum-wage-mcp server?
io.github.theluckystrike/minimum-wage-mcp is a hosted endpoint at https://minimum-wage-mcp.lipmichal.workers.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · minimum-wage-mcp.lipmichal.workers.dev
claude mcp add --transport http theluckystrike-minimum-wage-mcp 'https://minimum-wage-mcp.lipmichal.workers.dev/mcp'
What is the io.github.theluckystrike/minimum-wage-mcp server?
io.github.theluckystrike/minimum-wage-mcp is listed in the public MCP registry as io.github.theluckystrike/minimum-wage-mcp. US state minimum wage 2026-2027: rates, tipped wages and scheduled increases for 50 states and DC. This page covers its hosted endpoint (https://minimum-wage-mcp.lipmichal.workers.dev/mcp).
Is the io.github.theluckystrike/minimum-wage-mcp server safe to use?
io.github.theluckystrike/minimum-wage-mcp scores 69 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.theluckystrike/minimum-wage-mcp server expose?
io.github.theluckystrike/minimum-wage-mcp exposes 4 tools: get_minimum_wage, list_upcoming_increases, compare_states, annual_income_at_minimum_wage. Their descriptions and schemas cost roughly 640 tokens of context every time the server is loaded.
Does the io.github.theluckystrike/minimum-wage-mcp server require authentication?
No. We connected to io.github.theluckystrike/minimum-wage-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.theluckystrike/minimum-wage-mcp server still maintained?
io.github.theluckystrike/minimum-wage-mcp is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.