Skip to content

People Data Labs MCP by usefulapi

io.usefulapi/peopledatalabsusefulapi.iostreamable-httpv1.40.4Scanned

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

8 tools: 5 change things and 3 only read.

Tools: 0 delete, 0 irreversible, 5 write, 3 read.
  • Reads private data · 4
  • Reads text others write · 1
  • Can send data out · 1
  • 3 findings

The remote endpoint did not answer the last look. Remote posture

Anlyon alternative

5 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the People Data Labs MCP by usefulapi can do

The People Data Labs MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 8 tools. It can create or change data (5 tools: pdl_person_identify, pdl_person_search, pdl_company_search, pdl_ip_enrich and 1 more), but cannot delete data. 3 tools only read.

4 tools read private data (pdl_person_enrich, pdl_person_search, pdl_company_search and 1 more); 1 tool brings in text other people can write (pdl_person_enrich); 1 tool can send data out of your system (pdl_person_identify). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

The fixed checks matched 3 findings (annotation-conflict). Each one comes with the text it matched.

Last scanned Oct 25, 2026, version 1.40.4.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

8 tools

Changes things 5Claude Code: ask
  • 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_person_identifyGiven broad, possibly-ambiguous attributes about a person, return up to 20 strongly-related profiles ranked by match score.Can send data outNo 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.

    What it can reach

    • outboundThe input takes a destination (input.phone): what the tool writes goes there.
    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
Only reads 3Show 3 read-only tools
  • 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.).Reads private dataReads text others writeNo findings

    Why it is in this group

    • The description's first verb is "find": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "find" and "email": it reads mail.
    • untrusted-inputThe description's first sentence says "find" and "email": it reads inbound email, which other people can write.
    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.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

4 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.

Reads private data4
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__peopledatalabs__pdl_person_identify"
    ]
  }
}

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

The remote endpoint did not answer the last look

Looked at Nov 20, 2026, 19:37 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
no
HTTP status of an anonymous initialize
not observed
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: The server redirected a POST to a different request.

Posture changes

  1. Oct 29, 2026
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 5 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://peopledatalabs.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://peopledatalabs.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Findings

Matches of fixed checks, with the text they matched.

3 warn
  • The server marks "pdl_person_search" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true}; The name "pdl_person_search" says "search": a word for reading.

    What this check looks for
  • The server marks "pdl_company_search" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true}; The name "pdl_company_search" says "search": a word for reading.

    What this check looks for
  • The server marks "pdl_job_posting_search" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true}; The name "pdl_job_posting_search" says "search": a word for reading.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 5 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://peopledatalabs.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://peopledatalabs.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Install

Pinned to version 1.40.4. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.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. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as peopledatalabs. Review it before you use it.

Capability tags behind 5 rules
  • mcp__peopledatalabs__pdl_person_enrich private-data, untrusted-input
  • mcp__peopledatalabs__pdl_person_identify outbound
  • mcp__peopledatalabs__pdl_person_search private-data
  • mcp__peopledatalabs__pdl_company_search private-data
  • mcp__peopledatalabs__pdl_job_posting_search private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.usefulapi/peopledatalabs/verify?hash=ca3ccc884127592098a129de9d64d9a6a295bcb4366370cf363ff3c576c4813c" | jq -e '.changed == false'

Pinned hash ca3ccc884127, from Oct 25, 2026, 23:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.usefulapi/peopledatalabs/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.usefulapi/peopledatalabs
[![Anlyon Radar](https://radar.anlyon.com/badge/io.usefulapi/peopledatalabs.svg)](https://radar.anlyon.com/servers/io.usefulapi/peopledatalabs)

Source: MCP Registry · repository. Synced Nov 18, 2026, 11:18 UTC.

People Data Labs MCP by usefulapi: questions and answers

Answered from the scan above, not from the publisher's description.

Is the People Data Labs MCP by usefulapi safe?

No scan can promise that. What its definitions show: 8 tools, 5 of which can change, send or delete something, and 3 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the People Data Labs MCP by usefulapi delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the People Data Labs MCP by usefulapi do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the People Data Labs MCP by usefulapi have?

8 tools: 5 write, 3 read. pdl_person_identify, pdl_person_search, pdl_company_search, pdl_ip_enrich, pdl_job_posting_search, pdl_person_enrich, pdl_company_enrich and pdl_autocomplete.

Does the People Data Labs MCP by usefulapi need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the People Data Labs MCP by usefulapi send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): pdl_person_identify.

Has the People Data Labs MCP by usefulapi changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.