com.mambabuilt/mcp-people-finder
NPM · @MAMBALABSDEV/MCP-PEOPLE-FINDER · SCANNED AUG 17
Find people at a company by role, seniority and department, with verified business emails.
Available components
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 →
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
- 30 of 96 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 4 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability57
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1076 tokens (~1076/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 Management23
- Stability observed for 7 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @mambalabsdev/mcp-people-finder
claude mcp add com-mambabuilt-mcp-people-finder -- npx -y @mambalabsdev/mcp-people-finder
codex mcp add com-mambabuilt-mcp-people-finder -- npx -y @mambalabsdev/mcp-people-finder
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-mambabuilt-mcp-people-finder": {
"type": "local",
"command": [
"npx",
"-y",
"@mambalabsdev/mcp-people-finder"
],
"enabled": true
}
}
} openclaw mcp add com-mambabuilt-mcp-people-finder --command npx --arg -y --arg @mambalabsdev/mcp-people-finder
mcp_servers:
com-mambabuilt-mcp-people-finder:
command: "npx"
args: ["-y", "@mambalabsdev/mcp-people-finder"] {
"mcpServers": {
"com-mambabuilt-mcp-people-finder": {
"command": "npx",
"args": [
"-y",
"@mambalabsdev/mcp-people-finder"
]
}
}
} 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.
- 17 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Aug 26 +2
- Stability: unverified → 0.10 ▲ functional
- Package version: 1.0.0 → 1.0.1 functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 10 Aug 26 65
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 17 Aug 2026 · Analysed npm/@mambalabsdev/mcp-people-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 |
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
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.
find_people_and_emails Find People and Emails ~1,076
Find people at a company and optionally discover and verify their business email. Identify the company by bare domain, by company name, by LinkedIn company URL, or pass a list of domains to run a batch where every output row echoes its source domain. Results are filtered by job title include and exclude lists, by normalized seniority, by normalized department and by country. A four layer cascade runs the company website, public search and a licensed database fallback, with company match scoring on every candidate; nothing here scrapes LinkedIn directly. Email discovery runs a two provider waterfall and verification escalates catch all domains to a second provider for a definitive answer. Provider keys are yours: you supply them, the vendors bill you directly, and the actor does not mark them up. Without a Serper key the search layer is off and coverage drops sharply. targetCount is a hard cost cap because billing is per person actually returned. Requires an APIFY_TOKEN and consumes Apify credits. Read only: it finds and verifies, it writes nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| batchSize | integer | – | How many companies to search concurrently in batch mode. Default 5, maximum 10. Default: 5. |
| bounceBanApiKey | string | – | Catch-all resolution. Used only when the primary verifier returns catch-all or risky, to determine whether that specific mailbox exists. Get a key at https://bounceban.com. Billed to you by BounceBan. |
| claudeApiKey | string | – | Optional. Only used to classify job titles that the built-in rule table cannot place into a seniority and department. One batched call per run, never per person. Leave empty to leave those two fields… |
| company_name | string | – | Used when no domain is available, or as a disambiguation hint alongside a domain. |
| countries | array | – | ISO 3166-1 alpha-2 codes. Filters to people located in these countries. Example: US, GB, NL |
| departments | array | – | Filter to these normalized departments. Leave empty for all. |
| domain | string | – | Bare domain without https:// or trailing slash. Example: stripe.com |
| domains | array | – | Optional list of bare domains. Takes precedence over the single domain field. Each domain is searched independently and every output row echoes its source domain. |
| excludeJobTitles | array | – | Case-insensitive substring match. A person matching any of these is dropped even if they matched an include. Example: intern, assistant, former |
| icypeasApiKey | string | – | Optional. Only used for the licensed-database fallback layer, which runs when the company website and public search results do not yield enough people. Leave empty to skip that layer entirely; the ru… |
| includeEmails | boolean | – | Discover a business email for each person found, using your Icypeas and/or Prospeo keys. Billed only when an email is actually returned. Turn off to build an org map cheaply. Default: true. |
| jobTitles | array | – | Case-insensitive substring match against the person's current title. Any match qualifies. Leave empty for no title filter. Example: VP Sales, Head of Growth |
| linkedin_company_url | string | – | Example: https://www.linkedin.com/company/stripe. Skips internal company resolution when provided. |
| prospeoApiKey | string | – | Second provider in the email waterfall. Used only for people the first provider could not resolve. Get a key at https://prospeo.io. Billed to you by Prospeo; this actor does not mark it up. |
| reoonApiKey | string | – | Primary email verification. Returns deliverability status for each discovered address. Get a key at https://emailverifier.reoon.com. Billed to you by Reoon. |
| seniority | array | – | Filter to these normalized seniority levels. Leave empty for all. |
| serpApiKey | string | – | Serper.dev API key. Unlocks the search layer, which is the highest-coverage source of LinkedIn profile URLs. Without it this actor falls back to company website parsing only, which returns far fewer… |
| skipCache | boolean | – | Results are cached for 7 days and reused on repeat lookups. Set true to force a fresh search. Default: false. |
| suppressLinkedInUrls | array | – | LinkedIn profile URLs to exclude from results. Use to suppress already-contacted prospects or honor data subject removal requests. |
| targetCount | integer | – | Maximum people to return per company. Billing is per person actually returned, so a lower number is a hard cost cap. Default: 5. |
| verifyEmails | boolean | – | Check deliverability of each email found, escalating catch-all domains to a second provider for a definitive answer. Requires a Reoon and/or BounceBan key. Default: true. |
| verifyPosition | boolean | – | Check that the person still holds the returned title at the target company, and report the reasoning. Reduces bounced outreach to people who have moved on. Default: false. |
No output schema declared.
No examples provided.