Mcp Account Hiring Watch

com.mambabuilt由 mambabuilt.com 发布v1.0.2更新于 Nov 7, 2026

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

已验证STDIO仅桌面网页搜索与抓取商业与电商

概览

AI 生成的概览

监控公司招聘页面，只返回自上次运行以来的新增、关闭和重新发布的职位，并给出每家公司 30 天招聘速度。

可以做什么
  • 按公司域名列表监控招聘页面，只返回与同名 watch 上次运行相比的变化：新增、关闭和重新发布的职位。
  • 每条变化包含完整职位描述、稳定的职位标识和来源招聘平台，并为每家公司提供在招职位数与 30 天招聘速度汇总。
  • 可按职位类别或自定义标题关键词筛选变化，并为新域名设置首次运行的基线模式。
  • 可选将变化推送到 HTTPS webhook，请求带签名，支持批量或逐条发送。
适用场景
适合招聘、销售或市场研究场景，需要长期跟踪目标公司的招聘动向，并且只想看到增量变化而不是每次重读整个招聘页面。每个 watch 的首次运行建立基线，因此用同一 watch 名称重复运行才会产生变化报告。
运行要求
以 npm 包形式通过 npx 在本地运行，需要 Node.js 18 或更高版本。需要 Apify 账户和 Apify API 令牌，通过环境变量 APIFY_TOKEN 提供；无令牌时工具仍会列出，但调用需要令牌。所有处理在 Apify 上完成，需要网络访问。可选的 webhook 推送需要 HTTPS 端点和 webhook 密钥。
安装前请注意
调用会消耗 Apify 额度：每次运行有启动费用，并按返回的每条新增、关闭或重新发布职位计费，费用计入你的 Apify 账户；可用 max_charge_usd 设置上限，超出部分留到下次运行。APIFY_TOKEN 是敏感凭据。设置 webhook_url 会把变化数据发送到第三方端点，并需要 webhook_secret。watch 状态保存在你 Apify 账户的键值存储中。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Mcp Account Hiring Watch，将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only，通过 STDIO。 STDIO 服务会启动本地进程，因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

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.

来源：README.md，提交 c8994a8

工具

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.

输入参数domains必填watch_nameboard_hintsmax_domainsstate_storewebhook_urlfirst_run_modemax_charge_usdwebhook_secretcustom_keywordskeyword_categoriesrepost_window_days另有 5 个

版本历史

3
  1. v1.0.2最新Nov 5, 2026
  2. v1.0.1Oct 16, 2026
  3. v1.0.0Oct 15, 2026

评分

已满足适用检查项的 90%

该评分衡量此收录条目的完整程度，依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价，也不表示服务器安全或当前可用：可连通性是带日期的检查结果，评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分
  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头，或保持端点能够响应探测，以便判定其认证方式。

  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分