Remote MCP · Endpoint

Layero MCP server

No. Layero answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.layero.ru/mcp

The last check completed an MCP handshake.

Registry name
ru.layero/layero
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
410 ms
Tools exposed
36 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Deploy and operate sites on Layero — hosting with build servers in Russia: domains, env, Data API.
Listing
From the official MCP registry (active).
Recent checks of Layero
CheckedResultHandshake
1 hour agoHandshake completed410 ms
2 days agoHandshake completed567 ms
4 days agoHandshake completed401 ms
5 days agoHandshake completed366 ms
7 days agoHandshake completed376 ms
8 days agoHandshake completed405 ms
9 days agoHandshake completed364 ms
12 days agoHandshake completed428 ms
13 days agoHandshake completed395 ms
15 days agoHandshake completed369 ms
17 days agoHandshake completed383 ms
18 days agoHandshake completed375 ms
19 days agoHandshake completed371 ms
20 days agoHandshake completed450 ms
21 days agoHandshake completed376 ms
21 days agoHandshake completed367 ms
23 days agoHandshake completed408 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 Layero and makes no claim about it beyond what these checks measured.