Skip to main content
Glama

Related Servers

Alternatives to onet-match

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables querying the O*NET occupation taxonomy, including keyword search, occupation details, skills, and associated tools and technology.
      96 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to resolve occupations into O*NET/ESCO work primitives, audit resumes against ATS gatekeepers, and simulate adversarial hiring committees for deterministic career verification.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables querying U.S. Dept. of Labor CareerOneStop data for occupations, salaries, and salary comparisons across locations.
      94 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to search and retrieve French job profiles, RNCP certifications, training programs, training centers, and skills comparisons in read-only mode without requiring an account.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      US + EU salary benchmarking, pay transparency compliance, and semantic endpoints. 1,400+ US occupations, 28 EU countries. MCP server for AI agents.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables users to search a public job catalog by query, AI level, remote/city/company/recency, retrieve full job records, and look up AI levels for job titles without an API key. It provides read-only access via stdio or a hosted HTTP endpoint.
      MIT

    TDQS

    A4.2/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct roles: match_occupations performs free-text matching and ranking, while get_occupation retrieves a full record by SOC code. There is no realistic overlap or misselection risk because one is discovery and the other is lookup.

    Naming Consistency5/5

    Both names follow the same verb_noun snake_case pattern: match_occupations and get_occupation. The convention is predictable and readable.

    Tool Count4/5

    Two tools is slightly thin relative to the typical 3-15 range, but the server has a narrow purpose and each tool earns its place. Adding more tools would likely be unnecessary unless the server expands beyond matching and record retrieval.

    Completeness4/5

    The surface covers the core workflow: find occupations from free text, then retrieve the full O*NET record for a chosen SOC code. Minor gaps exist, such as no explicit listing or bulk retrieval of SOC codes, but agents can work around this through matching.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues