Model Context Protocol (MCP) server for Apollo.io API integration
Nothing to run from here
Gtm Job Discovery 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.
96/100
trust score
19
downloads a day
local
runs on your machine
484
downloads in 30d
What it does
Find companies hiring for your role keywords across job boards, with one firmographic row per posting.
All of the work runs on Mamba Labs actors on Apify. This server is a thin client: it starts the run, waits for it, and hands back the results. Add it to Claude, Cursor, or any MCP client with one npx line and your own APIFY_TOKEN.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --env 'APIFY_TOKEN=${APIFY_TOKEN}' --transport stdio gtm-job-discovery-mcp '--' npx -y @mambalabsdev/mcp-gtm-job-discovery
# 2 — ask your agent for something these tools do
# monitor_job_postings
It needs APIFY_TOKEN: this reads it from your environment, so export it first.
Gtm Job Discovery costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publisher
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Gtm Job Discovery as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. Claude Code reads APIFY_TOKEN (Apify API token from https://console.apify.com/account/integrations) from your environment each time it starts the server, so the value stays out of its config: export it in your shell profile (macOS, Linux), or run setx APIFY_TOKEN … and open a new terminal (Windows). The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user --env 'APIFY_TOKEN=${APIFY_TOKEN}' --transport stdio gtm-job-discovery-mcp '--' npx -y @mambalabsdev/mcp-gtm-job-discoveryReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
It reaches a system of yours, so it needs your own credential rather than the publisher’s: APIFY_TOKEN — Apify API token from https://console.apify.com/account/integrations. You set it in your own client’s config, on your machine — this marketplace never holds it.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
1 tool, 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.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Find companies that are hiring for a set of role keywords across public job boards, and return one flat row per posting enriched with company firmographics and the company LinkedIn URL. Discovery runs through the boards named in sources as a chain: seven keyless boards first (Jobicy, Remotive,…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| keywords | array | yes | Role titles to search for across job boards, one per entry, for example ["account executive", "revops manager"]. Each keyword runs through the source chain separately. |
| sources | array | no | Which job boards to search, run as an ordered chain. Tier 0 needs no key and runs every keyword: jobicy, remotive, arbeitnow, themuse, remoteok, weworkremotely, himalayas. Tier 1 is adzuna (needs adzu |
| country | string | no | Geographic filter, e.g. United States, United Kingdom, Canada. Default: "United States". |
| countries | array | no | Loop these countries inside one run; overrides country when set. Metered sources query each country separately; keyless remote boards are global and run once. Use the names Google Jobs accepts, for ex |
| lookback_days | integer | no | Only return postings newer than this many days. Default: 30. |
| company_size_min | integer | no | Optional. Drop companies with fewer employees than this (only applied when company size is known). |
| company_size_max | integer | no | Optional. Drop companies larger than this (only applied when company size is known). |
| exclude_staffing_agencies | boolean | no | Filter out staffing and recruitment agency postings using name and job-description heuristics. Default: true. |
| exclude_freelance_marketplaces | boolean | no | Filter out postings where the company is a freelance marketplace (Upwork, Fiverr, etc.), which are noise for direct outreach. Default: true. |
| freelance_marketplaces | array | no | Company names treated as freelance marketplaces and excluded when the toggle above is on. Defaults shown; override or extend as needed. Default: ["Upwork", "Fiverr", "Freelancer", "Toptal", "PeoplePer |
| remote_only | boolean | no | Only return remote / work-from-home postings. Default: false. |
| previous_run_date | string | no | Optional ISO date (e.g. 2026-06-01) of your last run. Only postings newer than this are emitted, on top of the built-in cross-run delta cache. |
| max_results | integer | no | Upper bound on raw postings pulled from the discovery source before filtering. Higher values cost more. Default: 100. |
| max_companies | integer | no | Cap on unique companies enriched per run (firmographics + LinkedIn). Bounds sub-actor cost. Default: 40. |
| serpapi_key | string | no | SerpAPI key used for Google Jobs discovery (get a free key at serpapi.com, 250 searches/month, no card). Required to produce results unless a SERPAPI_KEY environment variable is set on the actor. |
| adzuna_app_id | string | no | Your Adzuna application id for the adzuna source. It travels in the tool call; the actor's ADZUNA_APP_ID environment variable is used when this is empty. |
| adzuna_app_key | string | no | Your Adzuna application key for the adzuna source. The actor's ADZUNA_APP_KEY environment variable is used when this is empty. |
| jobspipe_key | string | no | Your JobsPipe Bearer key (jp_live_...) for the jobspipe source. JobsPipe bills one credit per job returned. The actor's JOBSPIPE_KEY environment variable is used when this is empty. |
| theirstack_key | string | no | Your TheirStack API key for the theirstack source. TheirStack bills one credit per job returned. The actor's THEIRSTACK_KEY environment variable is used when this is empty. |
| metered_window_days | integer | no | Only ask the metered sources (jobspipe, theirstack) for postings this many days old or newer. They bill per job returned, seen before or not, so a narrow window is the biggest credit saver. 1 to 7. De |
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- 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 Gtm Job Discovery 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: —
ATrust score 96 / 100
Release 1.5.0 · scanned 16 Oct 2026
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.
Threat score100
Client score96
Findings1 threat · 0 capability
Capabilitymoderate
Coveragesource
Verificationrepo
Surface digest2925e300d688403476204732890a44adcf1bf16b7cbf5568b1ed6fd58803307b
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (1 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| monitor_job_postings | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true, handler sends an HTTP POST (fetch(https://api.apify.com/v2/acts/${actorPath}/runs?timeout=${ACTOR_RUN_TIMEOUT_SECS}) at build/index.js:85 |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest2925e300d6884034
Scanned2026-10-16
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 1.5.0. Pin a release below and the command asks for exactly that one.
1.5.0
16 Oct 2026
latestNo release note was published with this version.
1.4.1
6 Oct 2026
No release note was published with this version.
1.3.0
undated
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
—
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 Gtm Job Discovery 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.