onet-match
Related Servers
Alternatives to onet-match
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables querying the O*NET occupation taxonomy, including keyword search, occupation details, skills, and associated tools and technology.96 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables 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
- AlicenseNot gradedqualityBmaintenanceEnables querying U.S. Dept. of Labor CareerOneStop data for occupations, salaries, and salary comparisons across locations.94 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables 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
- AlicenseNot gradedqualityDmaintenanceUS + EU salary benchmarking, pay transparency compliance, and semantic endpoints. 1,400+ US occupations, 28 EU countries. MCP server for AI agents.MIT
- AlicenseNot gradedqualityCmaintenanceEnables 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
Scored across 2 tools
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.
Both names follow the same verb_noun snake_case pattern: match_occupations and get_occupation. The convention is predictable and readable.
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.
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.