Remote MCP · Endpoint

ailibri — каталог ИИ-сервисов MCP server

No. ailibri — каталог ИИ-сервисов answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.ailibri.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.asrplv/ailibri
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
276 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Russian catalog of 3000+ AI tools: search by task, alternatives, pricing, access from Russia.
Listing
From the official MCP registry (active).
Recent checks of ailibri — каталог ИИ-сервисов
CheckedResultHandshake
1 hour agoHandshake completed276 ms
2 days agoHandshake completed279 ms
5 days agoHandshake completed279 ms
7 days agoHandshake completed280 ms
9 days agoHandshake completed277 ms
11 days agoHandshake completed277 ms
13 days agoHandshake completed279 ms
15 days agoHandshake completed283 ms
17 days agoHandshake completed273 ms
19 days agoHandshake completed260 ms
20 days agoHandshake completed303 ms
21 days agoHandshake completed275 ms
22 days agoHandshake completed292 ms
25 days agoHandshake completed262 ms

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

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 ailibri — каталог ИИ-сервисов and makes no claim about it beyond what these checks measured.