Remote MCP · Endpoint

HasData Yelp MCP server

No. HasData Yelp answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://mcp.hasdata.com/mcp?apis=yelp

The last check completed an MCP handshake.

Registry name
com.hasdata/yelp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
50 ms
Tools exposed
3 tools
Uptime, last 30 days
94.1% from 17 checks
Described by its publisher as
Yelp business search, place details and the full review feed, as structured JSON.
Listing
From the official MCP registry (active).
Recent checks of HasData Yelp
CheckedResultHandshake
2 hours agoHandshake completed50 ms
2 days agoHandshake completed46 ms
4 days agoHandshake completed46 ms
6 days agoHandshake completed45 ms
7 days agoHandshake completed97 ms
8 days agoHandshake completed48 ms
9 days agoHandshake completed59 ms
12 days agoCredentials required—
14 days agoCredentials required—
15 days agoCredentials required—
17 days agoCredentials required—
18 days agoCredentials required—
19 days agoCredentials required—
20 days agoCredentials required—
20 days agoCredentials required—
22 days agoFailed - the server returned an HTTP error—
23 days agoCredentials required—

The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 16 responding of 17.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with HasData Yelp and makes no claim about it beyond what these checks measured.