Remote MCP · Endpoint

Yelp data for agents MCP server

No. Yelp data for agents answered an MCP handshake 7 hours ago.

UpLast checked 7 hours ago

Server URL

https://yelp.fetcher.sh/mcp

The last check completed an MCP handshake.

Registry name
sh.fetcher.yelp/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
101 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
4 Yelp endpoints. Pay per call in USDC via x402.
Listing
From the official MCP registry (active).
Recent checks of Yelp data for agents
CheckedResultHandshake
7 hours agoHandshake completed101 ms
2 days agoHandshake completed98 ms
4 days agoHandshake completed331 ms
5 days agoHandshake completed107 ms
7 days agoHandshake completed103 ms
8 days agoHandshake completed122 ms
9 days agoHandshake completed225 ms
12 days agoHandshake completed85 ms
13 days agoHandshake completed244 ms
15 days agoHandshake completed180 ms
16 days agoHandshake completed121 ms
17 days agoHandshake completed73 ms
19 days agoHandshake completed80 ms
19 days agoHandshake completed74 ms
20 days agoHandshake completed101 ms
21 days agoHandshake completed116 ms
22 days agoHandshake completed231 ms

The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 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 Yelp data for agents and makes no claim about it beyond what these checks measured.