Remote MCP · Endpoint

dev.lingo/main MCP server

No. dev.lingo/main answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.lingo.dev/main

The last check completed an MCP handshake.

Registry name
dev.lingo/main
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
785 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Lingo.dev MCP Server - World-class i18n implementation with ICU MessageFormat.
Listing
From the official MCP registry (active).
Recent checks of dev.lingo/main
CheckedResultHandshake
1 hour agoHandshake completed785 ms
2 days agoHandshake completed91 ms
4 days agoHandshake completed552 ms
5 days agoHandshake completed886 ms
7 days agoHandshake completed78 ms
8 days agoHandshake completed874 ms
9 days agoHandshake completed1.09 s
12 days agoHandshake completed619 ms
13 days agoHandshake completed807 ms
15 days agoHandshake completed57 ms
16 days agoHandshake completed869 ms
17 days agoHandshake completed105 ms
19 days agoHandshake completed41 ms
20 days agoHandshake completed58 ms
20 days agoHandshake completed789 ms
21 days agoHandshake completed816 ms
22 days agoHandshake completed59 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 dev.lingo/main and makes no claim about it beyond what these checks measured.