Roleset — job postings index

io.rolesetPublished by roleset.ioOfficial publisherv0.1.0Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableWeb Search & Scraping

Overview

AI-generated overview

Lets an assistant search an index of about 690,000 open jobs sourced from official ATS feeds and see what changed since the last check.

What you can do
This remote server exposes a job postings index covering roughly 690,000 open roles drawn from official applicant tracking system feeds. Through it, an assistant can search open jobs and retrieve what has changed since a previous check. The manifest does not list individual tools, so the exact operations are not documented here.
When to use it
Useful when you want an assistant to look up current job openings or track new and changed postings over time without visiting each employer's careers site. Less relevant if you need sources other than official ATS feeds.
Requirements
A remote streamable HTTP endpoint; no local package or runtime is needed. A bearer key is required in the Authorization header. The manifest states a free key can be obtained without an account by posting acceptance of terms to the provider's key endpoint.
Before you install
The Authorization header carries a secret bearer key; keep it private and do not share it. The manifest says a key can be obtained by accepting terms, so review those terms before requesting one. Search queries are sent to the remote provider.

Installation

In SourceWeft

  1. Open Roleset — job postings index in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.roleset%2Fjobs/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "roleset-job-postings-index": {
      "type": "http",
      "url": "https://mcp.roleset.io/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

6

search_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.

Parametersqatslimittitlecursorremotecompanycountrylocationdepartmentposted_afteremployment_type+2 more

job_changes

Job changes since a cursor

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.

Parametersatseventlimitsincetitlecursorremotecompanycountrydepartmentinclude_job

get_job

Get one 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.

Parametersjob_idrequired

company_jobs

Jobs at one company

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.

Parameterslimitidentifierrequiredinclude_description

hiring_signal

Company 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.

Parametersidentifierrequired

stats

Index statistics

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.

Takes no parameters.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

72% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.