Model Context Protocol (MCP) server for Apollo.io API integration
Nothing to run from here
Peopledatalabs is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
tool-list score
8
tools declared
remote
at its publisher
—
calls last 7d
What it does
Enrich and search people and companies, resolve identities, and enrich IP addresses.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http usefulapi-peopledatalabs-mcp https://peopledatalabs.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# pdl_person_enrich, pdl_person_identify, pdl_person_search and 5 more
Peopledatalabs costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
USAll 334 servers
usefulapi334 servers
24 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http usefulapi-peopledatalabs-mcp https://peopledatalabs.usefulapi.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
8 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Find the single best-matching person profile for a set of identifying attributes (name, email, phone, profile URL, company, etc.). Returns one record plus a likelihood score (1-10), or a 404 'no match' body. Use uniquely-identifying inputs for best results. API: GET /person/enrich.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | no | Full name, e.g. 'Sean Thorne'. |
| first_name | string | no | First / given name. |
| last_name | string | no | Last / family name. |
| no | Email address, or an array of email addresses. | ||
| phone | string | no | Phone number (E.164 or local). |
| profile | no | Social profile URL(s), e.g. a LinkedIn URL. String or array. | |
| lid | string | no | LinkedIn numerical ID. |
| pdl_id | string | no | PDL persistent ID for a person record. |
| company | string | no | Company name, website, or PDL company id the person works at. |
| school | string | no | School name or website the person attended. |
| location | string | no | Free-text location, e.g. 'San Francisco, CA, USA'. |
| region | string | no | State / region, e.g. 'california'. |
| locality | string | no | City / locality, e.g. 'san francisco'. |
| postal_code | string | no | Postal / ZIP code (assumed US if no country). |
| country | string | no | Country name, e.g. 'united states'. |
| birth_date | string | no | Birth date (yyyy or yyyy-mm-dd). |
| min_likelihood | integer | no | Only return a 200 if match confidence >= this (1-10). |
| required | string | no | Only return a match that contains these fields, e.g. 'emails AND mobile_phone'. |
| titlecase | boolean | no | Titlecase the returned data (default false = lowercase). |
| pretty | boolean | no | Pretty-print the JSON response. |
Given broad, possibly-ambiguous attributes about a person, return up to 20 strongly-related profiles ranked by match score. Sits between enrich (1:1) and search (open-ended) — ideal when you can't uniquely resolve someone. API: GET /person/identify.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | no | Full name, e.g. 'Sean Thorne'. |
| first_name | string | no | First / given name. |
| last_name | string | no | Last / family name. |
| no | Email address, or an array of email addresses. | ||
| phone | string | no | Phone number (E.164 or local). |
| profile | no | Social profile URL(s), e.g. a LinkedIn URL. String or array. | |
| lid | string | no | LinkedIn numerical ID. |
| pdl_id | string | no | PDL persistent ID for a person record. |
| company | string | no | Company name, website, or PDL company id the person works at. |
| school | string | no | School name or website the person attended. |
| location | string | no | Free-text location, e.g. 'San Francisco, CA, USA'. |
| region | string | no | State / region, e.g. 'california'. |
| locality | string | no | City / locality, e.g. 'san francisco'. |
| postal_code | string | no | Postal / ZIP code (assumed US if no country). |
| country | string | no | Country name, e.g. 'united states'. |
| birth_date | string | no | Birth date (yyyy or yyyy-mm-dd). |
| titlecase | boolean | no | Titlecase the returned data (default false = lowercase). |
| pretty | boolean | no | Pretty-print the JSON response. |
Search the full PDL Person Dataset with an Elasticsearch query object OR a SQL string over the Person Schema (e.g. everyone with job_title_role='engineering' at a company). Returns matching profiles sorted by completeness; paginate with scroll_token. Each returned record costs 1 credit. API: POST /person/search.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | Elasticsearch query as a JSON string, e.g. {"query":{"term":{"job_company_name":"people data labs"}}} — pass the value of "query". |
| sql | string | no | SQL query string, e.g. SELECT * FROM person WHERE job_company_name='people data labs'. |
| size | integer | no | Number of records to return (1-100). Default 1. |
| from | integer | no | Legacy offset (0-9999). Prefer scroll_token. |
| scroll_token | string | no | Pagination token from a previous response. |
| dataset | string | no | Dataset(s) to search: resume, email, phone, mobile_phone, street_address, consumer_social, developer, all. Comma-separate; prefix '-' to exclude. |
| titlecase | boolean | no | Titlecase the returned data. |
| pretty | boolean | no | Pretty-print the JSON response. |
Find the single best-matching company record. Requires a non-ambiguous input — name OR website OR ticker OR profile (website/ticker/profile resolve more reliably than name). Returns firmographics (industry, size, location, etc.) or a 404 'no match' body. API: GET /company/enrich.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | no | Company name, e.g. 'People Data Labs'. |
| website | string | no | Company website, e.g. 'google.com' (most reliable). |
| ticker | string | no | Stock ticker for a public company, e.g. 'AAPL'. |
| profile | string | no | Company social profile URL, e.g. a LinkedIn company URL. |
| pdl_id | string | no | PDL id for a company record. |
| location | string | no | Company location free-text. |
| locality | string | no | Company city / locality. |
| region | string | no | Company state / region. |
| country | string | no | Company country. |
| titlecase | boolean | no | Titlecase the returned data. |
| pretty | boolean | no | Pretty-print the JSON response. |
Search the full PDL Company Dataset with an Elasticsearch query object OR a SQL string over the Company Schema (e.g. all SaaS companies with 50-200 employees in the US). Paginate with scroll_token. Each returned record costs 1 credit. API: POST /company/search.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | Elasticsearch query as a JSON string, e.g. {"query":{"term":{"industry":"computer software"}}} — pass the value of "query". |
| sql | string | no | SQL query string, e.g. SELECT * FROM company WHERE industry='computer software'. |
| size | integer | no | Number of records to return (1-100). Default 1. |
| from | integer | no | Legacy offset (0-9999). Prefer scroll_token. |
| scroll_token | string | no | Pagination token from a previous response. |
| titlecase | boolean | no | Titlecase the returned data. |
| pretty | boolean | no | Pretty-print the JSON response. |
Enrich an IP address with its location, company, and (optionally) associated person data via a 1:1 match against PDL's IP dataset. API: GET /ip/enrich.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ip | string | yes | The IP address to enrich, e.g. '72.212.42.169'. |
| return_person | boolean | no | Include associated person data if available. |
| min_confidence | string | no | Minimum confidence level required to return a match. |
| titlecase | boolean | no | Titlecase the returned data. |
| pretty | boolean | no | Pretty-print the JSON response. |
Get suggested values for a search field along with the number of available records for each — useful for building valid Person/Company Search queries. Free on all plans. API: GET /autocomplete.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| field | string | yes | Field to autocomplete: e.g. company, school, location, region, country, industry, title, role, sub_role, skill, major. |
| text | string | no | Partial text to get suggestions for, e.g. 'stanf'. |
| size | integer | no | Max suggestions to return. Default 10. |
| titlecase | boolean | no | Titlecase the returned data. |
| pretty | boolean | no | Pretty-print the JSON response. |
Search PDL's Job Posting Dataset (millions of active & historical postings sourced from company career pages) with an Elasticsearch query object OR a SQL string. Beta — may require plan access (HTTP 403 if not enabled). Each returned posting costs 1 credit. API: POST /job_posting/search.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | Elasticsearch query as a JSON string, e.g. {"query":{"term":{"title_role":"engineering"}}} — pass the value of "query". |
| sql | string | no | SQL query string over the job posting dataset. |
| size | integer | no | Number of records to return (1-100). Default 1. |
| scroll_token | string | no | Pagination token from a previous response. |
| pretty | boolean | no | Pretty-print the JSON response. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Peopledatalabs or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 93 / 100
Release 1.11.1 · scanned 20 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings0 threat · 0 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digestb3a5eeb547987765aab6aed289e3181ee1557baf76c4783a676cc67d31cc1637
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| pdl_person_enrich | no tags | |
| pdl_person_identify | no tags | |
| pdl_person_search | sensitive-source | sensitive-source: parameter "sql" |
| pdl_company_enrich | no tags | |
| pdl_company_search | sensitive-source | sensitive-source: parameter "sql" |
| pdl_ip_enrich | no tags | |
| pdl_autocomplete | no tags | |
| pdl_job_posting_search | sensitive-source | sensitive-source: parameter "sql" |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digestb3a5eeb547987765
Scanned2026-10-20
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.11.1.
1.11.1
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Peopledatalabs can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.