US Minimum Wage by Address and Date (bulk, Apify)

io.github.Nero-EnginePublished by GitHub account Nero-Enginev1.0.0Updated Oct 24, 2026

Bulk US minimum wage lookups by address, city or state and date, per lookup billing via Apify.

The publisher's own server: Apify MCP Server

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Looks up US minimum wage rates by address, city, or state and date through a hosted Apify endpoint.

What you can do
This remote MCP server exposes bulk US minimum wage lookups. An assistant can query wage rates for a given address, city, or state and a given date, and run these lookups in bulk. It is hosted at the Apify MCP endpoint, so no local package is installed.
When to use it
Useful when an assistant needs current or historical US minimum wage figures tied to a specific location and date, for example in payroll, compliance, or research workflows that involve many locations at once.
Requirements
A remote connection to the Apify MCP endpoint over streamable HTTP. An Apify API token is required, sent in the Authorization header as a Bearer token. Network access is needed.
Before you install
The Authorization header carries an Apify API token, which is a secret and should be kept private. Runs are billed per event to your Apify account, so bulk lookups can incur costs. Lookups send the queried addresses, cities, or states to Apify.

Installation

In SourceWeft

  1. Open US Minimum Wage by Address and Date (bulk, Apify) in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Nero-Engine%2Fus-minimum-wage-full/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "us-minimum-wage-by-address-and-date-bulk": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=nerolabs/us-minimum-wage"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 10, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Apify integrations