# Roleset — job postings index (remote · mcp.roleset.io)

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

- Trust score: 70/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `mcp.roleset.io`: 70/100 (this document), [markdown](https://verifymcp.io/servers/io-roleset-jobs/mcp.md), [page](https://verifymcp.io/servers/io-roleset-jobs/mcp)

## Channel facts

- Endpoint: `https://mcp.roleset.io/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `0.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1224 tokens (~204/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 90/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 67% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Roleset — job postings index MCP server?

Roleset — job postings index is a hosted endpoint at https://mcp.roleset.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http io-roleset-jobs 'https://mcp.roleset.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-roleset-jobs": {
      "url": "https://mcp.roleset.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-roleset-jobs": {
      "type": "http",
      "url": "https://mcp.roleset.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-roleset-jobs]
url = "https://mcp.roleset.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-roleset-jobs": {
      "type": "remote",
      "url": "https://mcp.roleset.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-roleset-jobs --url 'https://mcp.roleset.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-roleset-jobs:
    url: "https://mcp.roleset.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-roleset-jobs": {
      "Transport": "http",
      "Url": "https://mcp.roleset.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-roleset-jobs -t streamable-http -u 'https://mcp.roleset.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-roleset-jobs": {
      "type": "http",
      "url": "https://mcp.roleset.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-18 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-14 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-10 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-09 (score 65, 0)

- [cosmetic] “search_jobs” added an optional parameter “listed_since_after”

### 2026-09-08 (score 65, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-07 (score 65)

First indexed and scored.

## MCP tools (6)

### `search_jobs` (~322 tokens)

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.

Input parameters:

- `ats`: Restrict to one ATS platform.
- `company`: Company name, partial match.
- `country`: ISO-3166 alpha-2, e.g. US, DE.
- `cursor`: From a previous meta.next_cursor.
- `department`
- `employment_type`: full_time | part_time | contract | intern | temporary | volunteer
- `include_description` (boolean)
- `limit` (integer)
- `listed_since_after`: ISO-8601. When the company last put the role on the market — it moves when a posting is reopened, so this is the filter for what is on the market now.
- `location`: City or region.
- `posted_after`: ISO-8601 timestamp.
- `q`: Free text over title and description.
- `remote`: Only remote, or only non-remote.
- `title`: Match on the job title.

### `job_changes` (~273 tokens)

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.

Input parameters:

- `ats`
- `company`
- `country`: ISO-3166 alpha-2, e.g. US.
- `cursor`
- `department`: Department, partial match.
- `event`: opened | updated | closed | reopened
- `include_job` (boolean)
- `limit` (integer)
- `remote`: Only remote, or only non-remote.
- `since`: ISO-8601; ignored when cursor is set.
- `title`: Match on the job title.

### `get_job` (~86 tokens)

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.

Input parameters:

- `job_id` (string, required): Roleset job id (UUID) from an earlier result.

### `company_jobs` (~105 tokens)

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.

Input parameters:

- `identifier` (string, required): Domain, ATS board slug, or company name.
- `include_description` (boolean)
- `limit` (integer)

### `hiring_signal` (~106 tokens)

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.

Input parameters:

- `identifier` (string, required): Domain, ATS board slug, or company name.

### `stats` (~72 tokens)

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.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-roleset-jobs/mcp#diagnostics

## Score history

- 2026-09-20: 70
- 2026-09-19: 70
- 2026-09-18: 70
- 2026-09-17: 69
- 2026-09-16: 69
- 2026-09-15: 68
- 2026-09-14: 68
- 2026-09-13: 67
- 2026-09-12: 67
- 2026-09-11: 66
- 2026-09-10: 66
- 2026-09-09: 65
- 2026-09-08: 65
- 2026-09-07: 65

## Common questions

### What is the Roleset — job postings index MCP server?

Roleset — job postings index is an MCP server listed in the public MCP registry as io.roleset/jobs. Search 690k open jobs from official ATS feeds, and what changed since your last check. This page covers its hosted endpoint (https://mcp.roleset.io/mcp).

### Is the Roleset — job postings index MCP server safe to use?

Roleset — job postings index scores 70 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Roleset — job postings index MCP server expose?

Roleset — job postings index exposes 6 tools: search_jobs, job_changes, get_job, company_jobs, hiring_signal, stats. Their descriptions and schemas cost roughly 964 tokens of context every time the server is loaded.

### Does the Roleset — job postings index MCP server require authentication?

No. We connected to Roleset — job postings index without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Roleset — job postings index MCP server still maintained?

Roleset — job postings index is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.roleset.io/mcp
- Authorisation metadata: https://mcp.roleset.io/.well-known/oauth-protected-resource/mcp
- Website: https://roleset.io/
- Changelog RSS feed: https://verifymcp.io/servers/io-roleset-jobs/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-roleset-jobs/mcp.json
- HTML version of this page: https://verifymcp.io/servers/io-roleset-jobs/mcp