RoleDawn
REMOTE · ROLEDAWN.COM
New role families seen on public ATS job boards (SDR, RevOps...), company jobs, app reviews.
Available components
Last scanned (10 hours ago)
Scores higher than 89% of remote servers
Reachable. Last reached 5 Nov 2026.
Category CRM and Sales
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- 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 Usability62
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 4 Nov 26 +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.
- 2 Nov 26 +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.
- 31 Oct 26 +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.
- 28 Oct 26 +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.
- 26 Oct 26 +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.
- 24 Oct 26 +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.
- 22 Oct 26 +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.
- 20 Oct 26 +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.
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 5 Nov 2026 · Probed https://roledawn.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=roledawn.com | CN=WE1,O=Google Trust Services,C=US | 7 Oct 2026 | 5 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 3431f2291bceb9250e7a21df90d362d5 |
| SANs: roledawn.com, honesthaul.roledawn.com, *.honesthaul.roledawn.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of roledawn.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| roledawn.com. | 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 |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://roledawn.com/mcp | Verified | 200 | |
| http (plaintext) | http://roledawn.com/mcp | HTTPS enforced | 301 | https://roledawn.com/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 →
get_app Get an App Store / Google Play app listing (rating, installs, version) ~209
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.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Two-letter store country, default us. |
| id | string | yes | 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). |
No output schema declared.
No examples provided.
list_app_reviews Read App Store / Google Play reviews (complaints, feature requests) ~237
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.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Two-letter store country, default us. |
| id | string | yes | 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. |
No output schema declared.
No examples provided.
list_company_jobs List one company's open jobs (Greenhouse, Lever, Ashby) ~260
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ats | string | yes | Applicant tracking system that hosts the job board. Unknown? Try greenhouse, then lever, then ashby. |
| company | string | yes | 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. |
No output schema declared.
No examples provided.
list_hiring_signals Find companies with a new role family on their job board (sales triggers) ~438
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.
| Name | Type | Req | Description |
|---|---|---|---|
| family | array | yes | 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… |
No output schema declared.
No examples provided.
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.
remote · roledawn.com
claude mcp add --transport http com-roledawn-mcp 'https://roledawn.com/mcp'
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.