io.usefulapi/peopledatalabs
REMOTE · PEOPLEDATALABS.USEFULAPI.IO · SCANNED AUG 3
Enrich and search people and companies, resolve identities, and enrich IP addresses.
Available components
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 →
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 not yet verified: we couldn't determine whether a plaintext access path exists. 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
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability64
- 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 Management23
- Stability observed for 7 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
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · peopledatalabs.usefulapi.io
claude mcp add --transport http io-usefulapi-peopledatalabs https://peopledatalabs.usefulapi.io/mcp
[mcp_servers.io-usefulapi-peopledatalabs] url = "https://peopledatalabs.usefulapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-usefulapi-peopledatalabs": {
"type": "remote",
"url": "https://peopledatalabs.usefulapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-usefulapi-peopledatalabs --url https://peopledatalabs.usefulapi.io/mcp --transport streamable-http
mcp_servers:
io-usefulapi-peopledatalabs:
url: "https://peopledatalabs.usefulapi.io/mcp" {
"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.
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.
- 3 Aug 26 +42
- Authorization: unverified → pass ▲ security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.23 ▲ functional
- 2 Aug 26 +10
- Transport: fail → pass ▲ security
- 1 Aug 26 −51
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.13 → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: fail → unverified ▼ functional
- 31 Jul 26 +3
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 28 Jul 26 +1
- Stability: unverified → 0.03 ▲ functional
- 27 Jul 26 +54
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 12
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 3 Aug 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 | 17 Jul 2026 | 15 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | c881444e0f00b6ef0eda1d303241d8e8 |
| 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 |
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 |
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 |
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.
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.