Name: Account Hiring Watch
Author: Mamba Labs

Account Hiring Watch MCP

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

Grade A Local · stdio API key 1 tool v1.0.1 · 16 Oct 2026

No reviews yet by Mamba Labsnpm Runs on your machine, nothing hosted

93/100

trust score

tool declared

local

runs on your machine

—

downloads a day

What it does

Watch a list of company domains and get only what changed on their job boards since the last run: new, closed, and reposted postings, plus 30 day hiring velocity.

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 account-hiring-watch-mcp '--' npx -y @mambalabsdev/mcp-account-hiring-watch

# 2 — ask your agent for something these tools do
#   watch_account_hiring

It needs APIFY_TOKEN: this reads it from your environment, so export it first.

Account Hiring Watch costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.

Publisher

Mamba Labs58 servers

7 categories · publishing since 2026

All 58 servers

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 Account Hiring Watch 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 account-hiring-watch-mcp '--' npx -y @mambalabsdev/mcp-account-hiring-watch

Reconnect, 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.

Only tools that write or reach the network

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…

Parameter	Type	Required	Notes
domains	array	yes	Company website domains to watch, for example stripe.com. The watch reads each company's own job board. Up to 2,000 per run.
watch_name	string	no	Keeps 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_categories	array	no	Only 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_keywords	array	no	Extra 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_hints	array	no	Point 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, ash
first_run_mode	string	no	What 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
first_run_recent_days	string	no	With first_run_mode recent: how many days back counts as recent. 1 to 30. Default 7.
closed_after_misses	string	no	A posting closes after this many complete board reads without it. A partial read never counts. 1 to 5. Default 2.
repost_window_days	string	no	A closed posting that comes back inside this many days is reported as reposted, not new. 7 to 60. Default 30.
include_job_description	string	no	Adds the full description text to new and reposted rows. Closed rows carry no description. Default true.
description_max_chars	string	no	Longest description kept per row. job_description_chars always reports the full length. 500 to 100000. Default 20000.
webhook_url	string	no	Optional HTTPS endpoint. Changes are sent as signed Standard Webhooks requests, and a change is charged only after your endpoint answers 2xx.
webhook_secret	string	no	Required with webhook_url. Signs each request (HMAC SHA256). A whsec_ prefixed secret is base64 decoded per the Standard Webhooks spec.
webhook_batch_mode	string	no	batch 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_store	string	no	Optional key value store that holds the watch state. Leave empty to use the store account-hiring-watch-state in your own Apify account.
max_domains	string	no	Domains past this number are skipped. 1 to 2000. Default 500.
max_charge_usd	string	no	Optional. 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.

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

Nothing here is billable: mcprush charges nothing to install Account Hiring Watch or to call it, at any volume.

ATrust score 93 / 100

Release 1.0.1 · 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 score93

Findings1 threat · 3 capability

Capabilityhigh

Coveragesource

Verificationrepo

Surface digest38011495f760647669fa585757587fa58b3be5d3268fdb35d79b61f7937cb974

Score vectorthreat 100 → client 93

Term	Level	What it prices	Points
capability-exposure	high	capability blast radius (high) — client exposure if the model is manipulated	−6
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. high is the level these add up to.

Tool	Capability tags	Why the tag was assigned
watch_account_hiring	external-sinksensitive-source	external-sink: keyword "webhook", parameter "webhook", 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:80; sensitive-source: parameter "secret"

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.

flow-1

Tool "watch_account_hiring" both reads sensitive data and can send it externally.

Supply chain and provenance

Integrityfirst-seen

Surface digest38011495f7606476

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.