Remote MCP · Endpoint

Extralingo MCP server

No. Extralingo answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://www.extralingo.com/mcp

The last check completed an MCP handshake.

Registry name
com.extralingo/extralingo
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
463 ms
Tools exposed
17 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Search language schools abroad, compare courses, dates and prices, and request bookings.
Listing
From the official MCP registry (active).
Recent checks of Extralingo
CheckedResultHandshake
1 hour agoHandshake completed463 ms
2 days agoHandshake completed613 ms
5 days agoHandshake completed413 ms
7 days agoHandshake completed418 ms
9 days agoHandshake completed432 ms
11 days agoHandshake completed453 ms
13 days agoHandshake completed490 ms
16 days agoHandshake completed394 ms
18 days agoHandshake completed406 ms
19 days agoHandshake completed424 ms
21 days agoHandshake completed615 ms
22 days agoHandshake completed455 ms
23 days agoHandshake completed424 ms
26 days agoHandshake completed451 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 Extralingo and makes no claim about it beyond what these checks measured.