# HasData Yellow Pages (remote · mcp.hasdata.com)

Yellow Pages local business search and full business listings, as structured JSON.

- Trust score: 86/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-17

## Components

- remote · `mcp.hasdata.com`: 86/100 (this document), [markdown](https://verifymcp.io/servers/com-hasdata-yellowpages/mcp.md), [page](https://verifymcp.io/servers/com-hasdata-yellowpages/mcp)
- npm · `@hasdata/yellowpages-mcp`: 49/100, [markdown](https://verifymcp.io/servers/com-hasdata-yellowpages/hasdata-yellowpages-mcp.md), [page](https://verifymcp.io/servers/com-hasdata-yellowpages/hasdata-yellowpages-mcp)
- pypi · `hasdata-yellowpages-mcp`: 34/100, [markdown](https://verifymcp.io/servers/com-hasdata-yellowpages/hasdata-yellowpages-mcp-2.md), [page](https://verifymcp.io/servers/com-hasdata-yellowpages/hasdata-yellowpages-mcp-2)

## Channel facts

- Endpoint: `https://mcp.hasdata.com/mcp?apis=yellowpages`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.2`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-17.

- **Endpoint Security**: 97/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 82/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 488 tokens (~122/item across 4 items; 2 tools + 2 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the HasData Yellow Pages MCP server?

HasData Yellow Pages is a hosted endpoint at https://mcp.hasdata.com/mcp?apis=yellowpages, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-hasdata-yellowpages 'https://mcp.hasdata.com/mcp?apis=yellowpages'
```

### Cursor

```json
{
  "mcpServers": {
    "com-hasdata-yellowpages": {
      "url": "https://mcp.hasdata.com/mcp?apis=yellowpages"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-hasdata-yellowpages": {
      "type": "http",
      "url": "https://mcp.hasdata.com/mcp?apis=yellowpages"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-hasdata-yellowpages]
url = "https://mcp.hasdata.com/mcp?apis=yellowpages"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-hasdata-yellowpages": {
      "type": "remote",
      "url": "https://mcp.hasdata.com/mcp?apis=yellowpages",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-hasdata-yellowpages --url 'https://mcp.hasdata.com/mcp?apis=yellowpages' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-hasdata-yellowpages:
    url: "https://mcp.hasdata.com/mcp?apis=yellowpages"
```

### Netclaw

```json
{
  "McpServers": {
    "com-hasdata-yellowpages": {
      "Transport": "http",
      "Url": "https://mcp.hasdata.com/mcp?apis=yellowpages"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-hasdata-yellowpages -t streamable-http -u 'https://mcp.hasdata.com/mcp?apis=yellowpages'
```

### Other

```json
{
  "mcpServers": {
    "com-hasdata-yellowpages": {
      "type": "http",
      "url": "https://mcp.hasdata.com/mcp?apis=yellowpages"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-16 (score 86, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-14 (score 85, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-12 (score 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-10 (score 83, +44)

- [security improvement] Transport: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [security] First check of Judged manipulation: pass
- [security] Authorization: Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Stability: unverified → 0.10
- [functional improvement] Schema quality: unverified → 100
- [functional] First check of Schema quality: fail
- [functional] First check of Destructive annotations: pass
- [functional] First check of Tool coverage: 100
- [functional] First check of Schema quality: good
- [functional] First check of Schema quality: pass

### 2026-09-28 (score 39, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-25 (score 39, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-22 (score 39)

First indexed and scored.

## MCP tools (2)

### `hasdata_yellowpages_place_getPlaceDetails` (~158 tokens)

yellowpages_place: GET /

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.

Input parameters:

- `url` (string, required): The YellowPages URL of the place.

### `hasdata_yellowpages_search_getSearchResults` (~202 tokens)

yellowpages_search: GET /

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.

Input parameters:

- `domain` (string): YellowPages domain to use. Default is `www.yellowpages.com`.
- `keyword` (string, required): The search term for which to get the search results.
- `location` (string, required): The location where to search for businesses with the given keyword.
- `page` (number): The page number of the results to retrieve.
- `sort` (string): The sorting option for the search results.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-hasdata-yellowpages/mcp#diagnostics

## Score history

- 2026-10-17: 86
- 2026-10-16: 86
- 2026-10-15: 85
- 2026-10-14: 85
- 2026-10-13: 84
- 2026-10-12: 84
- 2026-10-11: 83
- 2026-10-10: 83
- 2026-10-04: 39
- 2026-10-03: 39
- 2026-10-02: 39
- 2026-10-01: 39
- 2026-09-30: 39
- 2026-09-29: 39
- 2026-09-28: 39
- 2026-09-27: 39
- 2026-09-26: 39
- 2026-09-25: 39
- 2026-09-24: 39
- 2026-09-23: 39
- 2026-09-22: 39

## Common questions

### What is the HasData Yellow Pages MCP server?

HasData Yellow Pages is an MCP server listed in the public MCP registry as com.hasdata/yellowpages. Yellow Pages local business search and full business listings, as structured JSON. This page covers its hosted endpoint (https://mcp.hasdata.com/mcp?apis=yellowpages).

### Is the HasData Yellow Pages MCP server safe to use?

HasData Yellow Pages scores 86 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the HasData Yellow Pages MCP server expose?

HasData Yellow Pages exposes 2 tools: hasdata_yellowpages_place_getPlaceDetails, hasdata_yellowpages_search_getSearchResults. Their descriptions and schemas cost roughly 360 tokens of context every time the server is loaded.

### Does the HasData Yellow Pages MCP server require authentication?

Yes. HasData Yellow Pages asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the HasData Yellow Pages MCP server still maintained?

HasData Yellow Pages is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.hasdata.com/mcp?apis=yellowpages
- Authorisation metadata: https://mcp.hasdata.com/.well-known/oauth-protected-resource/mcp
- Repository: https://github.com/HasData/yellowpages-mcp
- Website: https://hasdata.com/apis/yellow-pages-api
- Changelog RSS feed: https://verifymcp.io/servers/com-hasdata-yellowpages/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-hasdata-yellowpages/mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-hasdata-yellowpages/mcp