People Data Labs MCP by usefulapi
by usefulapi.io · remote · no sign-in to list tools · v1.16.3 · published by io.usefulapi
Enrich and search people and companies, resolve identities, and enrich IP addresses.
8 tools: 5 change things and 3 only read.
Scanned Oct 21, 2026
- Deletes or cancels0Claude Code: deny
- Can't be undone0Claude Code: ask
- Changes things5Claude Code: ask: see these tools
- Only reads3Claude Code: allow: see these tools
3 checks matched something in the tool definitions. No finding is not a safety guarantee. How the checks work.
claude mcp add --transport http peopledatalabs https://peopledatalabs.usefulapi.io/mcpFindings
Matches of fixed checks, with the text they matched.
The server marks "pdl_person_search" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true}; The name "pdl_person_search" says "search": a word for reading.
The server marks "pdl_company_search" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true}; The name "pdl_company_search" says "search": a word for reading.
The server marks "pdl_job_posting_search" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true}; The name "pdl_job_posting_search" says "search": a word for reading.
Tools
Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.
8 tools
Changes things 5Claude Code: ask
pdl_company_searchSearch the full PDL Company Dataset with an Elasticsearch query object OR a SQL string over the Company Schema (e.g.1 finding
Why it is in this group
- The name "pdl_company_search" says "search": a word for reading.
- The input takes a statement or command to run (input.sql), which can change anything it can reach.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "pdl_company_search" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true}; The name "pdl_company_search" says "search": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Search companies
- readOnlyHint: true
pdl_ip_enrichEnrich an IP address with its location, company, and (optionally) associated person data via a 1:1 match against PDL's IP dataset.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- title: Enrich an IP address
- readOnlyHint: true
pdl_job_posting_searchSearch PDL's Job Posting Dataset (millions of active & historical postings sourced from company career pages) with an Elasticsearch query object OR a SQL string.1 finding
Why it is in this group
- The name "pdl_job_posting_search" says "search": a word for reading.
- The input takes a statement or command to run (input.sql), which can change anything it can reach.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "pdl_job_posting_search" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true}; The name "pdl_job_posting_search" says "search": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Search job postings
- readOnlyHint: true
pdl_person_identifyGiven broad, possibly-ambiguous attributes about a person, return up to 20 strongly-related profiles ranked by match score.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- title: Identify a person
- readOnlyHint: true
pdl_person_searchSearch the full PDL Person Dataset with an Elasticsearch query object OR a SQL string over the Person Schema (e.g.1 finding
Why it is in this group
- The name "pdl_person_search" says "search": a word for reading.
- The input takes a statement or command to run (input.sql), which can change anything it can reach.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "pdl_person_search" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true}; The name "pdl_person_search" says "search": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Search people
- readOnlyHint: true
Only reads 3Claude Code: allow
pdl_autocompleteGet suggested values for a search field along with the number of available records for each — useful for building valid Person/Company Search queries.No findings
Why it is in this group
- The description's first verb is "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Autocomplete search values
- readOnlyHint: true
pdl_company_enrichFind the single best-matching company record.No findings
Why it is in this group
- The description's first verb is "find": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Enrich a company
- readOnlyHint: true
pdl_person_enrichFind the single best-matching person profile for a set of identifying attributes (name, email, phone, profile URL, company, etc.).No findings
Why it is in this group
- The description's first verb is "find": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Enrich a person
- readOnlyHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Install
Pinned to version 1.16.3. Values in angle brackets are yours to fill in.
claude mcp add --transport http peopledatalabs https://peopledatalabs.usefulapi.io/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__peopledatalabs__pdl_person_enrich",
"mcp__peopledatalabs__pdl_company_enrich",
"mcp__peopledatalabs__pdl_autocomplete"
],
"ask": [
"mcp__peopledatalabs__pdl_person_identify",
"mcp__peopledatalabs__pdl_person_search",
"mcp__peopledatalabs__pdl_company_search",
"mcp__peopledatalabs__pdl_ip_enrich",
"mcp__peopledatalabs__pdl_job_posting_search"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as peopledatalabs. Review it before you use it.