Roleset — job postings index MCP server

• company_jobsFree

  Every open posting at one company. Accepts a domain (acme.com), an ATS board slug, or the company name. Use when the company is already known and you want its roles; use search_jobs when you are looking across companies. For whether the company is growing rather than what it has open, use hiring_signal.

• get_jobFree

  Fetch a single posting by its Roleset id, including the full description text and HTML. Use after search_jobs or job_changes when you need the body of a specific posting — for summarising requirements, or checking whether a role matches a candidate's constraints. The id comes from an earlier result.

• hiring_signalFree

  Whether a company is hiring, and where. Returns open roles broken down by department plus how many opened and closed over the last 7 and 30 days, and the net change. Use for sales and research questions — 'is this company growing', 'are they building out engineering', 'did they stop hiring' — where counts and trend matter more than the individual postings. One call, not per record.

• job_changesFree

  What has opened, changed, closed or reopened in the index. This is the tool to poll: pass `since` (ISO-8601) the first time, then keep passing the returned `meta.next_cursor` and you will see each event exactly once, with no gaps or repeats. Filter it the same way you would a search — by department, country, remote, title, company or ATS — to subscribe to one slice of the market. Each event carries the event type, when it happened, a `diff` showing which fields changed and their before/after values, and the job record itself. Use this to track a hiring market over time, to answer 'what's new since yesterday', or to keep a downstream store in sync. Defaults to the last 24 hours.

• search_jobsFree

  Search the index of open job postings. Use for a one-off question about the job market: who is hiring for a role, what is open in a city or country, which companies have remote positions. Returns a page of job records plus a `meta.next_cursor` to continue; each record has title, company, structured locations, remote flag, employment type, salary when the board publishes one, and an apply URL. Descriptions are omitted unless `include_description` is set, because they are large. To find what has *changed* since you last looked, use job_changes instead — do not poll this tool in a loop.

• statsFree

  Size and freshness of the whole index: companies, boards per ATS, open and total postings, events in the last 24 hours, and when the oldest active board was last crawled. Free. Use to tell a user how much coverage stands behind an answer, or to check the index is current before relying on it.

• –Code scanremote-only server, no package to scann/a
• Live reliabilityremote reachable in 1678ms20/20
• Tool poisoning6 tool descriptions checked15/15
• Auth qualityAPI key sent as a header8/15
• Maintenanceno repository listed3/15
• Maintainer identityverified namespace with website, no repo4/10

Roleset — job postings index: common questions

Is Roleset — job postings index MCP server safe?

With care: it is graded C, so read the findings first (67/100). Read the Roleset — job postings index safety report

How do I install Roleset — job postings index?

It runs remotely at mcp.roleset.io. Add it to Claude Code, Claude Desktop or Cursor with the snippets above, or call it through the mcp.market gateway without installing anything.

Does Roleset — job postings index need an API key?

Yes. The registry entry asks for Authorization.

Is Roleset — job postings index maintained?

The latest release is v0.1.0.

Is Roleset — job postings index up?

100% of our last 5 checks got an answer. We check remote servers about four times a day.

What can I use instead of Roleset — job postings index?

Servers from other publishers that do the same job: Jobseek MCP server, Trackly CLI MCP server and HasData Yelp MCP server. Compare all Roleset — job postings index alternatives.