com.mambabuilt/mcp-team-page-people-extractor
NPM · @MAMBALABSDEV/MCP-TEAM-PAGE-PEOPLE-EXTRACTOR
Extract the people a company publishes on its own team, leadership or about page.
Available components
Last scanned (16 hours ago)
Scores higher than 74% of npm servers
Category Web Scraping
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 0 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 621 tokens (~621/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 Management97
- Stability observed for 29 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.
- 16 Oct 26 0
- Schema quality: 554 → 621 ▼ functional
- Package version: 1.1.1 → 1.2.0 functional
- 14 Oct 26 +43
- Injection markers: unverified → pass ▲ security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Stability: unverified → 0.90 ▲ functional
- Package version: 1.0.1 → 1.1.1 functional
- 12 Oct 26 +1
- Security disclosure: unverified → pass ▲ functional
- 11 Oct 26 −43
- Stability: 0.83 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Security disclosure: pass → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 1.0.1 → 1.1.1 functional
- 4 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Oct 26 −3
- Stability: pass → 0.80 functional
- 2 Oct 26 0
- Stability: 0.97 → pass security
- 1 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
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 16 Oct 2026 · Analysed npm/@mambalabsdev/mcp-team-page-people-extractor@1.2.0
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 →
extract_team_page_people Extract Team Page People ~621
Extract the people a company publishes on its own team, leadership or about page, and return their names, titles and the page each one came from. It also reports which pages it actually reached, so an empty result tells you whether the company publishes nobody or whether the site could not be read, which are very different answers. output_grain person returns one row per person and is what most tables want; output_grain company returns one row per company with a people_json array plus the first five names and titles flattened into columns. seniority_filter narrows to founders and C level, or adds VPs, directors and heads. People are ordered by seniority before max_people applies, and anything dropped is logged with a count. include_emails is off by default and should usually stay off: across the domains tested, the addresses published on team pages were role mailboxes, placeholders and literal template strings rather than real people, so when it is on the emails come back on the company row only and are never attached to a named person. Results are cached for 14 days. Nothing here scrapes LinkedIn or any profile network; it reads only what the company published itself. Requires an APIFY_TOKEN and consumes Apify credits. Read only.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | A single company domain, for example swishdata.com. Protocol and path are stripped. |
| include_emails | boolean | – | Off by default and you should probably leave it off. Across three domains that published an email on a team page we found one role mailbox, one placeholder in example content, and one literal user@do… |
| max_charge_usd | number | – | Optional spending cap for this call, in USD, passed to the actor as max_charge_usd. The run stops before any charge that would take it past this amount and keeps every row already charged. Leave empt… |
| max_people | string | – | Sent as a string so Clay can map a column into it. Clamped to 1 to 200. People are ordered by seniority before the cap applies, and anything dropped is logged with the count. Default: "50". |
| output_grain | string | – | person returns one row per person, which is the default and what most Clay tables want. company returns one row per company with a people_json array plus the first five names and titles flattened int… |
| seniority_filter | string | – | all keeps everyone the page published. executive keeps founders and C-level only. leadership adds VPs, directors and heads. Default: "all". |
| skipCache | string | – | false uses the 14 day result cache. true re-crawls the company from scratch. Default: "false". |
No output schema declared.
No examples provided.
How do I install the com.mambabuilt/mcp-team-page-people-extractor server?
com.mambabuilt/mcp-team-page-people-extractor runs locally as an npm package, launched with npx -y @mambalabsdev/mcp-team-page-people-extractor. 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-team-page-people-extractor
claude mcp add com-mambabuilt-mcp-team-page-people-extractor -- npx -y @mambalabsdev/mcp-team-page-people-extractor
What is the com.mambabuilt/mcp-team-page-people-extractor server?
com.mambabuilt/mcp-team-page-people-extractor is listed in the public MCP registry as com.mambabuilt/mcp-team-page-people-extractor. Extract the people a company publishes on its own team, leadership or about page. This page covers its npm package (@mambalabsdev/mcp-team-page-people-extractor).
Is the com.mambabuilt/mcp-team-page-people-extractor server safe to use?
com.mambabuilt/mcp-team-page-people-extractor scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 16 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-team-page-people-extractor server expose?
com.mambabuilt/mcp-team-page-people-extractor exposes 1 tool: extract_team_page_people. Their descriptions and schemas cost roughly 621 tokens of context every time the server is loaded.
Is the com.mambabuilt/mcp-team-page-people-extractor server still maintained?
com.mambabuilt/mcp-team-page-people-extractor is still listed as active in the MCP registry. We last reached this channel on 16 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-team-page-people-extractor server under?
com.mambabuilt/mcp-team-page-people-extractor declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.