Roleset MCP server

• Registry nameio.roleset/jobsverified in the MCP registry

The registry name sits under roleset.io. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-26
• Tools6
• Server calls itselfroleset
• Server version0.1.0
• Protocol version2025-06-18

On 2026-10-26 the server answered initialize and tools/list without a sign-in. First answer in 524 ms.

• Its tools do every use case we checked: List engineering roles opened in the last 24 hours; Search open roles by title, country, and remote status; Check which companies are hiring and in which departments.
• Checked on 1 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 1 so far
• What an agent can do with it3 of 3 use cases
• Answeredmeasuring1 of the 7 daily checks it takes to print a share
• Median first answer548 ms
• Space in an agent's context≈ 1,747 tokensthe definitions of all its tools (6), which an agent carries on every turn
• Tool definitionsB · 75 of 100
• Typed results6 of 6 toolsdeclared outputSchema: results come typed, read once

• Parameters without a description: in 3 of 6
• Not saying whether it only reads or can destroy: 6 of 6

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• 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…

• 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…

• 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…

• 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…

• 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…

• 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…