mcpbeat

O*NET Occupational Data MCP Server

com.olyport/onet
answering

O*NET Occupational Data is answering right now. Last checked moments ago. It exposes 4 tools.

Job descriptions, skills, education requirements, and wage data

Uptime history 40 hours of history
40 hours agonow
100.0%
Uptime 24h
92 of 92 checks
4
Tools
read from the server
529 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 0 min ago.

run in your terminal
claude mcp add onet --transport http https://mcp.olyport.com/onet/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "onet": {
      "url": "https://mcp.olyport.com/onet/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.onet]
url = "https://mcp.olyport.com/onet/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "onet": {
      "url": "https://mcp.olyport.com/onet/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "onet": {
      "url": "https://mcp.olyport.com/onet/mcp"
    }
  }
}

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

occupation
get_occupation_detail
Get detailed information about an O*NET occupation. Returns comprehensive data including description, skills, knowledge areas, abilities, work activities, technology skills, and education requirements. Args: soc_code: The O*NET-SOC code (e.g. '15-1252.00' for Software Developers, '29-1141.00' for Registered Nurses).
get_occupation_wages
Get wage and salary estimates for an O*NET occupation. Returns median, 10th, 25th, 75th, and 90th percentile wages, both hourly and annual. Can be filtered by location. Args: soc_code: The O*NET-SOC code (e.g. '15-1252.00' for Software Developers). location: Optional location filter — state name or 'National' (default: national).
career
get_career_outlook
Get employment projections and career outlook for an O*NET occupation. Returns projected job growth rate, employment numbers, projected openings, and an outlook summary (bright, average, or below average). Args: soc_code: The O*NET-SOC code (e.g. '15-1252.00' for Software Developers).
occupations
search_occupations
Search O*NET occupations by keyword. Returns a list of occupations matching the keyword with their SOC codes, titles, and relevance scores. Use the SOC code from results with other O*NET tools to get detailed information. Args: keyword: Search term (e.g. 'software developer', 'nurse', 'electrician'). limit: Maximum number of results to return (default 25).

Endpoints

URLTransportStateLatencyChecked
https://mcp.olyport.com/onet/mcp streamable-http answering 569 ms 0 min ago

O*NET Occupational Data — questions

Answers built from our own checks of this server.

What can O*NET Occupational Data do?
It exposes 4 tools, read directly from the server on our last check. Among them: get_career_outlook, get_occupation_detail, get_occupation_wages, search_occupations. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is O*NET Occupational Data working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 529 ms. The bar chart above shows every period we have measured.
How do I connect O*NET Occupational Data?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does O*NET Occupational Data need an API key?
No. O*NET Occupational Data completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is O*NET Occupational Data?
It answers our handshake in 529 ms on average, which is faster than 20% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.