mcpbeat Sign in

Roleset — job postings index MCP Server

answering

Roleset — job postings index is answering right now. Last checked 9 min ago. It exposes 6 tools.

Search 690k open jobs from official ATS feeds, and what changed since your last check.

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

What changed 1

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 8 September 2026. No other catalogue keeps this.

8 Sep a tool changed the parameters it asks for search_jobs

Nothing serious here today

Today is the operative word: we check Roleset — job postings index every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

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

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

Available tools 6

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

job
get_job
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.
job_changes
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.
company
company_jobs
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.
hiring
hiring_signal
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.
jobs
search_jobs
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.
stats
stats
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.

Endpoints

URLTransportStateLatencyChecked
https://mcp.roleset.io/mcp streamable-http answering 142 ms 9 min ago

Alternatives to Roleset — job postings index

same job, measured the same way
Logobaker
by logobaker

Search logos, browse feeds and blogs, check your stats — from your AI chat.

answering
Jobo Job Search
by jobo

Search a live index of millions of open jobs from employer career sites and 100+ ATS platforms.

20 installs/wk answering
JobsPipe
by jobspipe

Live job postings from 30+ ATS feeds and job boards, one schema. Live results need a Bearer key.

4 tools answering
Legalize
by legalize

Official MCP connector for Legalize: read and search its whole open corpus, at any point in time.

7 tools answering
A
Google Search Console
by b77

Search rankings, clicks, and indexing for your site — in chat.

answering
C
MCPFax Feed Reader
by mcpscores

What a source published since you last looked, from any RSS, RDF or Atom feed.

4 tools answering
SourceActs
by sourceacts

Official EUR-Lex, UK, US, and gazette search, metadata fetch, and change-only watches.

answering
Intermediair Jobs
by intermediair-www

Search and retrieve job postings on Intermediair (read-only).

2 tools answering

Roleset — job postings index — questions

Answers built from our own checks of this server.

What can Roleset — job postings index do?
It exposes 6 tools, read directly from the server on our last check. Among them: company_jobs, get_job, hiring_signal, job_changes, search_jobs, stats. 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 Roleset — job postings index 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 77 ms. The bar chart above shows every period we have measured.
How do I connect Roleset — job postings index?
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 Roleset — job postings index need an API key?
No. Roleset — job postings index completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 6 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Roleset — job postings index?
It answers our handshake in 77 ms on average, which is faster than 88% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.