Remote MCP · Endpoint

YloService MCP server

No. YloService answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://yloservice.com/mcp

The last check completed an MCP handshake.

Registry name
com.yloservice/search
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
296 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Search local service providers by skill and country
Listing
From the official MCP registry (active).
Recent checks of YloService
CheckedResultHandshake
1 hour agoHandshake completed296 ms
1 day agoHandshake completed285 ms
3 days agoHandshake completed300 ms
3 days agoHandshake completed291 ms
4 days agoHandshake completed301 ms
5 days agoHandshake completed331 ms
7 days agoHandshake completed341 ms
10 days agoHandshake completed299 ms
12 days agoHandshake completed311 ms
15 days agoHandshake completed295 ms
17 days agoHandshake completed277 ms
19 days agoHandshake completed290 ms
21 days agoHandshake completed274 ms
23 days agoHandshake completed284 ms
25 days agoHandshake completed271 ms
26 days agoHandshake completed279 ms
28 days agoHandshake completed275 ms
29 days agoHandshake completed270 ms

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

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 YloService and makes no claim about it beyond what these checks measured.