Server data from the Official MCP Registry
Extract the people a company publishes on its own team, leadership or about page.
About
Extract the people a company publishes on its own team, leadership or about page.
Security Report
This is a well-structured MCP server that acts as a thin client wrapper around the Apify Team Page People Extractor actor. Authentication is properly handled via environment variables, input validation is strict using Zod schemas, and the code has no malicious patterns or dangerous operations. The server appropriately requires APIFY_TOKEN and surfaces all errors explicitly rather than swallowing them. Minor code quality observations exist but do not pose security risks. Supply chain analysis found 3 known vulnerabilities in dependencies (0 critical, 3 high severity). Package verification found 1 issue.
3 files analyzed · 6 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
Permissions Required
This plugin requests these system permissions. Most are normal for its category.
What You'll Need
Set these up before or after installing:
Environment variable: APIFY_TOKEN
How to Install
Add this to your MCP configuration file:
{
"mcpServers": {
"com-mambabuilt-mcp-team-page-people-extractor": {
"env": {
"APIFY_TOKEN": "your-apify-token-here"
},
"args": [
"-y",
"@mambalabsdev/mcp-team-page-people-extractor"
],
"command": "npx"
}
}
}Documentation
View on GitHubFrom the project's GitHub README.
Team Page People Extractor MCP Server
MCP server for the Mamba Labs Team Page People Extractor actor on Apify.
Give it a company domain and it returns the people that company publishes on its own team, leadership or about page: names, titles, and the page each one came from. Nothing here reads LinkedIn or any other profile network.
Install
npx -y @mambalabsdev/mcp-team-page-people-extractor
Claude Desktop
{
"mcpServers": {
"mamba-team-page-people-extractor": {
"command": "npx",
"args": ["-y", "@mambalabsdev/mcp-team-page-people-extractor"],
"env": { "APIFY_TOKEN": "your-apify-token" }
}
}
}
Get an Apify token at console.apify.com/account/integrations.
Tool
extract_team_page_people
Give it a company domain and it returns the people that company publishes on its own team, leadership or about page: names, titles, and the page each one came from. Nothing here reads LinkedIn or any other profile network.
| Input | Type | Required | Notes |
|---|---|---|---|
domain | string | yes | A single company domain, for example swishdata.com. Protocol and path are stripped. |
output_grain | enum | no | 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 into columns. |
seniority_filter | enum | no | all keeps everyone the page published. executive keeps founders and C-level only. leadership adds VPs, directors and heads. |
max_people | string | no | 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. |
include_emails | boolean | no | 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@domain.com template string. Not one was a real person's address. When on, emails come back on the COMPANY row only, never attached to a named person, because nothing on these pages proves which address belongs to whom. |
skipCache | enum | no | false uses the 14 day result cache. true re-crawls the company from scratch. |
Billing
You are charged per person found, plus a small actor start fee. A company that publishes nobody costs only the start fee.
Pricing is on the actor's Apify page. Running this server consumes Apify credits.
What this server does and does not do
It is a thin client for the Apify actor. It passes your input through and returns the actor's output unchanged. Every behavior described above lives in the actor, not here.
Errors are surfaced, never swallowed. An invalid input, an invalid token, an exhausted balance, a timeout, or a run that returns anything other than a dataset all come back as an explicit tool error rather than as an empty result.
Source
The actor is on the Apify Store. This wrapper is MIT licensed.
Built by Mamba Labs
Reviews
No reviews yet
Be the first to review this server!
More Developer Tools MCP Servers
Git
Freeby Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
Toleno
Freeby Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
mcp-creator-python
Freeby mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.
MarkItDown
Freeby Microsoft · Content & Media
Convert files (PDF, Word, Excel, images, audio) to Markdown for LLM consumption
MCP Marketplace
Freeby mcp-marketplace · Developer Tools
Search and install MCP servers from inside your AI client.
FinAgent
Freeby mcp-marketplace · Finance
Free stock data and market news for any MCP-compatible AI assistant.