People Data Labs MCP by usefulapi
REMOTE · PEOPLEDATALABS.USEFULAPI.IO
Enrich and search people and companies, resolve identities, and enrich IP addresses.
Available components
Last scanned (8 hours ago)
Scores higher than 4% of remote servers
Reachable. Last reached 5 Nov 2026.
Category CRM and Sales
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Checks we ran (4)
- TLS certificate
- HSTS header
- DNSSEC
- Transport
Checks we could not complete (7)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 1 Nov 26 −60
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 31 Oct 26 +3
- Authorization: partial → pass ▲ security
- MCP protocol: fail → pass ▲ functional
- New prompt “enrich_a_person_from_an_email_or_name” functional
- New prompt “find_companies_by_size_industry_and_country” functional
- New prompt “find_possible_matches_from_unclear_person_details” functional
- New prompt “find_which_company_is_behind_an_ip_address” functional
- New prompt “look_up_a_company_s_size_industry_and_location” functional
- New prompt “search_people_by_job_role_company_or_place” functional
- MCP protocol version: 2025-06-18 → 2025-11-25 functional
- Server version: 1.31.0 → 1.33.0 functional
- Server version: 1.30.0 → 1.31.0 functional
- Server version: 1.29.2 → 1.30.0 functional
- 30 Oct 26 0
- Server version: 1.29.1 → 1.29.2 functional
- Server version: 1.29.0 → 1.29.1 functional
- 29 Oct 26 0
- Server version: 1.28.0 → 1.29.0 functional
- Server version: 1.27.0 → 1.28.0 functional
- 28 Oct 26 0
- Server version: 1.25.0 → 1.27.0 functional
- 27 Oct 26 0
- Server version: 1.24.0 → 1.25.0 functional
- 25 Oct 26 0
- Server version: 1.23.0 → 1.24.0 functional
- Server version: 1.22.0 → 1.23.0 functional
- Server version: 1.21.3 → 1.22.0 functional
- Server version: 1.21.2 → 1.21.3 functional
- Server version: 1.21.0 → 1.21.2 functional
- 24 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 1.20.0 → 1.21.0 functional
- Server version: 1.19.0 → 1.20.0 functional
- Server version: 1.17.0 → 1.19.0 functional
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 · Probed https://peopledatalabs.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of peopledatalabs.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| io. | DS published | 38690 | 8 | Verified |
| usefulapi.io. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 302 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://peopledatalabs.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/peopledatalabs/ |
| http (plaintext) | http://peopledatalabs.usefulapi.io/mcp | Inconclusive | 302 | http://peopledatalabs.usefulapi.io/mcp |
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_autocomplete Autocomplete search values ~144
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.
| Name | Type | Req | Description |
|---|---|---|---|
| field | string | yes | Field to autocomplete: e.g. company, school, location, region, country, industry, title, role, sub_role, skill, major. |
| pretty | boolean | – | Pretty-print the JSON response. |
| size | integer | – | Max suggestions to return. Default 10. |
| text | string | – | Partial text to get suggestions for, e.g. 'stanf'. |
| titlecase | boolean | – | Titlecase the returned data. |
No output schema declared.
No examples provided.
pdl_company_enrich Enrich a company ~236
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.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Company country. |
| locality | string | – | Company city / locality. |
| location | string | – | Company location free-text. |
| name | string | – | Company name, e.g. 'People Data Labs'. |
| pdl_id | string | – | PDL id for a company record. |
| pretty | boolean | – | Pretty-print the JSON response. |
| profile | string | – | Company social profile URL, e.g. a LinkedIn company URL. |
| region | string | – | Company state / region. |
| ticker | string | – | Stock ticker for a public company, e.g. 'AAPL'. |
| titlecase | boolean | – | Titlecase the returned data. |
| website | string | – | Company website, e.g. 'google.com' (most reliable). |
No output schema declared.
No examples provided.
pdl_company_search Search companies ~204
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.
| Name | Type | Req | Description |
|---|---|---|---|
| from | integer | – | Legacy offset (0-9999). Prefer scroll_token. |
| pretty | boolean | – | Pretty-print the JSON response. |
| query | string | – | Elasticsearch query as a JSON string, e.g. {"query":{"term":{"industry":"computer software"}}} — pass the value of "query". |
| scroll_token | string | – | Pagination token from a previous response. |
| size | integer | – | Number of records to return (1-100). Default 1. |
| sql | string | – | SQL query string, e.g. SELECT * FROM company WHERE industry='computer software'. |
| titlecase | boolean | – | Titlecase the returned data. |
No output schema declared.
No examples provided.
pdl_ip_enrich Enrich an IP address ~132
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ip | string | yes | The IP address to enrich, e.g. '72.212.42.169'. |
| min_confidence | string | – | Minimum confidence level required to return a match. |
| pretty | boolean | – | Pretty-print the JSON response. |
| return_person | boolean | – | Include associated person data if available. |
| titlecase | boolean | – | Titlecase the returned data. |
No output schema declared.
No examples provided.
pdl_job_posting_search Search job postings ~170
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.
| Name | Type | Req | Description |
|---|---|---|---|
| pretty | boolean | – | Pretty-print the JSON response. |
| query | string | – | Elasticsearch query as a JSON string, e.g. {"query":{"term":{"title_role":"engineering"}}} — pass the value of "query". |
| scroll_token | string | – | Pagination token from a previous response. |
| size | integer | – | Number of records to return (1-100). Default 1. |
| sql | string | – | SQL query string over the job posting dataset. |
No output schema declared.
No examples provided.
pdl_person_enrich Enrich a person ~417
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.
| Name | Type | Req | Description |
|---|---|---|---|
| birth_date | string | – | Birth date (yyyy or yyyy-mm-dd). |
| company | string | – | Company name, website, or PDL company id the person works at. |
| country | string | – | Country name, e.g. 'united states'. |
| – | – | Email address, or an array of email addresses. | |
| first_name | string | – | First / given name. |
| last_name | string | – | Last / family name. |
| lid | string | – | LinkedIn numerical ID. |
| locality | string | – | City / locality, e.g. 'san francisco'. |
| location | string | – | Free-text location, e.g. 'San Francisco, CA, USA'. |
| min_likelihood | integer | – | Only return a 200 if match confidence >= this (1-10). |
| name | string | – | Full name, e.g. 'Sean Thorne'. |
| pdl_id | string | – | PDL persistent ID for a person record. |
| phone | string | – | Phone number (E.164 or local). |
| postal_code | string | – | Postal / ZIP code (assumed US if no country). |
| pretty | boolean | – | Pretty-print the JSON response. |
| profile | – | – | Social profile URL(s), e.g. a LinkedIn URL. String or array. |
| region | string | – | State / region, e.g. 'california'. |
| required | string | – | Only return a match that contains these fields, e.g. 'emails AND mobile_phone'. |
| school | string | – | School name or website the person attended. |
| titlecase | boolean | – | Titlecase the returned data (default false = lowercase). |
No output schema declared.
No examples provided.
pdl_person_identify Identify a person ~360
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.
| Name | Type | Req | Description |
|---|---|---|---|
| birth_date | string | – | Birth date (yyyy or yyyy-mm-dd). |
| company | string | – | Company name, website, or PDL company id the person works at. |
| country | string | – | Country name, e.g. 'united states'. |
| – | – | Email address, or an array of email addresses. | |
| first_name | string | – | First / given name. |
| last_name | string | – | Last / family name. |
| lid | string | – | LinkedIn numerical ID. |
| locality | string | – | City / locality, e.g. 'san francisco'. |
| location | string | – | Free-text location, e.g. 'San Francisco, CA, USA'. |
| name | string | – | Full name, e.g. 'Sean Thorne'. |
| pdl_id | string | – | PDL persistent ID for a person record. |
| phone | string | – | Phone number (E.164 or local). |
| postal_code | string | – | Postal / ZIP code (assumed US if no country). |
| pretty | boolean | – | Pretty-print the JSON response. |
| profile | – | – | Social profile URL(s), e.g. a LinkedIn URL. String or array. |
| region | string | – | State / region, e.g. 'california'. |
| school | string | – | School name or website the person attended. |
| titlecase | boolean | – | Titlecase the returned data (default false = lowercase). |
No output schema declared.
No examples provided.
pdl_person_search Search people ~255
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.
| Name | Type | Req | Description |
|---|---|---|---|
| dataset | string | – | Dataset(s) to search: resume, email, phone, mobile_phone, street_address, consumer_social, developer, all. Comma-separate; prefix '-' to exclude. |
| from | integer | – | Legacy offset (0-9999). Prefer scroll_token. |
| pretty | boolean | – | Pretty-print the JSON response. |
| query | string | – | Elasticsearch query as a JSON string, e.g. {"query":{"term":{"job_company_name":"people data labs"}}} — pass the value of "query". |
| scroll_token | string | – | Pagination token from a previous response. |
| size | integer | – | Number of records to return (1-100). Default 1. |
| sql | string | – | SQL query string, e.g. SELECT * FROM person WHERE job_company_name='people data labs'. |
| titlecase | boolean | – | Titlecase the returned data. |
No output schema declared.
No examples provided.
How do I install the People Data Labs MCP by usefulapi server?
People Data Labs MCP by usefulapi is a hosted endpoint at https://peopledatalabs.usefulapi.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · peopledatalabs.usefulapi.io
claude mcp add --transport http io-usefulapi-peopledatalabs 'https://peopledatalabs.usefulapi.io/mcp'
What is the People Data Labs MCP by usefulapi server?
People Data Labs MCP by usefulapi is listed in the public MCP registry as io.usefulapi/peopledatalabs. Enrich and search people and companies, resolve identities, and enrich IP addresses. This page covers its hosted endpoint (https://peopledatalabs.usefulapi.io/mcp).
Is the People Data Labs MCP by usefulapi server safe to use?
People Data Labs MCP by usefulapi scores 18 out of 100 on VerifyMCP. 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 People Data Labs MCP by usefulapi server expose?
People Data Labs MCP by usefulapi exposes 8 tools: pdl_person_enrich, pdl_person_identify, pdl_person_search, pdl_company_enrich, pdl_company_search, and 3 more. Their descriptions and schemas cost roughly 1,918 tokens of context every time the server is loaded.
Does the People Data Labs MCP by usefulapi server require authentication?
Its publisher declares no required credentials for People Data Labs MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the People Data Labs MCP by usefulapi server still maintained?
People Data Labs MCP by usefulapi 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 did VerifyMCP test on the People Data Labs MCP by usefulapi server?
VerifyMCP ran 4 checks on People Data Labs MCP by usefulapi, covering TLS certificate, HSTS header, DNSSEC and Transport. 7 items could not be completed, a gap on our side rather than a finding about People Data Labs MCP by usefulapi: Authorization, HTTPS, Schema quality, Stability and 3 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.