# io.github.CloudCorpRecords/yelpdata (npm · @reneturcios/yelpdata)

Yelp business data as JSON: search by keyword and location, place details, and the review feed.

- Trust score: 73/100 (medium)
- Change this week: +5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- npm · `@reneturcios/yelpdata`: 73/100 (this document), [markdown](https://verifymcp.io/servers/cloudcorprecords-yelpdata/reneturcios-yelpdata.md), [page](https://verifymcp.io/servers/cloudcorprecords-yelpdata/reneturcios-yelpdata)
- oci · `ghcr.io/cloudcorprecords/yelpdata`: 43/100, [markdown](https://verifymcp.io/servers/cloudcorprecords-yelpdata/ghcr-io-cloudcorprecords-yelpdata.md), [page](https://verifymcp.io/servers/cloudcorprecords-yelpdata/ghcr-io-cloudcorprecords-yelpdata)

## Channel facts

- Registry: `npm`
- Package: `@reneturcios/yelpdata`
- Version: `0.1.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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-11-21.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 92 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 10 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 62/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1218 tokens (~406/item across 3 items; 3 tools + 0 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 3 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 io.github.CloudCorpRecords/yelpdata MCP server?

io.github.CloudCorpRecords/yelpdata runs locally as an npm package, launched with npx -y @reneturcios/yelpdata mcp. 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 cloudcorprecords-yelpdata -- npx -y @reneturcios/yelpdata mcp
```

### Cursor

```json
{
  "mcpServers": {
    "cloudcorprecords-yelpdata": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/yelpdata",
        "mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cloudcorprecords-yelpdata": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/yelpdata",
        "mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add cloudcorprecords-yelpdata -- npx -y @reneturcios/yelpdata mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cloudcorprecords-yelpdata": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@reneturcios/yelpdata",
        "mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add cloudcorprecords-yelpdata --command npx --arg -y --arg @reneturcios/yelpdata --arg mcp
```

### Hermes

```yaml
mcp_servers:
  cloudcorprecords-yelpdata:
    command: "npx"
    args: ["-y", "@reneturcios/yelpdata", "mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "cloudcorprecords-yelpdata": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@reneturcios/yelpdata",
        "mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add cloudcorprecords-yelpdata -t stdio -c npx -a -y @reneturcios/yelpdata mcp
```

### Other

```json
{
  "mcpServers": {
    "cloudcorprecords-yelpdata": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/yelpdata",
        "mcp"
      ]
    }
  }
}
```

## 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-11-21 (score 73, +1)

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

### 2026-11-20 (score 72, +4)

- [functional improvement] Stability: unverified → 0.33

### 2026-11-11 (score 68, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-10 (score 53)

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: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/cloudcorprecords-yelpdata/reneturcios-yelpdata#diagnostics

## Score history

- 2026-11-21: 73
- 2026-11-20: 72
- 2026-11-19: 68
- 2026-11-18: 68
- 2026-11-17: 68
- 2026-11-16: 68
- 2026-11-15: 68
- 2026-11-14: 68
- 2026-11-13: 68
- 2026-11-12: 68
- 2026-11-11: 68
- 2026-11-10: 53

## Common questions

### What is the io.github.CloudCorpRecords/yelpdata MCP server?

io.github.CloudCorpRecords/yelpdata is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/yelpdata. Yelp business data as JSON: search by keyword and location, place details, and the review feed. This page covers its npm package (@reneturcios/yelpdata).

### Is the io.github.CloudCorpRecords/yelpdata MCP server safe to use?

io.github.CloudCorpRecords/yelpdata scores 73 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. 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 io.github.CloudCorpRecords/yelpdata MCP server expose?

io.github.CloudCorpRecords/yelpdata 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.

### Is the io.github.CloudCorpRecords/yelpdata MCP server still maintained?

io.github.CloudCorpRecords/yelpdata is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the io.github.CloudCorpRecords/yelpdata MCP server under?

io.github.CloudCorpRecords/yelpdata declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the io.github.CloudCorpRecords/yelpdata MCP server?

VerifyMCP ran 16 checks on io.github.CloudCorpRecords/yelpdata, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@reneturcios/yelpdata
- Socket report: https://socket.dev/npm/package/@reneturcios/yelpdata
- Repository: https://github.com/CloudCorpRecords/yelpdata
- Changelog RSS feed: https://verifymcp.io/servers/cloudcorprecords-yelpdata/reneturcios-yelpdata.xml
- Changelog JSON feed: https://verifymcp.io/servers/cloudcorprecords-yelpdata/reneturcios-yelpdata/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/cloudcorprecords-yelpdata/reneturcios-yelpdata.json
- HTML version of this page: https://verifymcp.io/servers/cloudcorprecords-yelpdata/reneturcios-yelpdata
