_ registry / mcp streamable-http · checked 42m ago

nerolabs-us-minimum-wage

https://us-minimum-wage.nerolabs.workers.dev

Registry code: 5fcc6f7f3519ee8f

api record

Call get_minimum_wage with a street address (best) or a state plus city or county, and a date. It returns the highest rate that legally applies there, which jurisdiction sets it, the tipped cash wage, special industry rates, upcoming increases and the government source for every figure. Use list_upcoming_minimum_wage_changes to plan payroll ahead.

endpoint
https://us-minimum-wage.nerolabs.workers.dev/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is nerolabs-us-minimum-wage live?
Yes — it answered the hub's last check (checked 42m ago). It answered 100% of checks over the last 30 days.
Is nerolabs-us-minimum-wage free to use?
Yes — the hub reached it with no key and no payment.
What tools does nerolabs-us-minimum-wage have?
3 tools: get_minimum_wage, list_capabilities, list_upcoming_minimum_wage_changes.
Is nerolabs-us-minimum-wage safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
129ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 3 tools
2 open 1 never probed 2 of 3 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_capabilities open 42m ago

    Lists coverage (how many states, counties and cities), the date the data was last checked, and related Nero Labs Rules servers. Free.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • list_upcoming_minimum_wage_changes open 42m ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "days": {
          "type": "integer",
          "description": "Window length in days, 1 to 730. Default 365."
        },
        "state": {
          "type": "string",
          "description": "Two-letter state code or name. Optional, all states when left out."
        },
        "from_date": {
          "type": "string",
          "description": "Start of the window, YYYY-MM-DD. Defaults to today."
        }
      },
      "additionalProperties": false
    }
    arguments 18 lines
  • get_minimum_wage unknown 42m ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "city": {
          "type": "string",
          "description": "City name, for example \"Seattle\". Optional."
        },
        "date": {
          "type": "string",
          "description": "Date the work is done, YYYY-MM-DD. Defaults to today. Future dates use rates already scheduled or announced."
        },
        "state": {
          "type": "string",
          "description": "Two-letter state code or name. Needed when no address is given."
        },
        "county": {
          "type": "string",
          "description": "County name, for example \"Montgomery County\". Optional."
        },
        "address": {
          "type": "string",
          "description": "US street address, for example \"100 N Main St, Los Angeles, CA\". Resolved with the US Census Bureau geocoder."
        },
        "industry": {
          "type": "string",
          "description": "Optional, for example \"fast food\", \"hotel\", \"healthcare\". Used to flag special industry rates."
        },
        "employer_size": {
          "type": "integer",
          "description": "Number of employees. Some places set different rates by employer size. Optional."
        },
        "annual_revenue": {
          "type": "number",
          "description": "Employer annual gross sales or receipts in US dollars. A few states (Ohio, Oklahoma, Montana) set a lower rate below a threshold. Optional."
        }
      },
      "additionalProperties": false
    }
    arguments 38 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 5fcc6f7f3519ee8f.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/5fcc6f7f3519ee8f/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/5fcc6f7f3519ee8f/badge.svg)](https://brick.blue/agent/5fcc6f7f3519ee8f?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
70%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.