com.mambabuilt/mcp-new-hire-finder
NPM · @MAMBALABSDEV/MCP-NEW-HIRE-FINDER
Find people who started a matching role at a company inside a lookback window.
Available components
Last scanned (10 hours ago)
Scores higher than 39% of npm servers
Category CRM and Sales
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability58
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1139 tokens (~1139/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 +1
- Known CVEs: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Capabilities: pass → unverified ▼ functional
- Dependency health: 0.85 → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Package version: 1.0.0 → 1.0.1 functional
- 15 Oct 26 +28
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 100 functional
- 14 Oct 26 39
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 18 Oct 2026 · Analysed npm/@mambalabsdev/mcp-new-hire-finder@1.0.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
find_new_hires Find new hires ~1,139
Find people who started a role matching your titles at a company inside a lookback window. Give company_domain (or company_domains), target_titles, and lookback_months. Returns one flat, Clay-ready JSON row per person with name, profile URL, title, start month, prior role, move type (new hire, internal promotion, or announcement only), and source, plus one summary row per company that says whether anyone was found or why nothing could be looked up. Runs on your own Prospeo, Serper, SerpApi, or Exa keys passed as inputs, and on a people list you send; it never fetches LinkedIn and holds no key of its own. A run that does not succeed is returned as an error with its run ID. Reads public data and writes nothing; requires an APIFY_TOKEN and consumes Apify credits per call.
| Name | Type | Req | Description |
|---|---|---|---|
| company_domain | string | – | One company domain, for example zapier.com. Use this or Company domains (batch); both are merged. |
| company_domains | array | – | A list of company domains. Each company gets its own summary row. |
| company_name | string | – | Optional, single company runs only. Leave empty and the name is read from the homepage. |
| departments | array | – | Optional. Keep only these departments. |
| exa_api_key | string | – | Your own Exa key. Exa people search returns work histories with start months, so its results need no enrichment. Your own key, sent as a run input; never stored by the actor. |
| exclude_titles | array | – | Optional. Drop any title that contains one of these phrases, for example intern. |
| expand_title_synonyms | boolean | – | Also match a short synonym list (marketing also matches growth, brand, demand generation). Off by default, because every row is charged. |
| include_year_only | boolean | – | Also return people whose start is known only to the year and could fall inside the window. They are charged like any row. Off by default. |
| lookback_months | string | – | How many calendar months back to look, including this month. 1 to 24, default 6. 6 in October means May to October. Typed as text so Clay can send it. |
| max_charge_usd | number | – | Optional. The run stops before any charge that would take this run past this amount, and keeps every row already paid for. Leave empty to rely only on the maximum cost per run set in Apify, which the… |
| max_enrich_per_company | string | – | Prospeo enrichment calls per company to date people found by web search, headlines, and team pages. 0 to 25, default 5. |
| max_people_per_company | string | – | Most person rows to return per company, newest starts first. 1 to 100, default 25. |
| max_prospeo_pages_per_company | string | – | Prospeo search pages of 25 people per company. 1 to 4, default 1. |
| max_search_queries_per_company | string | – | Web search queries per company on your key. 1 to 4, default 1. |
| move_types | array | – | Which moves to return and charge. new_hire is a person who came from another employer. promotion is a new role at the same employer. unknown is a hire announcement with no work history. Default new_h… |
| people | array | – | People you already hold, with role histories. Each item: person_name, company_domain, profile_url (optional), and roles, a list of {title, company_name, start (YYYY-MM), end (YYYY-MM or null)}. The s… |
| prospeo_api_key | string | – | Your own Prospeo key. Gives the work history behind start month and move type. One Prospeo credit per search page of 25 people and one per person enrichment, billed by Prospeo to you. Never stored. Y… |
| seniority | array | – | Optional. Keep only these seniority levels. |
| serpapi_api_key | string | – | Your own SerpApi key for web search. A different vendor from Serper. Your own key, sent as a run input; never stored by the actor. |
| serper_api_key | string | – | Your own Serper.dev key for web search. One search per company by default. Search results carry no start date, so they are dated with your Prospeo key or counted as undated. Your own key, sent as a r… |
| skip_cache | boolean | – | Search again even when the same company and filters ran in the last 7 days. A cached result is returned free. |
| sources | array | – | Routes to run. Default all. buyer_data is your people list; prospeo and web_search run only with your key; news, newsroom, and team_pages are free. |
| target_titles | array | – | Title phrases to match, for example marketing, head of content, editor. A title matches when it contains every word of a phrase as a whole word. Also sent to Prospeo and web search as the title filte… |
| web_search_provider | string | – | Which of your search keys to use. auto takes the first key present: Serper, then SerpApi, then Exa. |
No output schema declared.
No examples provided.
How do I install the com.mambabuilt/mcp-new-hire-finder server?
com.mambabuilt/mcp-new-hire-finder runs locally as an npm package, launched with npx -y @mambalabsdev/mcp-new-hire-finder. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @mambalabsdev/mcp-new-hire-finder
claude mcp add com-mambabuilt-mcp-new-hire-finder -- npx -y @mambalabsdev/mcp-new-hire-finder
What is the com.mambabuilt/mcp-new-hire-finder server?
com.mambabuilt/mcp-new-hire-finder is listed in the public MCP registry as com.mambabuilt/mcp-new-hire-finder. Find people who started a matching role at a company inside a lookback window. This page covers its npm package (@mambalabsdev/mcp-new-hire-finder).
Is the com.mambabuilt/mcp-new-hire-finder server safe to use?
com.mambabuilt/mcp-new-hire-finder scores 69 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 18 October 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the com.mambabuilt/mcp-new-hire-finder server expose?
com.mambabuilt/mcp-new-hire-finder exposes 1 tool: find_new_hires. Their descriptions and schemas cost roughly 1,139 tokens of context every time the server is loaded.
Is the com.mambabuilt/mcp-new-hire-finder server still maintained?
com.mambabuilt/mcp-new-hire-finder is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the com.mambabuilt/mcp-new-hire-finder server under?
com.mambabuilt/mcp-new-hire-finder declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.