US Minimum Wage by Address and Date
REMOTE · US-MINIMUM-WAGE.NEROLABS.WORKERS.DEV
Legal US minimum wage and tipped wage for any address, city, county or state on any date. Sourced.
Available components
Last scanned (21 hours ago)
Scores higher than 45% of remote servers
Reachable. Last reached 18 Oct 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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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 Usability69
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 581 tokens (~193/item across 3 items; 3 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 Management23
- Stability observed for 7 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 16 Oct 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.
- 14 Oct 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.
- 12 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 11 Oct 26 57
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 18 Oct 2026 · Probed https://us-minimum-wage.nerolabs.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=nerolabs.workers.dev | CN=YE2,O=Let's Encrypt,C=US | 12 Sept 2026 | 11 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6f7f02a43942bb2aca3c411aec703cf0dc1 |
| SANs: *.nerolabs.workers.dev, nerolabs.workers.dev | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of us-minimum-wage.nerolabs.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://us-minimum-wage.nerolabs.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://us-minimum-wage.nerolabs.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 →
get_minimum_wage ~341
Returns the legal hourly minimum wage that applies at a US location on a date: the highest of the federal, state, county and city rates, which jurisdiction sets it, the minimum cash wage for tipped workers, special industry rates (for example California fast food, Los Angeles hotels), the next scheduled change, and the primary government source for each figure. Give an address (most accurate: it resolves the exact city and county, including unincorporated areas) or a state plus city and/or county. Rates can depend on employer size or region; pass employer_size to get one answer, otherwise every variant is listed. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | US street address, for example "100 N Main St, Los Angeles, CA". Resolved with the US Census Bureau geocoder. |
| annual_revenue | number | – | Employer annual gross sales or receipts in US dollars. A few states (Ohio, Oklahoma, Montana) set a lower rate below a threshold. Optional. |
| city | string | – | City name, for example "Seattle". Optional. |
| county | string | – | County name, for example "Montgomery County". Optional. |
| date | string | – | Date the work is done, YYYY-MM-DD. Defaults to today. Future dates use rates already scheduled or announced. |
| employer_size | integer | – | Number of employees. Some places set different rates by employer size. Optional. |
| industry | string | – | Optional, for example "fast food", "hotel", "healthcare". Used to flag special industry rates. |
| state | string | – | Two-letter state code or name. Needed when no address is given. |
No output schema declared.
No examples provided.
list_capabilities ~37
Lists coverage (how many states, counties and cities), the date the data was last checked, and related Nero Labs Rules servers. Free.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_upcoming_minimum_wage_changes ~127
Lists every scheduled or announced minimum wage change (state, county and city) in a date window, soonest first, with the new rate and source. Use it to plan payroll or warn an employer before a rate rises. Filter by state. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Window length in days, 1 to 730. Default 365. |
| from_date | string | – | Start of the window, YYYY-MM-DD. Defaults to today. |
| state | string | – | Two-letter state code or name. Optional, all states when left out. |
No output schema declared.
No examples provided.
How do I install the US Minimum Wage by Address and Date MCP server?
US Minimum Wage by Address and Date is a hosted endpoint at https://us-minimum-wage.nerolabs.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 · us-minimum-wage.nerolabs.workers.dev
claude mcp add --transport http nero-engine-us-minimum-wage 'https://us-minimum-wage.nerolabs.workers.dev/mcp'
What is the US Minimum Wage by Address and Date MCP server?
US Minimum Wage by Address and Date is an MCP server listed in the public MCP registry as io.github.Nero-Engine/us-minimum-wage. Legal US minimum wage and tipped wage for any address, city, county or state on any date. Sourced. This page covers its hosted endpoint (https://us-minimum-wage.nerolabs.workers.dev/mcp).
Is the US Minimum Wage by Address and Date MCP server safe to use?
US Minimum Wage by Address and Date scores 60 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 US Minimum Wage by Address and Date MCP server expose?
US Minimum Wage by Address and Date exposes 3 tools: list_capabilities, get_minimum_wage, list_upcoming_minimum_wage_changes. Their descriptions and schemas cost roughly 505 tokens of context every time the server is loaded.
Does the US Minimum Wage by Address and Date MCP server require authentication?
No. We connected to US Minimum Wage by Address and Date without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the US Minimum Wage by Address and Date MCP server still maintained?
US Minimum Wage by Address and Date is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.