Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
Yelpdata is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
99/100
trust score
3
tools declared
local
runs on your machine
—
downloads a day
What it does
Yelp business data as JSON: search by keyword and location, place details, and the review feed.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user yelpdata-mcp '--' npx -y @reneturcios/yelpdata mcp
# 2 — ask your agent for something these tools do
# hasdata_yelp_place_getPlaceDetails, hasdata_yelp_reviews_getPlaceReviews, hasdata_yelp_search_getSearchResults
Yelpdata costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
CLAll 425 servers
CloudCorpRecords425 servers
28 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Yelpdata as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user yelpdata-mcp '--' npx -y @reneturcios/yelpdata mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
3 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
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…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| placeId | string | yes | The Yelp ID or Yelp Alias of the place. For example, 'jPIZ3FR5LNcwPuUHi2Fe4g' or 'mcdonalds-new-york-386'. |
| domain | string | no | Yelp domain to use. Default is www.yelp.com. |
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…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| placeId | string | yes | The Yelp ID of the place. For example, '-4ofMtrD7pSpZIX5pnDkig'. Yelp IDs can be obtained from the Yelp Search Scraper API. |
| domain | string | no | Yelp domain to use. Default is www.yelp.com. |
| query | string | no | 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. |
| sortBy | string | no | The order in which the reviews are returned. Defaults to relevanceDesc. |
| rating | string | no | 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 |
| languageCode | string | no | Language of the reviews to return, as a two-letter code (e.g., 'en', 'es', 'fr'). Defaults to en. |
| notRecommended | boolean | no | 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 reactions |
| start | number | no | 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 echoes |
| num | number | no | 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. |
| nextPageToken | string | no | 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 the |
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…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| keyword | string | yes | The search term for which to get the search results. |
| location | string | yes | The location where to search for businesses with the given keyword. |
| l | string | no | Parameter defines the distance or map radius for the search results. For example: g:-95.2486,29.8496,-95.4277,29.6324. |
| domain | string | no | Yelp domain to use. Default is www.yelp.com. |
| start | number | no | Result offset for pagination (e.g., 0 for the first page, 10 for the 2nd page, etc.). |
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Yelpdata or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 99 / 100
Release 0.1.0 · scanned 11 Nov 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score99
Findings0 threat · 0 capability
Capabilityminimal
Coveragesource
Verificationrepo
Surface digest4ffc4fd3b61fc8f7ac98821a9679b6c9bb83884d578d23beeda364cb26fdb601
Score vectorthreat 100 → client 99
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfacenot available
Implementation sourceread
Package metadataread
Live transportnot available
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
No tool surface was enumerated, so there is nothing to attribute a capability to.
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest4ffc4fd3b61fc8f7
Scanned2026-11-11
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.1.0. Pin a release below and the command asks for exactly that one.
0.1.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Yelpdata can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.