Roleset — job postings index
REMOTE · MCP.ROLESET.IO · SCANNED SEP 20
Search 690k open jobs from official ATS feeds, and what changed since your last check.
Available components
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability67
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
- Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage90
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 67% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
remote · mcp.roleset.io
claude mcp add --transport http io-roleset-jobs 'https://mcp.roleset.io/mcp'
{
"mcpServers": {
"io-roleset-jobs": {
"url": "https://mcp.roleset.io/mcp"
}
}
} {
"servers": {
"io-roleset-jobs": {
"type": "http",
"url": "https://mcp.roleset.io/mcp"
}
}
} [mcp_servers.io-roleset-jobs] url = "https://mcp.roleset.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-roleset-jobs": {
"type": "remote",
"url": "https://mcp.roleset.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-roleset-jobs --url 'https://mcp.roleset.io/mcp' --transport streamable-http
mcp_servers:
io-roleset-jobs:
url: "https://mcp.roleset.io/mcp" {
"McpServers": {
"io-roleset-jobs": {
"Transport": "http",
"Url": "https://mcp.roleset.io/mcp"
}
}
} assistant mcp add io-roleset-jobs -t streamable-http -u 'https://mcp.roleset.io/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 18 Sept 26 +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.
- 16 Sept 26 +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.
- 14 Sept 26 +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.
- 12 Sept 26 +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.
- 10 Sept 26 +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.
- 9 Sept 26 0
- “search_jobs” added an optional parameter “listed_since_after” cosmetic
1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.
- 8 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 7 Sept 26 65
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://mcp.roleset.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.roleset.io | CN=YE1,O=Let's Encrypt,C=US | 6 Sept 2026 | 5 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 65bf4ce0ad6403ca090ed0c1b331e1c4a22 |
| SANs: mcp.roleset.io | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.roleset.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| roleset.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.roleset.io/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.roleset.io/mcp | HTTPS enforced | 308 | https://mcp.roleset.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
company_jobs Jobs at one company ~105
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.
| Name | Type | Req | Description |
|---|---|---|---|
| identifier | string | yes | Domain, ATS board slug, or company name. |
| include_description | boolean | – | – |
| limit | integer | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_job Get one job ~86
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.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | Roleset job id (UUID) from an earlier result. |
Structured output declared, but exposes no named fields.
No examples provided.
hiring_signal Company hiring signal ~106
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.
| Name | Type | Req | Description |
|---|---|---|---|
| identifier | string | yes | Domain, ATS board slug, or company name. |
Structured output declared, but exposes no named fields.
No examples provided.
job_changes Job changes since a cursor ~273
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
Structured output declared, but exposes no named fields.
No examples provided.
search_jobs Search jobs ~322
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
Structured output declared, but exposes no named fields.
No examples provided.
stats Index statistics ~72
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.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
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.