Remote MCP · Endpoint

AnySkills MCP server

No. AnySkills answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.anyskills.ru/

The last check completed an MCP handshake.

Registry name
ru.anyskills/anyskills
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
515 ms
Tools exposed
45 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
AnySkills online school: build courses, lessons and tests, publish, track student progress.
Listing
From the official MCP registry (active).
Recent checks of AnySkills
CheckedResultHandshake
1 hour agoHandshake completed515 ms
2 days agoHandshake completed505 ms
4 days agoHandshake completed525 ms
5 days agoHandshake completed516 ms
7 days agoHandshake completed510 ms
8 days agoHandshake completed531 ms
9 days agoHandshake completed506 ms
12 days agoHandshake completed516 ms
13 days agoHandshake completed562 ms
15 days agoHandshake completed689 ms
17 days agoHandshake completed513 ms
18 days agoHandshake completed519 ms
19 days agoHandshake completed524 ms
20 days agoHandshake completed527 ms
21 days agoHandshake completed571 ms
21 days agoHandshake completed510 ms
23 days agoHandshake completed524 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 AnySkills and makes no claim about it beyond what these checks measured.