
RoleWeek MCP server
Which MCP servers are RoleWeek's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-11-03
- Registry namecom.roleweek/jobsverified in the MCP registry
The registry name sits under roleweek.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-11-03
- Tools5
- Server calls itselfroleweek
- Server version1.1.0
- Protocol version2025-06-18
On 2026-11-03 the server answered initialize and tools/list without a sign-in. First answer in 115 ms.
- Its tools do Browse developer roles posted within the past week; Filter openings by city, remote work, and seniority, but not Save companies and watch for newly listed roles.
- Checked on 1 of the 7 days it takes to judge reliability.
Once connected
- For "Browse developer roles posted within the past week", the likely first call is search_jobs.
- For "Filter openings by city, remote work, and seniority", the likely first call is search_jobs.
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 it2 of 3 use cases
- Answeredmeasuring1 of the 7 daily checks it takes to print a share
- Median first answer121 ms
- Space in an agent's context≈ 2,166 tokensthe definitions of all its tools (5), which an agent carries on every turn
- Tool definitionsA · 100 of 100
- Typed results0 of 5 toolsdeclared outputSchema: results come typed, read once
- Every tool passes all six checks.
What an agent can do with it
- can do · Browse developer roles posted within the past week
- can do · Filter openings by city, remote work, and seniority
- cannot · Save companies and watch for newly listed roles
Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?
Worth a look
None of the five warning signs in these definitions.
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_jobsSearches developer and tech roles that employers posted in the last 7 days, read directly from the employers' own hiring systems (Workday, Greenhouse, Lever, Ashby, iCIMS and others) and checked daily. Covers 35 metro areas in the US and…
get_jobReturns one RoleWeek role by its slug (as returned by search_jobs, or the last part of a roleweek.com/job/<slug>/ URL): employer, location and work mode, level, pay as listed, posted date, the date it leaves RoleWeek, skills mentioned, an…
salary_summaryYearly salary ranges that employers posted in their own job postings, summarised the way RoleWeek's salary and skill pages do, for roles posted in the last 7 days: how many roles list a yearly range, the median bottom and median top of…
company_overviewWhat RoleWeek knows about one employer's open developer roles, from the facts block on its company page: how many roles were posted in the last 7 days, where, role types, levels, how many list a salary and the yearly range, which hiring…
weekly_summaryRoleWeek's weekly report on developer hiring, one finished week (Monday to Sunday, Pacific time) at a time: new developer roles RoleWeek first saw that week, by city, by employer, role type and level, the share that list a salary, the…
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"jobs": {
"type": "http",
"url": "https://roleweek.com/api/mcp?src=mcp-registry"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http roleweek https://roleweek.com/api/mcp?src=mcp-registryclaude.ai, ChatGPT and other clients: add https://roleweek.com/api/mcp?src=mcp-registry as a custom connector in the settings.
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.