Skip to main content
Glama
haksanlulz

mcp-wagewatch

by haksanlulz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to mcp-wagewatch

No user-submitted related servers found.

    Related Servers

    • dol-whd

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables querying concluded U.S. Department of Labor Wage & Hour Division enforcement cases, including employer search, case histories, back-wage totals, and dataset coverage.
      MIT

    • DOL WHD MCP

      UHQ-Actual
      F
      license
      B
      quality
      D
      maintenance
      TypeScript MCP server for accessing Department of Labor enforcement data, OSHA inspections, and SAM.gov contract opportunities via natural language queries.
      28
      -

    • mcp-nychousing

      haksanlulz
      A
      license
      A
      quality
      A
      maintenance
      MCP server for NYC housing data, enabling tenant organizers and legal-aid intakes to pull building violations, complaints, ownership, litigation, and evictions. It wraps six city datasets from NYC Open Data.
      6
      11 npm
      MIT

    • WageAPI

      aethar-dev
      A
      license
      Not graded
      quality
      C
      maintenance
      US + EU salary benchmarking, pay transparency compliance, and semantic endpoints. 1,400+ US occupations, 28 EU countries. MCP server for AI agents.
      MIT

    • wgea-mcp

      Bigred97
      A
      license
      A
      quality
      A
      maintenance
      One-call Australian workplace gender data plumbing via WGEA — cited responses for workforce, pay-gap and inclusion analysis, not a data broker.
      6
      122 PyPI
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.2/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: employer_violations searches by employer name, back_wages_summary provides aggregate statistics, violations_by_state lists top cases in a state with optional industry filter, and case_detail gives full details for a specific case. No overlap in functionality.

    Naming Consistency5/5

    All tool names use consistent snake_case format and follow a clear pattern: noun_descriptor (employer_violations, back_wages_summary, case_detail) and noun_by_noun (violations_by_state). There is no mixing of conventions or confusing naming.

    Tool Count5/5

    With 4 tools, the server is well-scoped for the domain of WHD enforcement cases. Each tool serves a necessary function (search, aggregate, state-level view, detail) without being too few or too many.

    Completeness5/5

    The tool surface covers the essential operations for the domain: searching by employer, viewing top cases by state, getting aggregate summaries, and retrieving full case details. There are no obvious gaps or dead ends; the tools work together to provide a complete workflow.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources