Mcp Account Hiring Watch

com.mambabuiltPublished by mambabuilt.comv1.0.2Updated Nov 7, 2026

Watch company job boards for new, closed, and reposted postings, with 30 day hiring velocity.

VerifiedSTDIODesktop onlyWeb Search & ScrapingBusiness & Commerce

Overview

AI-generated overview

Watches company job boards and returns only new, closed and reposted postings since the last run, plus 30-day hiring velocity per company.

What you can do
  • Watch job boards for a list of company domains and get back only what changed since the last run with the same watch name: new, closed and reposted postings.
  • Read full job descriptions, stable posting keys and source board for each change, with a per-company summary of open postings and 30-day hiring velocity.
  • Filter changes by role categories or custom title keywords, and set a first-run baseline mode for new domains.
  • Optionally deliver changes to an HTTPS webhook with signed requests, in batch or per change.
When to use it
Useful for recruiting, sales or market research when you want to track hiring signals at target accounts over time and see only the deltas rather than re-reading whole job boards. The first run per watch sets a baseline, so repeated runs with the same watch name are what produce change reports.
Requirements
Runs locally as an npm package via npx, requiring Node.js 18 or newer. Needs an Apify account and an Apify API token supplied as the APIFY_TOKEN environment variable; the tool is listed without a token but a call needs one. All work runs on Apify, so network access is required. Optional webhook delivery needs an HTTPS endpoint and a webhook secret.
Before you install
Calls consume Apify credits: a per-run start fee plus a per-change fee for each new, closed or reposted posting returned, billed to your Apify account; a max_charge_usd cap can hold excess changes for the next run. The APIFY_TOKEN is a secret credential. Setting a webhook_url sends change data to a third-party endpoint and requires a webhook_secret. Watch state is kept in an Apify key-value store in your account.

Installation

In SourceWeft

  1. Open Mcp Account Hiring Watch in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Account Hiring Watch MCP Server

[Glama score] [MCP Registry] [npm version] [npm downloads] [license] [mcpservers.org]

[Account Hiring Watch MCP server]

An MCP server for the Mamba Labs Account Hiring Watch actor on Apify. Send a list of company domains. Each run reads every company's own job board and returns only what changed since the last run: new, closed, and reposted postings, with the full job description, a stable posting key, and 30 day hiring velocity per company.

What's Inside

What it does

Watch a list of company domains and get back only what changed on their job boards since the last run with the same watch name: new, closed, and reposted postings, read live from 17 job boards including Greenhouse, Lever, Ashby, and Workday. Each change row carries the full job description, a stable posting key, and the board it came from; each company also gets a summary row with open postings and 30 day hiring velocity. The first run for a watch sets the baseline, and its rows are marked is_backfill and never charged. Optional signed webhook delivery. A run that does not succeed is returned as an error with its run ID. Read-only on the boards; requires an APIFY_TOKEN and consumes Apify credits per change returned.

All of the work runs on Apify. This package is a thin client that starts the actor run, waits for it, and hands back the dataset rows.

Quick start

You need Node.js 18 or newer and an Apify account with an API token.

Add this to your Claude Desktop config (claude_desktop_config.json), Cursor, or any MCP client:

json
{  "mcpServers": {    "mamba-account-hiring-watch": {      "command": "npx",      "args": [        "-y",        "@mambalabsdev/mcp-account-hiring-watch"      ],      "env": {        "APIFY_TOKEN": "your-apify-token"      }    }  }}

Restart the client. The watch_account_hiring tool appears.

Prerequisites

Example prompts

  • "Watch stripe.com, ramp.com, and vercel.com for new sales and RevOps postings."
  • "Run my target account watch again and tell me which companies opened or closed GTM roles since last week."

Tool

watch_account_hiring. One tool. Example arguments:

json
{  "domains": ["stripe.com", "ramp.com", "vercel.com"],  "watch_name": "target-accounts",  "keyword_categories": ["GTM"]}

Inputs

Every buyer facing input of the live actor, unchanged. Omitted inputs take the actor's own defaults.

InputTypeRequiredDescription
domainsarrayyesCompany website domains to watch, for example stripe.com. The watch reads each company's own job board. Up to 2,000 per run.
watch_namestringnoKeeps separate watch lists apart. Use one name per list or client. Changing the name starts a new watch, and its first run sets the baseline. Default default.
keyword_categoriesarraynoOnly changes to postings whose title matches these role categories are returned and charged. All returns every posting change. Every posting still counts toward hiring velocity. Default ["All"].
custom_keywordsarraynoExtra title keywords, matched on whole words. Prefix with T1: for the strongest tier or T3: for the weakest; no prefix is tier 2. Adding any keyword also adds the Custom category.
board_hintsarraynoPoint a domain at its job board when the watch cannot find it, as domain=provider:slug, for example acme.com=greenhouse:acmeinc or acme.com=workday:acme.wd5/External. Providers: greenhouse, lever, ashby, workable, smartrecruiters, personio, recruitee, workday, rippling.
first_run_modestringnoWhat a domain's first run returns. recent returns postings the board dates inside the last N days, baseline_only returns the summary row, all_open returns every open posting. First run rows are marked is_backfill and never charged. Default recent.
first_run_recent_daysstringnoWith first_run_mode recent: how many days back counts as recent. 1 to 30. Default 7.
closed_after_missesstringnoA posting closes after this many complete board reads without it. A partial read never counts. 1 to 5. Default 2.
repost_window_daysstringnoA closed posting that comes back inside this many days is reported as reposted, not new. 7 to 60. Default 30.
include_job_descriptionstringnoAdds the full description text to new and reposted rows. Closed rows carry no description. Default true.
description_max_charsstringnoLongest description kept per row. job_description_chars always reports the full length. 500 to 100000. Default 20000.
webhook_urlstringnoOptional HTTPS endpoint. Changes are sent as signed Standard Webhooks requests, and a change is charged only after your endpoint answers 2xx.
webhook_secretstringnoRequired with webhook_url. Signs each request (HMAC SHA256). A whsec_ prefixed secret is base64 decoded per the Standard Webhooks spec.
webhook_batch_modestringnobatch sends up to 50 changes per request, grouped by company. per_change sends one request per change, for tools where one request is one row (Clay table webhooks, Zapier). Default batch.
state_storestringnoOptional key value store that holds the watch state. Leave empty to use the store account-hiring-watch-state in your own Apify account.
max_domainsstringnoDomains past this number are skipped. 1 to 2000. Default 500.
max_charge_usdstringnoOptional. When the next change would take this run's charges over this amount, the remaining changes are held and delivered first on the next run.

Pricing

Pay per event on Apify, billed to your Apify account. Prices in USD.

EventFree planBronzeSilverGold
posting_change, per change returned (new, closed, or reposted)$0.01$0.0095$0.009$0.0085
apify-actor-start, per run start$0.002$0.002$0.002$0.002

First run rows (is_backfill) and rows from a board the run could not confirm are never charged. With a webhook set, a change is charged only after your endpoint answers 2xx.

Your keys

The actor needs no provider key. It reads public job board APIs and holds no key of its own. A webhook secret, if you set one, is yours and is stored by Apify as a secret input.

Full actor documentation

apify.com/mambalabs/account-hiring-watch

License

MIT. See LICENSE.

Source: README.md at commit c8994a8

Tools

1

watch_account_hiring

Watch account hiring

Watch a list of company domains and get back only what changed on their job boards since the last run with the same watch name: new, closed, and reposted postings, read live from 17 job boards including Greenhouse, Lever, Ashby, and Workday. Each change row carries the full job description, a stable posting key, and the board it came from; each company also gets a summary row with open postings and 30 day hiring velocity. The first run for a watch sets the baseline, and its rows are marked is_backfill and never charged. Optional signed webhook delivery. A run that does not succeed is returned as an error with its run ID. Read-only on the boards; requires an APIFY_TOKEN and consumes Apify credits per change returned.

Parametersdomainsrequiredwatch_nameboard_hintsmax_domainsstate_storewebhook_urlfirst_run_modemax_charge_usdwebhook_secretcustom_keywordskeyword_categoriesrepost_window_days+5 more

Version history

3
  1. v1.0.2LatestNov 5, 2026
  2. v1.0.1Oct 16, 2026
  3. v1.0.0Oct 15, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts
  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts