Skip to main content
Glama
mambalabsdev

mcp-job-board-keyword-signal-scanner

Job Board Keyword Signal Scanner MCP Server

Smithery Glama score MCP Registry npm version npm downloads license mcpservers.org

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

Related MCP server: mcp-gtm-suite

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

  • company_domain (required): the bare company domain, no https:// and no trailing slash. Example: stripe.com

  • role_categories (required): one or more of GTM, Engineering, Finance, Operations, Executive, Marketing, HR, CustomerSuccess, Data, Product, Legal, Design, or Custom. Matching is case insensitive and ignores separators, so customer_success and Customer Success both work, and sales resolves to GTM.

  • custom_keywords (optional): keyword strings to match when Custom is included.

  • enable_fallback (optional): fall back to a pre-indexed job database when the live ATS cascade finds nothing.

  • previous_roles_detected and previous_run_date (optional): pass a prior run's results to compute newly added or removed roles over time.

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

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 part of the Mamba Labs GTM Suite, a fleet of twelve specialized MCP servers for go-to-market signal intelligence, each backed by a dedicated Apify actor.

Actor

Immutable Actor ID

GTM Hiring Signal Scraper

D7O1SA2EqwHGsGr1P

GTM Tech Stack Signal Enrichment

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 & Press Signal Scanner

FS13X6dhQVgX3XOM6

Built by Mamba Labs | npm | Apify Store

License

MIT

Built by Mamba Labs. https://apify.com/mambalabs

Available Tools

1 tool
scan_job_board_keywordsScan Job Board KeywordsA
Read-onlyIdempotent

Scan a company's job board for roles in chosen categories across Greenhouse, Lever, Ashby, Workday, and Rippling. Pick from GTM, Engineering, Finance, Operations, Executive, or supply custom keywords. Returns a flat, Clay-ready JSON row of matched role counts and titles per category. Read-only; requires an APIFY_TOKEN and consumes Apify credits per call.

ParametersJSON Schema
NameRequiredDescriptionDefault
company_domainYesBare company domain without https:// and without a trailing slash. Example: stripe.com
role_categoriesYesOne or more role categories to scan for. Valid values: GTM, Engineering, Finance, Operations, Executive, Custom. Use Custom together with custom_keywords.
custom_keywordsNoKeyword strings to match when Custom is included in role_categories. Required only if Custom is requested.
enable_fallbackNoIf true, falls back to a pre-indexed job database when the live ATS cascade finds nothing.
previous_roles_detectedNoComma-separated matched role titles from a previous run, used to compute newly added or removed roles.
previous_run_dateNoISO date of the previous run, e.g. 2026-03-15. Used for tracking changes over time.

TDQS

A4.4/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Description adds 'Read-only; requires an APIFY_TOKEN and consumes Apify credits per call' beyond the annotations (readOnlyHint=true). This provides critical behavioral and cost information.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences front-load the key purpose, then output format, then requirements. Every sentence adds value with no fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Description covers return type, cost, and required token. Without output schema, it sufficiently explains outputs. Minor omission: no details on error cases, but acceptable given complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so baseline is 3. The description adds minimal extra meaning since schema already explains parameter choices; no compensation needed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states verb 'scan', resource 'job board', and specific ATS platforms (Greenhouse, Lever, etc.), distinguishing it from any potential siblings. It also mentions the output format.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Description explicitly lists role categories to pick from and explains when to use custom keywords. While no sibling tools exist to provide usage alternatives, it gives clear guidance on usage context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool updatev1.0.3
    • First observedscan_job_board_keywords

TDQS

A4.6/5.0

Scored across 1 tool

Disambiguation5/5

Only one tool exists, so there is no ambiguity with other tools. The tool's purpose is clearly defined.

Naming Consistency5/5

The single tool name 'scan_job_board_keywords' follows a clear verb_noun pattern, which is consistent and descriptive.

Tool Count5/5

The server has exactly one tool, which is appropriate for its focused purpose of scanning job boards for keyword signals. A single, well-defined tool is sufficient for this narrow scope.

Completeness5/5

The tool covers the full intended functionality: scanning multiple ATS platforms with configurable categories and returning results. No additional tools are necessary for its read-only scanning purpose.

Maintenance

ActivityMaintained
ResponsivenessResponsive

Related MCP Connectors

Related MCP Servers

  • A
    license
    A
    quality
    A
    maintenance
    GTM signal intelligence suite for AI agents. Six tools: hiring signals, tech stack detection, company-to-LinkedIn resolution, ICP scoring, job board scanning, and a combined signals aggregator. Built for outbound sales workflows.
    11
    122
    1
    MIT
  • F
    license
    Not graded
    quality
    D
    maintenance
    Transforms job postings into qualified sales leads by searching for active jobs, enriching company data, and identifying decision-maker contact information.
    -
  • F
    license
    Not graded
    quality
    B
    maintenance
    MCP server that turns live job postings into buying signals for B2B sales, enabling AI agents to find in-market accounts and time outreach based on hiring intent.
    -