# HasData Yelp (remote · mcp.hasdata.com)

Yelp business search, place details and the full review feed, as structured JSON.

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

## Components

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

## Channel facts

- Endpoint: `https://mcp.hasdata.com/mcp?apis=yelp`
- 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-16.

- **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**: 75/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).
  - Context-footprint check failed: tool/resource definitions use about 1353 tokens (~270/item across 5 items; 3 tools + 2 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 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 Yelp MCP server?

HasData Yelp is a hosted endpoint at https://mcp.hasdata.com/mcp?apis=yelp, 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-yelp 'https://mcp.hasdata.com/mcp?apis=yelp'
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

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-14 (score 85, +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-12 (score 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 23. That category is still filling its 30-day observation window: 5 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-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] Schema quality: unverified → 100
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Stability: unverified → 0.17
- [functional improvement] Tool coverage: unverified → 100
- [functional] First check of Tool coverage: 100
- [functional] First check of Schema quality: good
- [functional] First check of Schema quality: fail
- [functional] First check of Destructive annotations: pass
- [functional] First check of Schema quality: fail

### 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 (3)

### `hasdata_yelp_place_getPlaceDetails` (~169 tokens)

yelp_place: GET /

Get Yelp Place Details

Fetches a single Yelp business by Yelp ID or alias with domain targeting. Returns name, address, phone, website, price range, categories, overall rating, review count, hours, amenities, photos, and highlighted reviews. Use to enrich leads or listings with verified Yelp metadata, monitor a competitor's rating and review count over time, or validate hours/amenities before displaying venue details to end users.

Input parameters:

- `domain` (string): Yelp domain to use. Default is `www.yelp.com`.
- `placeId` (string, required): The Yelp ID or Yelp Alias of the place. For example, 'jPIZ3FR5LNcwPuUHi2Fe4g' or 'mcdonalds-new-york-386'.

### `hasdata_yelp_reviews_getPlaceReviews` (~789 tokens)

yelp_reviews: GET /

Get Yelp Place Reviews

Fetches the review feed of a single Yelp business by Yelp ID, with sorting (relevance, date, rating, elites), filtering by star rating, language and free-text query, and cursor pagination. To page, either step `start` by `num`, or resend the `pagination.nextPageToken` of the previous response as the `nextPageToken` parameter, keeping the other filters unchanged, until `pagination.hasNextPage` is false. The response reports the page it returned as `pagination.start` and `pagination.num`, matching the parameter names. Each review returns the author profile (name, location, review/friend/photo counts, Elite status), full text with language, star rating, timestamp, attached photos and videos, reader reactions, review tags (check-ins, first review, reservation and payment flags) and the owner reply when present. The response also carries the business review totals broken down by rating and by language. Use to monitor customer sentiment over time, mine complaints for a competitor, track how a business responds to negative reviews, or build rating-distribution and review-velocity datasets.

Input parameters:

- `domain` (string): Yelp domain to use. Default is `www.yelp.com`.
- `languageCode` (string): Language of the reviews to return, as a two-letter code (e.g., 'en', 'es', 'fr'). Defaults to en.
- `nextPageToken` (string): Opaque cursor for the next page, taken verbatim from `pagination.nextPageToken` of the previous response. It carries both the offset and the page size, so passing it alone continues the feed where th…
- `notRecommended` (boolean): Returns the reviews Yelp does not currently recommend (filtered out of the main feed by its recommendation software) instead of the recommended ones. These reviews carry no photos, videos or reaction…
- `num` (number): Number of reviews to return per page. The maximum is 49. Defaults to 49 for the recommended feed and to 10 when `notRecommended` is set. The response echoes it back as `pagination.num`.
- `placeId` (string, required): The Yelp ID of the place. For example, '-4ofMtrD7pSpZIX5pnDkig'. Yelp IDs can be obtained from the Yelp Search Scraper API.
- `query` (string): Note: Yelp ignores the `rating` filter while searching, so a query returns matching reviews of every star rating. Free-text query to search within the reviews of the place.
- `rating` (string): Note: Yelp ignores this filter when `query` is set, so a search returns matching reviews of every star rating. Filters the reviews by star rating. Possible values are 5, 4, 3, 2 and 1. To return only…
- `sortBy` (string): The order in which the reviews are returned. Defaults to relevanceDesc.
- `start` (number): Result offset for pagination. It skips the given number of reviews, so the step matches `num` (e.g., 0, 49, 98 for the recommended feed, or 0, 10, 20 when `notRecommended` is set). The response echoe…

### `hasdata_yelp_search_getSearchResults` (~260 tokens)

yelp_search: GET /

Get Yelp Search Results

Runs a Yelp business search by keyword and location with optional map-bounded radius via the `l` parameter (g:lon1,lat1,lon2,lat2), domain targeting, and offset-based pagination. Returns a ranked list of businesses with Yelp alias/ID, name, categories, rating, review count, price tier, and thumbnail. Use the returned aliases as input to the Yelp Place endpoint for full details, to power local-discovery UIs, or to build market-share/competitor datasets for a niche in a given geography.

Input parameters:

- `domain` (string): Yelp domain to use. Default is `www.yelp.com`.
- `keyword` (string, required): The search term for which to get the search results.
- `l` (string): Parameter defines the distance or map radius for the search results. For example: `g:-95.2486,29.8496,-95.4277,29.6324`.
- `location` (string, required): The location where to search for businesses with the given keyword.
- `start` (number): Result offset for pagination (e.g., 0 for the first page, 10 for the 2nd page, etc.).

## Diagnostics

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

## Score history

- 2026-10-16: 85
- 2026-10-15: 85
- 2026-10-14: 85
- 2026-10-13: 84
- 2026-10-12: 84
- 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 Yelp MCP server?

HasData Yelp is an MCP server listed in the public MCP registry as com.hasdata/yelp. Yelp business search, place details and the full review feed, as structured JSON. This page covers its hosted endpoint (https://mcp.hasdata.com/mcp?apis=yelp).

### Is the HasData Yelp MCP server safe to use?

HasData Yelp scores 85 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 Yelp MCP server expose?

HasData Yelp exposes 3 tools: hasdata_yelp_place_getPlaceDetails, hasdata_yelp_reviews_getPlaceReviews, hasdata_yelp_search_getSearchResults. Their descriptions and schemas cost roughly 1,218 tokens of context every time the server is loaded.

### Does the HasData Yelp MCP server require authentication?

Yes. HasData Yelp 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 Yelp MCP server still maintained?

HasData Yelp is still listed as active in the MCP registry. We last reached this channel on 16 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=yelp
- Authorisation metadata: https://mcp.hasdata.com/.well-known/oauth-protected-resource/mcp
- Repository: https://github.com/HasData/yelp-mcp
- Website: https://hasdata.com/apis/yelp-api
- Changelog RSS feed: https://verifymcp.io/servers/com-hasdata-yelp/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-hasdata-yelp/mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-hasdata-yelp/mcp