Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.usefulapi/peopledatalabs

REMOTE · PEOPLEDATALABS.USEFULAPI.IO · SCANNED SEP 20

Enrich and search people and companies, resolve identities, and enrich IP addresses.

Available components

remote · peopledatalabs.usefulapi.io 81
+63 this week 81 Trust /100
Trust breakdown (7 categories)

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 Security78
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
  • HTTPS enforcement could not be verified: the plaintext port answered with HTTP 401, which proves neither a plaintext path nor enforcement. 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
  • The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
Schema Quality & AI Usability66
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1918 tokens (~239/item across 8 items; 8 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 Management80
  • Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Install

How do I install the io.usefulapi/peopledatalabs MCP server?

io.usefulapi/peopledatalabs 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

# add to Claude Code
claude mcp add --transport http io-usefulapi-peopledatalabs 'https://peopledatalabs.usefulapi.io/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "io-usefulapi-peopledatalabs": {
      "url": "https://peopledatalabs.usefulapi.io/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "io-usefulapi-peopledatalabs": {
      "type": "http",
      "url": "https://peopledatalabs.usefulapi.io/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.io-usefulapi-peopledatalabs]
url = "https://peopledatalabs.usefulapi.io/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-peopledatalabs": {
      "type": "remote",
      "url": "https://peopledatalabs.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add io-usefulapi-peopledatalabs --url 'https://peopledatalabs.usefulapi.io/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  io-usefulapi-peopledatalabs:
    url: "https://peopledatalabs.usefulapi.io/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "io-usefulapi-peopledatalabs": {
      "Transport": "http",
      "Url": "https://peopledatalabs.usefulapi.io/mcp"
    }
  }
}
# add to Vellum
assistant mcp add io-usefulapi-peopledatalabs -t streamable-http -u 'https://peopledatalabs.usefulapi.io/mcp'
// mcp.json
{
  "mcpServers": {
    "io-usefulapi-peopledatalabs": {
      "type": "http",
      "url": "https://peopledatalabs.usefulapi.io/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Sept 26 +62
    • Transport: unverified → pass ▲ security
    • Authorization: unverified → pass ▲ security
    • Injection markers: unverified → pass ▲ security
    • MCP protocol: unverified → fail ▼ functional
    • Endpoint reachability: not serving MCP → reachable ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • Stability: unverified → 0.77 ▲ functional
  • 18 Sept 26 −10
    • Transport: pass → unverified ▼ security
  • 17 Sept 26 +10
    • Transport: unverified → pass ▲ security
  • 9 Sept 26 −65
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Authorization: pass → unverified ▼ security
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Transport: pass → unverified ▼ security
    • Capabilities: fail → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 2 Sept 26 0
    • Stability: 0.97 → pass security
  • 31 Aug 26 0
    • Stability: pass → 0.93 functional
  • 27 Aug 26 +65
    • Transport: unverified → pass ▲ security
    • Authorization: unverified → pass ▲ security
    • Injection markers: unverified → pass ▲ security
    • Stability: unverified → pass ▲ security
    • First check of Judged manipulation: pass security
    • MCP protocol: unverified → fail ▼ functional
    • Endpoint reachability: not serving MCP → reachable ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • First check of Destructive annotations: pass functional
Diagnostics

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 20 Sept 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 14 Sept 2026 13 Dec 2026 ECDSA 256 ECDSA-SHA256 ec91c71d64a9fb5e0eb28b44b4a277c2
SANs: usefulapi.io, peopledatalabs.usefulapi.io, *.peopledatalabs.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. present 57355 8 Verified
usefulapi.io. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://peopledatalabs.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token" 

Bearer realm="OAuth", resource_metadata="https://peopledatalabs.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"

Protected resource metadata

Document https://peopledatalabs.usefulapi.io/.well-known/oauth-protected-resource/mcp
Retrieved Yes
Resource https://peopledatalabs.usefulapi.io/mcp
Authorisation server https://peopledatalabs.usefulapi.io

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 Verified 200
http (plaintext) http://peopledatalabs.usefulapi.io/mcp Inconclusive 401
MCP tools · 8 exposed · ~1,918 tokens

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 →

Tool Tokens
pdl_autocomplete ~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.

NameTypeReqDescription
fieldstringyesField to autocomplete: e.g. company, school, location, region, country, industry, title, role, sub_role, skill, major.
prettyboolean–Pretty-print the JSON response.
sizeinteger–Max suggestions to return. Default 10.
textstring–Partial text to get suggestions for, e.g. 'stanf'.
titlecaseboolean–Titlecase the returned data.

No output schema declared.

No examples provided.

pdl_company_enrich ~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.

NameTypeReqDescription
countrystring–Company country.
localitystring–Company city / locality.
locationstring–Company location free-text.
namestring–Company name, e.g. 'People Data Labs'.
pdl_idstring–PDL id for a company record.
prettyboolean–Pretty-print the JSON response.
profilestring–Company social profile URL, e.g. a LinkedIn company URL.
regionstring–Company state / region.
tickerstring–Stock ticker for a public company, e.g. 'AAPL'.
titlecaseboolean–Titlecase the returned data.
websitestring–Company website, e.g. 'google.com' (most reliable).

No output schema declared.

No examples provided.

pdl_company_search ~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.

NameTypeReqDescription
frominteger–Legacy offset (0-9999). Prefer scroll_token.
prettyboolean–Pretty-print the JSON response.
querystring–Elasticsearch query as a JSON string, e.g. {"query":{"term":{"industry":"computer software"}}} — pass the value of "query".
scroll_tokenstring–Pagination token from a previous response.
sizeinteger–Number of records to return (1-100). Default 1.
sqlstring–SQL query string, e.g. SELECT * FROM company WHERE industry='computer software'.
titlecaseboolean–Titlecase the returned data.

No output schema declared.

No examples provided.

pdl_ip_enrich ~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.

NameTypeReqDescription
ipstringyesThe IP address to enrich, e.g. '72.212.42.169'.
min_confidencestring–Minimum confidence level required to return a match.
prettyboolean–Pretty-print the JSON response.
return_personboolean–Include associated person data if available.
titlecaseboolean–Titlecase the returned data.

No output schema declared.

No examples provided.

pdl_job_posting_search ~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.

NameTypeReqDescription
prettyboolean–Pretty-print the JSON response.
querystring–Elasticsearch query as a JSON string, e.g. {"query":{"term":{"title_role":"engineering"}}} — pass the value of "query".
scroll_tokenstring–Pagination token from a previous response.
sizeinteger–Number of records to return (1-100). Default 1.
sqlstring–SQL query string over the job posting dataset.

No output schema declared.

No examples provided.

pdl_person_enrich ~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.

NameTypeReqDescription
birth_datestring–Birth date (yyyy or yyyy-mm-dd).
companystring–Company name, website, or PDL company id the person works at.
countrystring–Country name, e.g. 'united states'.
email––Email address, or an array of email addresses.
first_namestring–First / given name.
last_namestring–Last / family name.
lidstring–LinkedIn numerical ID.
localitystring–City / locality, e.g. 'san francisco'.
locationstring–Free-text location, e.g. 'San Francisco, CA, USA'.
min_likelihoodinteger–Only return a 200 if match confidence >= this (1-10).
namestring–Full name, e.g. 'Sean Thorne'.
pdl_idstring–PDL persistent ID for a person record.
phonestring–Phone number (E.164 or local).
postal_codestring–Postal / ZIP code (assumed US if no country).
prettyboolean–Pretty-print the JSON response.
profile––Social profile URL(s), e.g. a LinkedIn URL. String or array.
regionstring–State / region, e.g. 'california'.
requiredstring–Only return a match that contains these fields, e.g. 'emails AND mobile_phone'.
schoolstring–School name or website the person attended.
titlecaseboolean–Titlecase the returned data (default false = lowercase).

No output schema declared.

No examples provided.

pdl_person_identify ~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.

NameTypeReqDescription
birth_datestring–Birth date (yyyy or yyyy-mm-dd).
companystring–Company name, website, or PDL company id the person works at.
countrystring–Country name, e.g. 'united states'.
email––Email address, or an array of email addresses.
first_namestring–First / given name.
last_namestring–Last / family name.
lidstring–LinkedIn numerical ID.
localitystring–City / locality, e.g. 'san francisco'.
locationstring–Free-text location, e.g. 'San Francisco, CA, USA'.
namestring–Full name, e.g. 'Sean Thorne'.
pdl_idstring–PDL persistent ID for a person record.
phonestring–Phone number (E.164 or local).
postal_codestring–Postal / ZIP code (assumed US if no country).
prettyboolean–Pretty-print the JSON response.
profile––Social profile URL(s), e.g. a LinkedIn URL. String or array.
regionstring–State / region, e.g. 'california'.
schoolstring–School name or website the person attended.
titlecaseboolean–Titlecase the returned data (default false = lowercase).

No output schema declared.

No examples provided.

pdl_person_search ~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.

NameTypeReqDescription
datasetstring–Dataset(s) to search: resume, email, phone, mobile_phone, street_address, consumer_social, developer, all. Comma-separate; prefix '-' to exclude.
frominteger–Legacy offset (0-9999). Prefer scroll_token.
prettyboolean–Pretty-print the JSON response.
querystring–Elasticsearch query as a JSON string, e.g. {"query":{"term":{"job_company_name":"people data labs"}}} — pass the value of "query".
scroll_tokenstring–Pagination token from a previous response.
sizeinteger–Number of records to return (1-100). Default 1.
sqlstring–SQL query string, e.g. SELECT * FROM person WHERE job_company_name='people data labs'.
titlecaseboolean–Titlecase the returned data.

No output schema declared.

No examples provided.

Common questions

What is the io.usefulapi/peopledatalabs MCP server?

io.usefulapi/peopledatalabs is an MCP server 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 io.usefulapi/peopledatalabs MCP server safe to use?

io.usefulapi/peopledatalabs scores 81 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 io.usefulapi/peopledatalabs MCP server expose?

io.usefulapi/peopledatalabs 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 io.usefulapi/peopledatalabs MCP server require authentication?

Yes. io.usefulapi/peopledatalabs asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the io.usefulapi/peopledatalabs MCP server still maintained?

io.usefulapi/peopledatalabs is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.