# RoleDawn (remote · roledawn.com)

New role families seen on public ATS job boards (SDR, RevOps...), company jobs, app reviews.

- Trust score: 84/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

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

## Channel facts

- Endpoint: `https://roledawn.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.4.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 1416 tokens (~354/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 93/100
  - Stability observed for 28 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the RoleDawn MCP server?

RoleDawn is a hosted endpoint at https://roledawn.com/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 com-roledawn-mcp 'https://roledawn.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-roledawn-mcp": {
      "url": "https://roledawn.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-roledawn-mcp": {
      "type": "http",
      "url": "https://roledawn.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-roledawn-mcp]
url = "https://roledawn.com/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add com-roledawn-mcp --url 'https://roledawn.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-roledawn-mcp:
    url: "https://roledawn.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-roledawn-mcp": {
      "Transport": "http",
      "Url": "https://roledawn.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-roledawn-mcp -t streamable-http -u 'https://roledawn.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-roledawn-mcp": {
      "type": "http",
      "url": "https://roledawn.com/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-11-04 (score 84, +1)

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

### 2026-11-02 (score 83, +1)

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

### 2026-10-31 (score 82, +1)

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

### 2026-10-28 (score 81, +1)

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

### 2026-10-26 (score 80, +1)

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

### 2026-10-24 (score 79, +1)

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

### 2026-10-22 (score 78, +1)

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

### 2026-10-20 (score 77, +1)

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

## MCP tools (4)

### `list_hiring_signals` (~438 tokens)

Find companies with a new role family on their job board (sales triggers)

Use when the user wants companies to prospect because a role in a function is new on their job board, e.g. "companies that started hiring SDRs this week". Up to 20 companies per call, each with job URL, ATS posting date, our first-seen and detection times and what we saw before. first_hire = first role of the family seen on their board since we began tracking it, not proof of a first-ever hire (founding_evidence quotes the company); surge = hiring jump. For one company: list_company_jobs.

Input parameters:

- `family` (array, required): Role family ids (1-5). Common: sdr (SDR/BDR), sales (AEs), revops, customer-success, marketing, security, data-engineering, ml-ai. All ids: sdr, sales, revops, sales-enablement, marketing-ops, sales-…
- `include_closed` (boolean): true = also return signals whose job post has since closed (still_open=false). Default false.
- `limit` (integer): Companies per page (1-20). Default 20.
- `offset` (integer): Companies to skip; use next_offset from the previous result.
- `since` (string): Detected in the last 7, 14 or 30 days. Default 7d.
- `type` (string): first_hire (default) = first role of the family RoleDawn has observed on the board since tracking it (observed) or inferred on its first read (inferred), not the company's first hire ever; surge = hi…

### `list_company_jobs` (~260 tokens)

List one company's open jobs (Greenhouse, Lever, Ashby)

Use when the user names a company and wants its current open roles, e.g. "is Stripe hiring engineers in London?" or "list this company's remote jobs". Reads the public Greenhouse, Lever or Ashby job board and returns title, location, department, remote flag, job URL and posting date, newest first. company = board slug (stripe in boards.greenhouse.io/stripe); if not found on one ATS, retry the other two. For companies newly hiring across the market use list_hiring_signals.

Input parameters:

- `ats` (string, required): Applicant tracking system that hosts the job board. Unknown? Try greenhouse, then lever, then ashby.
- `company` (string, required): Job-board slug from the careers URL, e.g. stripe.
- `limit` (integer): Jobs per page (1-500). Default 25.
- `location` (string): Text that must appear in the location, e.g. London.
- `offset` (integer): Jobs to skip; use next_offset from the previous result.
- `q` (string): Text that must appear in the job title, e.g. engineer.
- `remote` (boolean): true = only remote jobs, false = only non-remote jobs. Omit for all.

### `get_app` (~209 tokens)

Get an App Store / Google Play app listing (rating, installs, version)

Use when the user asks about one mobile app's store listing - rating, ratings count, installs, price, latest version or release notes - e.g. "what is Spotify's Google Play rating?". id = App Store numeric id (324684580), Android package name (com.spotify.music) or the store URL; the store is inferred. Returns title, developer, rating, star histogram, ratings count, price, installs (Google Play), version, release notes, dates, genre and description. For what users say, use list_app_reviews.

Input parameters:

- `country` (string): Two-letter store country, default us.
- `id` (string, required): App Store id (e.g. 324684580), package name (e.g. com.spotify.music) or store URL.
- `lang` (string): Google Play language, e.g. en, de, pt-BR. Default en.
- `store` (string): Optional; inferred from id (numeric = apple, package name = google).

### `list_app_reviews` (~237 tokens)

Read App Store / Google Play reviews (complaints, feature requests)

Use when the user wants what people say about an app - complaints, bugs, feature requests, competitor research - e.g. "recent 1- and 2-star reviews of WhatsApp in the UK App Store". Returns the reviews shown on the store page (about 10 per App Store country, 20 per Google Play language) with rating, title, text, date, app version, thumbs-up and developer reply (Google Play). Filter with rating=[1,2], sort and country; page with offset. For ratings and metadata use get_app.

Input parameters:

- `country` (string): Two-letter store country, default us.
- `id` (string, required): App Store id, package name or store URL.
- `lang` (string): Google Play language, default en.
- `limit` (integer): Reviews per page (1-50). Default 20.
- `offset` (integer): Reviews to skip; use next_offset.
- `rating` (array): Only these star ratings, e.g. [1,2].
- `sort` (string): Default newest.
- `store` (string): Optional; inferred from id.

## Diagnostics

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

## Score history

- 2026-11-05: 84
- 2026-11-04: 84
- 2026-11-03: 83
- 2026-11-02: 83
- 2026-11-01: 82
- 2026-10-31: 82
- 2026-10-30: 81
- 2026-10-29: 81
- 2026-10-28: 81
- 2026-10-27: 80
- 2026-10-26: 80
- 2026-10-25: 79
- 2026-10-24: 79
- 2026-10-23: 78
- 2026-10-22: 78
- 2026-10-21: 77
- 2026-10-20: 77
- 2026-10-19: 76
- 2026-10-18: 76
- 2026-10-17: 75
- 2026-10-16: 75
- 2026-10-15: 74
- 2026-10-14: 74
- 2026-10-13: 74
- 2026-10-12: 73
- 2026-10-10: 73

## Common questions

### What is the RoleDawn MCP server?

RoleDawn is an MCP server listed in the public MCP registry as com.roledawn/mcp. New role families seen on public ATS job boards (SDR, RevOps...), company jobs, app reviews. This page covers its hosted endpoint (https://roledawn.com/mcp).

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

RoleDawn scores 84 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 RoleDawn MCP server expose?

RoleDawn exposes 4 tools: list_hiring_signals, list_company_jobs, get_app, list_app_reviews. Their descriptions and schemas cost roughly 1,144 tokens of context every time the server is loaded.

### Does the RoleDawn MCP server require authentication?

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

### Is the RoleDawn MCP server still maintained?

RoleDawn 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://roledawn.com/mcp
- Website: https://roledawn.com/api#mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-roledawn-mcp/roledawn.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-roledawn-mcp/roledawn.json
- HTML version of this page: https://verifymcp.io/servers/com-roledawn-mcp/roledawn