peopledatalabs
Server Details
Enrich and search people and companies, resolve identities, and enrich IP addresses.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- m190/usefulapi-mcp
- GitHub Stars
- 0
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Score is being calculated. Check back soon.
Available Tools
8 toolspdl_autocompleteAutocomplete search valuesRead-onlyInspect
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 | Required | Description | Default |
|---|---|---|---|
| size | No | Max suggestions to return. Default 10. | |
| text | No | Partial text to get suggestions for, e.g. 'stanf'. | |
| field | Yes | Field to autocomplete: e.g. company, school, location, region, country, industry, title, role, sub_role, skill, major. | |
| pretty | No | Pretty-print the JSON response. | |
| titlecase | No | Titlecase the returned data. |
pdl_company_enrichEnrich a companyRead-onlyInspect
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 | Required | Description | Default |
|---|---|---|---|
| name | No | Company name, e.g. 'People Data Labs'. | |
| pdl_id | No | PDL id for a company record. | |
| pretty | No | Pretty-print the JSON response. | |
| region | No | Company state / region. | |
| ticker | No | Stock ticker for a public company, e.g. 'AAPL'. | |
| country | No | Company country. | |
| profile | No | Company social profile URL, e.g. a LinkedIn company URL. | |
| website | No | Company website, e.g. 'google.com' (most reliable). | |
| locality | No | Company city / locality. | |
| location | No | Company location free-text. | |
| titlecase | No | Titlecase the returned data. |
pdl_company_searchSearch companiesRead-onlyInspect
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 | Required | Description | Default |
|---|---|---|---|
| sql | No | SQL query string, e.g. SELECT * FROM company WHERE industry='computer software'. | |
| from | No | Legacy offset (0-9999). Prefer scroll_token. | |
| size | No | Number of records to return (1-100). Default 1. | |
| query | No | Elasticsearch query as a JSON string, e.g. {"query":{"term":{"industry":"computer software"}}} — pass the value of "query". | |
| pretty | No | Pretty-print the JSON response. | |
| titlecase | No | Titlecase the returned data. | |
| scroll_token | No | Pagination token from a previous response. |
pdl_ip_enrichEnrich an IP addressRead-onlyInspect
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 | Required | Description | Default |
|---|---|---|---|
| ip | Yes | The IP address to enrich, e.g. '72.212.42.169'. | |
| pretty | No | Pretty-print the JSON response. | |
| titlecase | No | Titlecase the returned data. | |
| return_person | No | Include associated person data if available. | |
| min_confidence | No | Minimum confidence level required to return a match. |
pdl_job_posting_searchSearch job postingsRead-onlyInspect
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 | Required | Description | Default |
|---|---|---|---|
| sql | No | SQL query string over the job posting dataset. | |
| size | No | Number of records to return (1-100). Default 1. | |
| query | No | Elasticsearch query as a JSON string, e.g. {"query":{"term":{"title_role":"engineering"}}} — pass the value of "query". | |
| pretty | No | Pretty-print the JSON response. | |
| scroll_token | No | Pagination token from a previous response. |
pdl_person_enrichEnrich a personRead-onlyInspect
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 | Required | Description | Default |
|---|---|---|---|
| lid | No | LinkedIn numerical ID. | |
| name | No | Full name, e.g. 'Sean Thorne'. | |
| No | Email address, or an array of email addresses. | ||
| phone | No | Phone number (E.164 or local). | |
| pdl_id | No | PDL persistent ID for a person record. | |
| pretty | No | Pretty-print the JSON response. | |
| region | No | State / region, e.g. 'california'. | |
| school | No | School name or website the person attended. | |
| company | No | Company name, website, or PDL company id the person works at. | |
| country | No | Country name, e.g. 'united states'. | |
| profile | No | Social profile URL(s), e.g. a LinkedIn URL. String or array. | |
| locality | No | City / locality, e.g. 'san francisco'. | |
| location | No | Free-text location, e.g. 'San Francisco, CA, USA'. | |
| required | No | Only return a match that contains these fields, e.g. 'emails AND mobile_phone'. | |
| last_name | No | Last / family name. | |
| titlecase | No | Titlecase the returned data (default false = lowercase). | |
| birth_date | No | Birth date (yyyy or yyyy-mm-dd). | |
| first_name | No | First / given name. | |
| postal_code | No | Postal / ZIP code (assumed US if no country). | |
| min_likelihood | No | Only return a 200 if match confidence >= this (1-10). |
pdl_person_identifyIdentify a personRead-onlyInspect
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 | Required | Description | Default |
|---|---|---|---|
| lid | No | LinkedIn numerical ID. | |
| name | No | Full name, e.g. 'Sean Thorne'. | |
| No | Email address, or an array of email addresses. | ||
| phone | No | Phone number (E.164 or local). | |
| pdl_id | No | PDL persistent ID for a person record. | |
| pretty | No | Pretty-print the JSON response. | |
| region | No | State / region, e.g. 'california'. | |
| school | No | School name or website the person attended. | |
| company | No | Company name, website, or PDL company id the person works at. | |
| country | No | Country name, e.g. 'united states'. | |
| profile | No | Social profile URL(s), e.g. a LinkedIn URL. String or array. | |
| locality | No | City / locality, e.g. 'san francisco'. | |
| location | No | Free-text location, e.g. 'San Francisco, CA, USA'. | |
| last_name | No | Last / family name. | |
| titlecase | No | Titlecase the returned data (default false = lowercase). | |
| birth_date | No | Birth date (yyyy or yyyy-mm-dd). | |
| first_name | No | First / given name. | |
| postal_code | No | Postal / ZIP code (assumed US if no country). |
pdl_person_searchSearch peopleRead-onlyInspect
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 | Required | Description | Default |
|---|---|---|---|
| sql | No | SQL query string, e.g. SELECT * FROM person WHERE job_company_name='people data labs'. | |
| from | No | Legacy offset (0-9999). Prefer scroll_token. | |
| size | No | Number of records to return (1-100). Default 1. | |
| query | No | Elasticsearch query as a JSON string, e.g. {"query":{"term":{"job_company_name":"people data labs"}}} — pass the value of "query". | |
| pretty | No | Pretty-print the JSON response. | |
| dataset | No | Dataset(s) to search: resume, email, phone, mobile_phone, street_address, consumer_social, developer, all. Comma-separate; prefix '-' to exclude. | |
| titlecase | No | Titlecase the returned data. | |
| scroll_token | No | Pagination token from a previous response. |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!