com.mambabuilt/mcp-team-page-people-extractor
NPM · @MAMBALABSDEV/MCP-TEAM-PAGE-PEOPLE-EXTRACTOR · SCANNED AUG 17
Extract the people a company publishes on its own team, leadership or about page.
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 3 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability67
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 554 tokens (~554/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-team-page-people-extractor
claude mcp add com-mambabuilt-mcp-team-page-people-extractor -- npx -y @mambalabsdev/mcp-team-page-people-extractor
codex mcp add com-mambabuilt-mcp-team-page-people-extractor -- npx -y @mambalabsdev/mcp-team-page-people-extractor
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-mambabuilt-mcp-team-page-people-extractor": {
"type": "local",
"command": [
"npx",
"-y",
"@mambalabsdev/mcp-team-page-people-extractor"
],
"enabled": true
}
}
} openclaw mcp add com-mambabuilt-mcp-team-page-people-extractor --command npx --arg -y --arg @mambalabsdev/mcp-team-page-people-extractor
mcp_servers:
com-mambabuilt-mcp-team-page-people-extractor:
command: "npx"
args: ["-y", "@mambalabsdev/mcp-team-page-people-extractor"] {
"mcpServers": {
"com-mambabuilt-mcp-team-page-people-extractor": {
"command": "npx",
"args": [
"-y",
"@mambalabsdev/mcp-team-page-people-extractor"
]
}
}
} 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: 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
- Tool coverage: 100 → unverified ▼ functional
- Stability: unverified → 0.10 ▲ functional
- First check of Schema quality: unverified functional
- Package version: 1.0.0 → 1.0.1 functional
- 11 Aug 26 +1
- 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 66
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-team-page-people-extractor@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.
extract_team_page_people Extract Team Page People ~554
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_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.