Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.markswendsen-code/yelp

NPM · @STRIDERLABS/MCP-YELP

MCP server for Yelp - search businesses, read reviews, make reservations

0 this week 83 Trust /100

Last scanned (11 hours ago)

Scores higher than 74% of npm servers

Category Search and Retrieval

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 30 of 94 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 143 days ago).Pass
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 584 tokens (~48/item across 12 items; 12 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (15)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 6 Nov 26 +1
    • Stability: 0.97 → pass security
    • Security disclosure: fail → unverified ▼ functional
  • 4 Nov 26 +1

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

  • 3 Nov 26 −2
    • Stability: pass → 0.90 functional
  • 31 Oct 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 28 Oct 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 22 Oct 26 +1
    • Stability: 0.97 → pass security
    • Security disclosure: unverified → fail ▼ functional
  • 21 Oct 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 20 Oct 26 −1
    • Stability: pass → 0.93 functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 7 Nov 2026 · Analysed npm/@striderlabs/mcp-yelp@0.1.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 94 packages
Packages resolved 94
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 12 exposed · ~584 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
yelp_check_wait_time ~33

Check estimated wait time at a restaurant (if available).

NameTypeReqDescription
businessIdstringyesYelp business ID

No output schema declared.

No examples provided.

yelp_find_similar ~45

Find businesses similar to a given business.

NameTypeReqDescription
businessIdstringyesYelp business ID to find similar places
limitnumber–Number of similar places

No output schema declared.

No examples provided.

yelp_get_business_details ~39

Get detailed information about a specific business including hours, menu, amenities.

NameTypeReqDescription
businessIdstringyesYelp business ID or URL slug

No output schema declared.

No examples provided.

yelp_get_collections ~45

Get curated Yelp collections for a location (best of lists, staff picks).

NameTypeReqDescription
categorystring–Collection category
locationstringyesLocation to search

No output schema declared.

No examples provided.

yelp_get_deals ~41

Get current deals and offers for businesses in a location.

NameTypeReqDescription
categorystring–Business category
locationstringyesLocation to search

No output schema declared.

No examples provided.

yelp_get_hours ~30

Get business hours including special hours and holidays.

NameTypeReqDescription
businessIdstringyesYelp business ID

No output schema declared.

No examples provided.

yelp_get_menu ~30

Get menu items and prices for a restaurant.

NameTypeReqDescription
businessIdstringyesYelp business ID

No output schema declared.

No examples provided.

yelp_get_photos ~50

Get photos for a specific business.

NameTypeReqDescription
businessIdstringyesYelp business ID
categorystring–Photo category
limitnumber–Number of photos to retrieve

No output schema declared.

No examples provided.

yelp_get_reviews ~55

Get reviews for a specific business with ratings and text.

NameTypeReqDescription
businessIdstringyesYelp business ID
limitnumber–Number of reviews to retrieve
sortBystring–Sort reviews by

No output schema declared.

No examples provided.

yelp_get_trending ~52

Get trending/hot new restaurants and businesses in a location.

NameTypeReqDescription
categorystring–Category filter (e.g., 'restaurants', 'nightlife')
locationstringyesLocation to search

No output schema declared.

No examples provided.

yelp_search_businesses ~68

Search for any type of business on Yelp (not just restaurants).

NameTypeReqDescription
categorystring–Business category
locationstringyesLocation (city, neighborhood, or address)
querystringyesSearch query (e.g., 'plumber', 'hair salon')

No output schema declared.

No examples provided.

yelp_search_restaurants ~96

Search for restaurants on Yelp by location, cuisine, price range, and more.

NameTypeReqDescription
locationstringyesLocation (city, neighborhood, or address)
openNowboolean–Only show places open now
priceRangestring–Price range filter
querystring–Search query (e.g., 'sushi', 'italian')
sortBystring–Sort order

No output schema declared.

No examples provided.

Install

How do I install the io.github.markswendsen-code/yelp MCP server?

io.github.markswendsen-code/yelp runs locally as an npm package, launched with npx -y @striderlabs/mcp-yelp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @striderlabs/mcp-yelp

# add to Claude Code
claude mcp add markswendsen-code-yelp -- npx -y @striderlabs/mcp-yelp
Common questions

What is the io.github.markswendsen-code/yelp MCP server?

io.github.markswendsen-code/yelp is an MCP server listed in the public MCP registry as io.github.markswendsen-code/yelp. MCP server for Yelp - search businesses, read reviews, make reservations. This page covers its npm package (@striderlabs/mcp-yelp).

Is the io.github.markswendsen-code/yelp MCP server safe to use?

io.github.markswendsen-code/yelp scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 7 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.markswendsen-code/yelp MCP server expose?

io.github.markswendsen-code/yelp exposes 12 tools: yelp_search_restaurants, yelp_search_businesses, yelp_get_business_details, yelp_get_reviews, yelp_get_photos, and 7 more. Their descriptions and schemas cost roughly 584 tokens of context every time the server is loaded.

Is the io.github.markswendsen-code/yelp MCP server still maintained?

io.github.markswendsen-code/yelp is still listed as active in the MCP registry. We last reached this channel on 7 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.markswendsen-code/yelp MCP server under?

io.github.markswendsen-code/yelp 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.markswendsen-code/yelp MCP server?

VerifyMCP ran 15 checks on io.github.markswendsen-code/yelp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about io.github.markswendsen-code/yelp: Security disclosure. 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.