HasData Yellow Pages is an MCP server published by com.hasdata, hosted at mcp.hasdata.com. When last checked on 2026-11-22 it was working: it answers and lists its tools. It declares 2 tools, including hasdata_yellowpages_place_getPlaceDetails, hasdata_yellowpages_search_getSearchResults.
Yellow Pages local business search and full business listings, as structured JSON.
81 connections through 5 shared values. Tap any node.
Inferred from the host name and headers: what a server runs on, not who runs it.
Get Yellow Pages Place Details Scrapes a single YellowPages business listing URL and returns business name, street address, city, region, zip code, coordinates, phone, website, hours of operation, payment methods, categories, ratings, review counts, photos, and service descriptions, plus email and years in business on yellowpages.com listings. Fields the listing does not publish, such as a street address, hours, or email, are omitted from the response. Use to hydrate a lead with verified NAP data, build a B2B contact database from YellowPages URLs collected via the Search endpoint, or validate business legitimacy and hours before outreach.
| Parameter | Type | Description |
|---|---|---|
| url * | string | The YellowPages URL of the place. |
None yet. Changes appear after a server's second daily check.
Squares are this server's values; dots are other servers sharing them. A shared address or publisher is a lead, not proof of a common operator.
{
"name": "hasdata_yellowpages_place_getPlaceDetails",
"title": "yellowpages_place: GET /",
"description": "Get Yellow Pages Place Details\n\nScrapes a single YellowPages business listing URL and returns business name, street address, city, region, zip code, coordinates, phone, website, hours of operation, payment methods, categories, ratings, review counts, photos, and service descriptions, plus email and years in business on yellowpages.com listings. Fields the listing does not publish, such as a street address, hours, or email, are omitted from the response. Use to hydrate a lead with verified NAP data, build a B2B contact database from YellowPages URLs collected via the Search endpoint, or validate business legitimacy and hours before outreach.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"url"
],
"properties": {
"url": {
"type": "string",
"description": "The YellowPages URL of the place."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}Get YellowPages Search Results Runs a YellowPages business search by keyword plus location with sort (default, distance, averageRating, name; yellowpages.com only), country domain targeting, and page-based pagination. Returns each business with name, listing URL, phone, address, categories, rating, review count, and years in business. Use for B2B lead generation by niche and city, feeding the resulting URLs into the YellowPages Place endpoint for enrichment, or building geo-targeted prospect lists for sales outreach.
| Parameter | Type | Description |
|---|---|---|
| page | number | The page number of the results to retrieve. |
| sort | string | The sorting option for the search results. |
| domain | string | YellowPages domain to use. Default is `www.yellowpages.com`. |
| keyword * | string | The search term for which to get the search results. |
| location * | string | The location where to search for businesses with the given keyword. |
{
"name": "hasdata_yellowpages_search_getSearchResults",
"title": "yellowpages_search: GET /",
"description": "Get YellowPages Search Results\n\nRuns a YellowPages business search by keyword plus location with sort (default, distance, averageRating, name; yellowpages.com only), country domain targeting, and page-based pagination. Returns each business with name, listing URL, phone, address, categories, rating, review count, and years in business. Use for B2B lead generation by niche and city, feeding the resulting URLs into the YellowPages Place endpoint for enrichment, or building geo-targeted prospect lists for sales outreach.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"keyword",
"location"
],
"properties": {
"page": {
"type": "number",
"description": "The page number of the results to retrieve."
},
"sort": {
"enum": [
"default",
"distance",
"averageRating",
"name"
],
"type": "string",
"description": "The sorting option for the search results."
},
"domain": {
"enum": [
"www.yellowpages.com",
"www.yellowpages.ca"
],
"type": "string",
"description": "YellowPages domain to use. Default is `www.yellowpages.com`."
},
"keyword": {
"type": "string",
"description": "The search term for which to get the search results."
},
"location": {
"type": "string",
"description": "The location where to search for businesses with the given keyword."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}HasData MCP server. Tools are generated from generated/endpoints.json. Listing tools, prompts and resources needs no credentials; calling a tool needs a HasData OAuth connection or an x-api-key header. This connection is limited to 2 of 88 HasData tools (apis=yellowpages). Other HasData APIs exist but are not available here.
Names, descriptions and schemas were written by the server and are shown as data.
Shared addresses on big platforms (Cloudflare, Vercel and the like) put unrelated servers together; those are marked shared_infrastructure. A match is a pivot, not a link between operators.