com.mambabuilt/mcp-job-board-keyword-signal-scanner
Scans Greenhouse, Lever, Ashby, Workday, Rippling for roles in any category. Clay-ready.
What can you do with com.mambabuilt/mcp-job-board-keyword-signal-scanner?
- Configurable role categories: GTM, Engineering, Finance, Operations, Executive, Custom
- User-defined keyword arrays for custom scanning
- Per-category counts via roles_by_category, with category-level signal scoring
- Same ATS cascade as the Hiring Signal Scraper
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
@mambalabsdev/mcp-job-board-keyword-signal-scannerclaude mcp add mcp-job-board-keyword-signal-scanner -e 'APIFY_TOKEN=<your apify_token>' -- npx -y @mambalabsdev/mcp-job-board-keyword-signal-scanner@1.3.0
{
"mcpServers": {
"mcp-job-board-keyword-signal-scanner": {
"command": "npx",
"args": [
"-y",
"@mambalabsdev/mcp-job-board-keyword-signal-scanner@1.3.0"
],
"env": {
"APIFY_TOKEN": "<your apify_token>"
}
}
}
}
Environment variables
APIFY_TOKENrequired secret Apify API token from https://console.apify.com/account/integrations
Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
Contents
Job Board Keyword Signal Scanner MCP Server
An MCP server that scans a company's job board for the roles you care about. It wraps the Mamba Labs Job Board Keyword Signal Scanner actor on Apify and returns a Clay-ready flat JSON row to any MCP client.
What's Inside
- What it does
- Quick start
- Prerequisites
- Example prompts
- Inputs
- Output
- Example output
- Features
- Pricing
- How each call runs
- Full actor documentation
- Mamba Labs GTM Suite
- License
What it does
Give it a company domain and a set of role categories, and it scans Greenhouse, Lever, Ashby, Workday, and Rippling for matching open roles. Pick from GTM, Engineering, Finance, Operations, Executive, or pass your own custom keywords. You get back a flat row of matched role counts and titles per category, ready for Clay, a CRM, or an AI agent workflow. All of the scanning runs on Apify. This package is a thin client that calls the actor and hands back the result.
Quick start
You need Node.js 18 or newer and an Apify account with an API token.
Add this to your Claude Desktop config:
{
"mcpServers": {
"mamba-job-board-scanner": {
"command": "npx",
"args": ["-y", "@mambalabsdev/mcp-job-board-keyword-signal-scanner"],
"env": {
"APIFY_TOKEN": "your-apify-token"
}
}
}
}
Get your token at https://console.apify.com/account/integrations, paste it in, and restart Claude Desktop. The scan_job_board_keywords tool will be available.
Prerequisites
- Node.js 18 or newer
- An Apify account with an API token
Example prompts
- "Is stripe.com hiring engineers? Scan their job board for Engineering roles."
- "Check openai.com for GTM and Executive openings."
- "Scan figma.com for Finance and Operations roles."
- "Look for roles matching 'machine learning' and 'platform' at datadoghq.com using custom keywords."
Inputs
Every input the tool accepts, generated from the server's own tool list.
| Input | Type | Required | Description |
|---|---|---|---|
company_domain | string | yes | Bare company domain without https:// and without a trailing slash. Example: stripe.com |
role_categories | array of GTM, Engineering, Finance, Operations, Executive, Marketing, HR, CustomerSuccess, Data, Product, Legal, Design, Custom | yes | One or more role categories to scan for. Twelve categories plus Custom, which is used together with custom_keywords. Matching on the actor side is case insensitive and ignores separators, so customer_success and Customer Success both reach CustomerSuccess, and sales resolves to GTM. |
custom_keywords | array of string | no | Keyword strings to match when Custom is included in role_categories. Required only if Custom is requested. |
enable_fallback | boolean | no | If true, falls back to a pre-indexed job database when the live ATS cascade finds nothing. |
previous_roles_detected | string | no | Comma-separated matched role titles from a previous run, used to compute newly added or removed roles. |
previous_run_date | string | no | ISO date of the previous run, e.g. 2026-03-15. Used for tracking changes over time. |
max_charge_usd | number | no | Optional spending cap for this call, in USD. The actor stops before any charge that would take the run past this amount and keeps every row already charged. |
Output
The tool returns the actor's flat JSON row for the scanned company, including matched role counts and titles per requested category, the ATS platform detected, and optional change tracking. See the Apify Store page for the full output schema.
Example output
{
"company_domain": "figma.com",
"hiring_signal": true,
"ats_platform": "greenhouse",
"categories_searched": [
"Engineering"
],
"matched_role_count": 8,
"signal_strength": "high",
"top_matched_role": "Staff Engineer",
"most_recent_posting_date": "2026-05-27",
"run_date": "2026-05-28"
}
Features
- Configurable role categories: GTM, Engineering, Finance, Operations, Executive, Custom
- User-defined keyword arrays for custom scanning
- Per-category counts via roles_by_category, with category-level signal scoring
- Same ATS cascade as the Hiring Signal Scraper
Pricing
You pay per event on Apify, billed to your own Apify account. Prices from the live pricing record, read 2026-10-16:
| Event | Price per event (USD) | Fires when |
|---|---|---|
apify-default-dataset-item | $0.05 on the Free plan, down to $0.0425 on higher Apify plans | Single result in the default dataset. |
apify-actor-start | $0.00005 | Charged when the Actor starts running. Number of events charged depends on Actor memory (one event per GB, minimum one event). |
The actor's Apify page carries the current prices. Running this server consumes Apify credits.
How each call runs
Each call starts the actor run, polls it until it finishes, then reads the dataset. The run is allowed 1,800 seconds. If the run is still going when this call stops waiting, the call returns the run id and a console link instead of a timeout, so the result is never lost.
Full actor documentation
This server is a thin client and holds no scanning logic. For the complete input and output reference, pricing, and run history, see the Apify Store page:
https://apify.com/mambalabs/job-board-keyword-signal-scanner
Mamba Labs GTM Suite
This server is one of 58 Mamba Labs MCP servers, each backed by a dedicated Apify actor and published under @mambalabsdev on npm. The ones closest to this server:
| Actor | Immutable Actor ID |
|---|---|
| GTM Hiring Signal Scraper | D7O1SA2EqwHGsGr1P |
| Tech Stack Signal Detector | qyd7nNyqFPelQViBx |
| GTM Signals Aggregator | xKdRfnfFNkdMpFuNs |
| Job Board Keyword Signal Scanner | 4DvqpvhMR74NLcDDY |
| Domain to LinkedIn URL Resolver | 3HtnSaqPHOg1Qg5gx |
| ICP Fit Scorer | W161DT8W4kW55dMFh |
| Domain Deliverability Checker | 0tVgxI7A6o9jMlxmc |
| Company Firmographic Enricher | YlUtLWjfPpqykmB8g |
| Company Social Presence Mapper | 4k6CCemkgBDz18m2h |
| Company Identity Resolver | lr8fTRAmZCBZmuwwh |
| Company Change Event Feed | oX44rS0fkEJ3rXLWe |
| Funding and Press Signal Scanner | FS13X6dhQVgX3XOM6 |
To get twenty one of them in one install, use @mambalabsdev/mcp-gtm-suite.
Built by Mamba Labs | npm | Apify Store
License
MIT
Built by Mamba Labs. https://apify.com/mambalabs
Frequently asked questions
What is com.mambabuilt/mcp-job-board-keyword-signal-scanner?
Scans Greenhouse, Lever, Ashby, Workday, Rippling for roles in any category. Clay-ready.
How do I install com.mambabuilt/mcp-job-board-keyword-signal-scanner?
It runs on your machine. In Claude Code: claude mcp add mcp-job-board-keyword-signal-scanner -e 'APIFY_TOKEN=<your apify_token>' -- npx -y @mambalabsdev/mcp-job-board-keyword-signal-scanner@1.3.0. For other clients, paste the JSON configuration from this page into their MCP settings.
Does com.mambabuilt/mcp-job-board-keyword-signal-scanner need an API key?
Yes. It expects APIFY_TOKEN, which you set in its configuration.
Is com.mambabuilt/mcp-job-board-keyword-signal-scanner open source?
Yes. Its code is on GitHub under the MIT license.
Who maintains com.mambabuilt/mcp-job-board-keyword-signal-scanner?
It is published by mambalabsdev. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.