# Usefulapi Peopledatalabs MCP server

Source: https://glimind.com/server/mcp-registry%2Fio.usefulapi%2Fpeopledatalabs
Registry id: `mcp-registry/io.usefulapi/peopledatalabs`
Status: auth-required (checked 2026-10-27T02:28:17.155Z)

## Verdict

Usefulapi Peopledatalabs MCP server answered 100% of Glimind's liveness checks over 30 days, better than 42% of MCP servers, with 60 ms median handshake and 0 outages in 90 days. Its agent-readiness grade is A (96/100) across 8 tools, costing an agent about 3,018 tokens to load. Checked every few minutes; no tool is ever called.

## Measurements (30 days)

| Metric | Value | Better than |
|---|---|---|
| Uptime, 30 days | 100% | 42% of MCP servers |
| Median handshake latency | 60 ms | 88% of MCP servers |
| p95 handshake latency | 302 ms | — |
| Checks in 30 days | 211 | — |
| Outages, 90 days | 0 | — |
| Median recovery | — | — |
| Agent-readiness score | 96/100 (A) | 82% of MCP servers |
| Tools | 8 | — |
| Tool-list size for an agent | ~3,018 tokens | 45% of MCP servers |
| Days observed | 28 | — |

## Install

```json
{
  "mcpServers": {
    "usefulapi-peopledatalabs-mcp-server": {
      "type": "http",
      "url": "https://peopledatalabs.usefulapi.io/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http usefulapi-peopledatalabs-mcp-server https://peopledatalabs.usefulapi.io/mcp
```

## Tools (8)

- `pdl_autocomplete`: 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 a
- `pdl_company_enrich`: Find the single best-matching company record. Requires a non-ambiguous input — name OR website OR ticker OR profile (website/ticker/profile resolve more reliabl
- `pdl_company_search`: 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
- `pdl_ip_enrich`: 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.
- `pdl_job_posting_search`: 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
- `pdl_person_enrich`: 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 lik
- `pdl_person_identify`: 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
- `pdl_person_search`: 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

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.