Remote MCP · Endpoint

mcp-catalog MCP server

No. mcp-catalog answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp-catalog.ru/mcp

The last check completed an MCP handshake.

Registry name
io.github.atomno-mcp/mcp-catalog
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
768 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Search MCP servers in the public mcp-catalog.ru directory.
Listing
From the official MCP registry (active).
Recent checks of mcp-catalog
CheckedResultHandshake
1 hour agoHandshake completed768 ms
2 days agoHandshake completed541 ms
4 days agoHandshake completed545 ms
5 days agoHandshake completed686 ms
7 days agoHandshake completed610 ms
8 days agoHandshake completed546 ms
9 days agoHandshake completed570 ms
12 days agoHandshake completed558 ms
13 days agoHandshake completed682 ms
15 days agoHandshake completed484 ms
16 days agoHandshake completed512 ms
18 days agoHandshake completed1.04 s
19 days agoHandshake completed513 ms
20 days agoHandshake completed521 ms
20 days agoHandshake completed554 ms
21 days agoHandshake completed648 ms
22 days agoHandshake completed522 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 mcp-catalog and makes no claim about it beyond what these checks measured.