# RoleDawn > New role families seen on public ATS job boards (SDR, RevOps...), company jobs, app reviews. - name: com.roledawn/mcp - version: 0.4.0 - connection class: R0 (autonomous) - trust: 82/100 flags: no-repository - quality: 80/100 (good) - owner: not claimed - descriptor: https://api.protogrid.dev/v1/servers/com.roledawn%2Fmcp - tools: https://api.protogrid.dev/v1/servers/com.roledawn%2Fmcp/tools **An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe. ## Connection (mcpServers) ```json { "mcpServers": { "roledawn": { "type": "http", "url": "https://roledawn.com/mcp" } } } ``` ## Trust - hygiene: 80 - liveness: 99 - freshness: 100 - provenance: 55 - drivers: +dns-namespace +website +reachable +uptime-98% +updated-9d-ago -no-repository - Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. ## Quality 80/100 (good) ### protocol: 75 (weight 25) - warn `protocol.modern`: newest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28 - n/a `protocol.stateless`: only applies to 2026-07-28 servers - pass `protocol.transport`: streamable HTTP - n/a `protocol.list_ttl`: only applies to 2026-07-28 servers ### authorization: n/a (weight 15) - n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth - n/a `auth.secret_in_url`: no templated URL ### tool hygiene: 100 (weight 30) - pass `tools.descriptions`: every tool has a description - pass `tools.description_length`: descriptions are concise - pass `tools.schemas`: every tool has an object input schema - pass `tools.annotations`: 4 of 4 tools declare readOnlyHint or destructiveHint - pass `tools.directory_hints`: every tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHint - pass `tools.token_cost`: about 1,678 tokens to load every tool - pass `tools.api_dump`: tools are not a one-to-one API dump ### stability: 50 (weight 15) - pass `stability.changes`: 5 tool changes in 30 days - fail `stability.rug_pull`: 1 tools kept their name but changed most of their description in 30 days; review before trusting them ### dependencies: n/a (weight 15) - n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package - tools: 4, about 1,678 tokens to load them all - tool set hash: 1993751522ec27aa7f0b8f3a86220b2a - tools last changed: 2026-10-11T20:52:16.669Z - badge: [![protogrid quality](https://protogrid.dev/badge/com.roledawn/mcp.svg)](https://protogrid.dev/servers/com.roledawn/mcp) - Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. ### Tool changes - 2026-10-11 `list_hiring_signals` changed (title, description, inputSchema) **meaning changed** - before: Use when the user wants companies to prospect or watch because they just began hiring for a function, e.g. "companies hiring their first SDR this week" or "who started a RevOps or security team". Returns up to 20 companies per call, each with job title, location, job URL, posted and detected dates. first_hire = first role of that family on their own careers page; surge = clearly more roles than the prior 30 days. For one known company's jobs use list_company_jobs. - after: 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. - 2026-10-10 `list_app_reviews` changed (title, description) - before: List the recent reviews shown on an App Store or Google Play app page: rating, title, text, date, app version, thumbs-up and developer reply (Google Play). Filter by star rating, sort, and page. Useful for complaint and feature-request research and competitor monitoring. About 10 (App Store) or 20 (Google Play) reviews per country/language. - after: 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. - 2026-10-10 `get_app` changed (title, description, inputSchema) - before: Get one App Store or Google Play app: title, developer, rating, ratings count, star histogram, price, installs (Google Play), version, release notes, release and update dates, genre, content rating and description. id = numeric App Store id, Android package name, or the full store URL. - after: 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. - 2026-10-10 `list_company_jobs` changed (title, description, inputSchema) - before: List the open jobs on one company's public Greenhouse, Lever or Ashby job board, newest first: title, location, department, remote flag, job URL and posting date. company = the job-board slug from the careers URL (boards.greenhouse.io/, jobs.lever.co/, jobs.ashbyhq.com/). If a slug is not found on one ATS, try the other two. Page with offset = next_offset. - after: 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. - 2026-10-10 `list_hiring_signals` changed (title, description, inputSchema) - before: Find companies that just started hiring in a role family - first_hire = the family is new on their own careers page (e.g. their first SDR, RevOps or security role); surge = clearly more roles than the previous 30 days. Each row has company, job title, location, job URL, posted and detected dates. Use it for sales prospecting and market research. Returns the top 20 companies per query (the full list is the RoleDawn Weekly List). - after: Use when the user wants companies to prospect or watch because they just began hiring for a function, e.g. "companies hiring their first SDR this week" or "who started a RevOps or security team". Returns up to 20 companies per call, each with job title, location, job URL, posted and detected dates. first_hire = first role of that family on their own careers page; surge = clearly more roles than the prior 30 days. For one known company's jobs use list_company_jobs. Full history: https://api.protogrid.dev/v1/servers/com.roledawn%2Fmcp/changes ## Remotes - https://roledawn.com/mcp (streamable-http, auth none, reachable true, uptime30d 0.98039216) ## Packages _none_ ## Tools (4) - `get_app`: 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. - `list_app_reviews`: 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. - `list_company_jobs`: 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. - `list_hiring_signals`: 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.