Model Context Protocol (MCP) server for Apollo.io API integration
Nothing to run from here
RoleDawn is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
4
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
New role families seen on public ATS job boards (SDR, RevOps...), company jobs, app reviews.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http roledawn-mcp https://roledawn.com/mcp
# 2 — ask your agent for something these tools do
# list_hiring_signals, list_company_jobs, get_app and 1 more
RoleDawn costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
ROAll 1 server
roledawn1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http roledawn-mcp https://roledawn.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
4 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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 (fo
| Parameter | Type | Required | Notes |
|---|---|---|---|
| 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-e |
| since | string | no | Detected in the last 7, 14 or 30 days. Default 7d. |
| type | string | no | 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 = hir |
| limit | integer | no | Companies per page (1-20). Default 20. |
| offset | integer | no | Companies to skip; use next_offset from the previous result. |
| include_closed | boolean | no | true = also return signals whose job post has since closed (still_open=false). Default false. |
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 othe
| Parameter | Type | Required | Notes |
|---|---|---|---|
| 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. |
| remote | boolean | no | true = only remote jobs, false = only non-remote jobs. Omit for all. |
| q | string | no | Text that must appear in the job title, e.g. engineer. |
| location | string | no | Text that must appear in the location, e.g. London. |
| limit | integer | no | Jobs per page (1-500). Default 25. |
| offset | integer | no | Jobs to skip; use next_offset from the previous result. |
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), v
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | App Store id (e.g. 324684580), package name (e.g. com.spotify.music) or store URL. |
| store | string | no | Optional; inferred from id (numeric = apple, package name = google). |
| country | string | no | Two-letter store country, default us. |
| lang | string | no | Google Play language, e.g. en, de, pt-BR. Default en. |
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,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | App Store id, package name or store URL. |
| store | string | no | Optional; inferred from id. |
| country | string | no | Two-letter store country, default us. |
| lang | string | no | Google Play language, default en. |
| rating | array | no | Only these star ratings, e.g. [1,2]. |
| sort | string | no | Default newest. |
| limit | integer | no | Reviews per page (1-50). Default 20. |
| offset | integer | no | Reviews to skip; use next_offset. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install RoleDawn or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.4.0.
0.4.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish RoleDawn can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.