Remote MCP · Endpoint

dev.lekta/lekta MCP server

No. dev.lekta/lekta answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://lekta.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.lekta/lekta
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
440 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Audits how AI answer engines read a page and grades it A+ to F across four measured layers.
Listing
From the official MCP registry (active).
Recent checks of dev.lekta/lekta
CheckedResultHandshake
1 hour agoHandshake completed440 ms
1 day agoHandshake completed393 ms
2 days agoHandshake completed1.33 s
3 days agoHandshake completed405 ms
4 days agoHandshake completed376 ms
5 days agoHandshake completed403 ms
6 days agoHandshake completed371 ms
9 days agoHandshake completed399 ms
12 days agoHandshake completed402 ms
14 days agoHandshake completed539 ms
16 days agoHandshake completed716 ms
18 days agoHandshake completed392 ms
20 days agoHandshake completed494 ms
22 days agoHandshake completed358 ms
24 days agoHandshake completed372 ms
26 days agoHandshake completed392 ms
27 days agoHandshake completed468 ms
29 days agoHandshake completed424 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with dev.lekta/lekta and makes no claim about it beyond what these checks measured.