Peopledatalabs
NPM · @PIPEWORX/MCP-PEOPLEDATALABS · 2 COMPONENTS
People Data Labs MCP — wraps the PDL person/company enrichment API (peopledatalabs.com).
Available components
Last scanned (4 hours ago)
Scores higher than 58% 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 Security100
- 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
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-peopledatalabs). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability61
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 476 tokens (~238/item across 2 items; 2 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 4 Nov 26 78
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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-peopledatalabs@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-peopledatalabs |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-peopledatalabs/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3685277429 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:26d475def8e885bb80c5b83b38ee5066e75a43fb02d93ec10550351a69f4feae93d6a0489667846b8bb167478c8a6f6a7f0eacf05fd1d76289bf4afcb |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
pdl_company_enrich ~145
Enrich a company from its name or domain using People Data Labs. Returns size, employee count, industry, founding year, location, LinkedIn, and website. Provide a name and/or website. Example: pdl_company_enrich({ website: "peopledatalabs.com", _apiKey: "your-key" })
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | Your People Data Labs API key (peopledatalabs.com; free tier ~100/mo). |
| name | string | – | Company name, e.g. "People Data Labs" |
| website | string | – | Company website or domain, e.g. "peopledatalabs.com" |
No output schema declared.
No examples provided.
pdl_person_enrich ~273
Enrich a person from their email / LinkedIn / name+company / phone using People Data Labs. Returns job title, company, emails, phone numbers, location, and skills. Provide at least one identifier. Example: pdl_person_enrich({ email: "sean@peopledatalabs.com", _apiKey: "your-key" })
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | Your People Data Labs API key (peopledatalabs.com; free tier ~100/mo). |
| company | string | – | Company name or domain the person works at, e.g. "People Data Labs" or "peopledatalabs.com" |
| string | – | Email address of the person, e.g. "sean@peopledatalabs.com" | |
| min_likelihood | number | – | Minimum match likelihood, integer 1-10. PDL only returns a person if confidence meets this floor. |
| name | string | – | Full name of the person, e.g. "Sean Thorne" (best combined with `company`) |
| phone | string | – | Phone number of the person, e.g. "+14155551234" |
| profile | string | – | LinkedIn profile URL, e.g. "https://www.linkedin.com/in/seanthorne" |
No output schema declared.
No examples provided.
How do I install the Peopledatalabs MCP server?
Peopledatalabs runs locally as an npm package, launched with npx -y @pipeworx/mcp-peopledatalabs. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-peopledatalabs
claude mcp add pipeworx-io-peopledatalabs -- npx -y @pipeworx/mcp-peopledatalabs
What is the Peopledatalabs MCP server?
Peopledatalabs is an MCP server listed in the public MCP registry as io.github.pipeworx-io/peopledatalabs. People Data Labs MCP, wraps the PDL person/company enrichment API (peopledatalabs.com). This page covers its npm package (@pipeworx/mcp-peopledatalabs).
Is the Peopledatalabs MCP server safe to use?
Peopledatalabs scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Peopledatalabs MCP server expose?
Peopledatalabs exposes 2 tools: pdl_person_enrich, pdl_company_enrich. Their descriptions and schemas cost roughly 418 tokens of context every time the server is loaded.
Is the Peopledatalabs MCP server still maintained?
Peopledatalabs is still listed as active in the MCP registry. We last reached this channel on 5 November 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 Peopledatalabs MCP server under?
Peopledatalabs declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.