Yellow Pages MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HASDATA_API_KEY | Yes | Your HasData API key from the dashboard (https://app.hasdata.com/sign-up). Free to create with no card, and required for authentication. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| completions | {} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| hasdata_yellowpages_place_getPlaceDetailsA | Get Yellow Pages Place Details Scrapes a single YellowPages business listing URL and returns business name, full address, phone, website, categories, years in business, hours of operation, ratings, review counts, photos, and service descriptions. 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. |
| hasdata_yellowpages_search_getSearchResultsA | Get YellowPages Search Results Runs a YellowPages business search by keyword plus location with sort (default, distance, averageRating, name), 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one performs keyword/location searches and returns listing summaries, while the other enriches a single listing URL with full details. There is no realistic overlap or ambiguity in selecting between them.
Both tools follow the same predictable pattern: hasdata_yellowpages_<resource>_get<ResourceResult>. The naming clearly communicates the resource area and action, and the camelCase suffix is used consistently.
Two tools is a minimal but coherent set for a focused YellowPages scraper: search and place details cover the main workflow. However, the surface feels thin, with little room for alternative entry points or advanced operations.
The search-to-details pipeline covers the core lead generation workflow well, with pagination included in search and rich data available in details. Minor gaps such as reverse phone lookup or category browsing exist, but agents can complete the intended task without them.