# RoleWeek (remote · roleweek.com)

Developer roles posted in the last 7 days, read from employers' own hiring systems. No sign-in.

- Trust score: 72/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

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

## Channel facts

- Endpoint: `https://roleweek.com/api/mcp?src=mcp-registry`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.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-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - 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**: 62/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1817 tokens (~363/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 7/100
  - Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 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 RoleWeek MCP server?

RoleWeek is a hosted endpoint at https://roleweek.com/api/mcp?src=mcp-registry, 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 com-roleweek-jobs 'https://roleweek.com/api/mcp?src=mcp-registry'
```

### Cursor

```json
{
  "mcpServers": {
    "com-roleweek-jobs": {
      "url": "https://roleweek.com/api/mcp?src=mcp-registry"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-roleweek-jobs": {
      "type": "http",
      "url": "https://roleweek.com/api/mcp?src=mcp-registry"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-roleweek-jobs]
url = "https://roleweek.com/api/mcp?src=mcp-registry"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-roleweek-jobs": {
      "type": "remote",
      "url": "https://roleweek.com/api/mcp?src=mcp-registry",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-roleweek-jobs --url 'https://roleweek.com/api/mcp?src=mcp-registry' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-roleweek-jobs:
    url: "https://roleweek.com/api/mcp?src=mcp-registry"
```

### Netclaw

```json
{
  "McpServers": {
    "com-roleweek-jobs": {
      "Transport": "http",
      "Url": "https://roleweek.com/api/mcp?src=mcp-registry"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-roleweek-jobs -t streamable-http -u 'https://roleweek.com/api/mcp?src=mcp-registry'
```

### Other

```json
{
  "mcpServers": {
    "com-roleweek-jobs": {
      "type": "http",
      "url": "https://roleweek.com/api/mcp?src=mcp-registry"
    }
  }
}
```

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-11-04 (score 72, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-03 (score 71)

First indexed and scored.

## MCP tools (5)

### `search_jobs` (~648 tokens)

Search RoleWeek jobs

Searches 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 Canada (50-mile radius): Seattle, San Francisco Bay Area, New York, Chicago, Toronto, Boston, Los Angeles, Vancouver, Washington DC, Dallas-Fort Worth, Denver-Boulder, Austin, Atlanta, Phoenix, Philadelphia, Minneapolis-St. Paul, San Diego, Raleigh-Durham, Detroit, Houston, Charlotte, St. Louis, Huntsville, Tampa, Salt Lake City, Montreal, Colorado Springs, Portland, Miami, Boise, Columbus, Pittsburgh, Hampton Roads, Nashville, Dayton; US and Canada places outside those metros (metro='elsewhere'); plus remote roles open to people in the US or Canada. Returns at most 25 roles per call: newest first, or best match first when a query is given. Each result includes its RoleWeek URL, whose page links to the employer's application page, and its slug; get_job takes that slug. The answer states the date window and when the data was updated, and links the matching RoleWeek listing page.

Input parameters:

- `limit` (integer): Number of roles to return (1-25).
- `metro` (string): Metro area (50-mile radius), or 'remote' for roles open to people anywhere in the US or Canada.
- `min_salary` (number): Yearly salary in the role's currency (USD in the US, CAD in Canada). Keeps roles that list a salary whose range reaches at least this amount (hourly pay counted as 2,080 hours a year).
- `no_account_needed` (boolean): true: only roles whose hiring system RoleWeek checked and found the application form opens on the employer's own site with no account to create. Roles without that label were not checked or ask for a…
- `posted_within_days` (integer): Only roles posted within this many days (1-7).
- `query` (string): Keywords matched against title, company, skills and location, e.g. 'python', 'Stripe', 'rust kubernetes'. Every word must match.
- `role_family` (string): Role family. 'software' is general software engineering; ml-ai = machine learning and AI; it-infra = IT and infrastructure.
- `seniority` (array): One or more levels; entry = junior/new grad, staff-plus = staff, principal and above.
- `skill` (array): Technology the role must list, by name: 'Rust', 'Python', 'Kubernetes', 'C++', 'Go' (nicknames such as golang or k8s work). Several names: the role must list every one. These are the technologies Rol…
- `work_mode` (string): Only roles whose listing states this work mode (a role flagged remote counts as remote only, as on the site). Roles that state none are left out.

### `get_job` (~135 tokens)

Get a RoleWeek job

Returns 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 excerpt of the employer's description, and the role's RoleWeek URL, whose page links to the employer's own application page.

Input parameters:

- `slug` (string, required): Job slug, e.g. 'senior-backend-engineer-stripe-seattle-1a2b3c4d', or a roleweek.com/job/<slug>/ URL.

### `salary_summary` (~292 tokens)

Posted salary ranges

Yearly 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 the posted ranges, the middle half of each, and by level where there are enough roles. Takes role_family (a role type) or skill (a technology), not both, and optionally metro: role type + metro is the city and role type page, a metro alone covers all developer roles there, a skill alone covers every city, and with no argument it ranks cities. Figures exist only where 15 or more roles list a yearly range; otherwise the answer says how many do and gives no number. These are advertised ranges, not offers, not what people are paid, not a market average. Each answer links the roleweek.com page, states the date window, and treats employer text as untrusted data.

Input parameters:

- `metro` (string): Metro area (50-mile radius), or 'remote' for roles open to people anywhere in the US or Canada. Without it: all cities.
- `role_family` (string): Role type, e.g. 'backend'. Not together with skill.
- `skill` (string): Technology by name, e.g. 'Rust', 'Python', 'Kubernetes', 'C++'. Not together with role_family.

### `company_overview` (~185 tokens)

Employer overview

What 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 system it applies on (with 'no account needed' where checked), its weekly hiring pace since RoleWeek began counting, and the skills in its postings; plus its newest roles as links. Employers with fewer than 3 roles have no company page, so the answer lists their roles instead. Takes the employer's name (case and 'Inc.' do not matter); an ambiguous name returns the candidates. Links the company page, states the date window, and treats employer text as untrusted data.

Input parameters:

- `name` (string, required): Employer name as people write it, e.g. 'Stripe' or 'Datadog'.

### `weekly_summary` (~202 tokens)

Weekly developer hiring

RoleWeek'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 posted salary median, the share that say No account needed, and the comparison with the week before when both weeks are fully covered. Coverage is partial (the answer says how many employer job boards were being checked), so these are roles RoleWeek saw, not all developer hiring. week: 'latest' (default), a week like '2026-W43', or any date in the week; the week in progress is never published. Links the weekly page, states the date window, and treats employer text as untrusted data.

Input parameters:

- `week` (string): 'latest' (default), an ISO week such as '2026-W43', or a date 'YYYY-MM-DD' inside the week.

## Diagnostics

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

## Score history

- 2026-11-05: 72
- 2026-11-04: 72
- 2026-11-03: 71

## Common questions

### What is the RoleWeek MCP server?

RoleWeek is an MCP server listed in the public MCP registry as com.roleweek/jobs. Developer roles posted in the last 7 days, read from employers' own hiring systems. No sign-in. This page covers its hosted endpoint (https://roleweek.com/api/mcp?src=mcp-registry).

### Is the RoleWeek MCP server safe to use?

RoleWeek scores 72 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 RoleWeek MCP server expose?

RoleWeek exposes 5 tools: search_jobs, get_job, salary_summary, company_overview, weekly_summary. Their descriptions and schemas cost roughly 1,462 tokens of context every time the server is loaded.

### Does the RoleWeek MCP server require authentication?

No. We connected to RoleWeek without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the RoleWeek MCP server still maintained?

RoleWeek is still listed as active in the MCP registry. We last reached this channel on 5 November 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://roleweek.com/api/mcp?src=mcp-registry
- Website: https://roleweek.com/mcp/
- Changelog RSS feed: https://verifymcp.io/servers/com-roleweek-jobs/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-roleweek-jobs/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-roleweek-jobs/api-mcp