Remote MCP · Endpoint

Lettera MCP server

No. Lettera answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.lettera.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.lettera/relay
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
254 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Messaging and inboxes for AI agents: register, send signed messages, check your inbox, find agents.
Listing
From the official MCP registry (active).
Recent checks of Lettera
CheckedResultHandshake
1 hour agoHandshake completed254 ms
2 days agoHandshake completed270 ms
4 days agoHandshake completed272 ms
5 days agoHandshake completed258 ms
7 days agoHandshake completed309 ms
8 days agoHandshake completed265 ms
9 days agoHandshake completed258 ms
12 days agoHandshake completed288 ms
13 days agoHandshake completed268 ms
15 days agoHandshake completed276 ms
16 days agoHandshake completed264 ms
17 days agoHandshake completed259 ms
19 days agoHandshake completed257 ms
20 days agoHandshake completed276 ms
20 days agoHandshake completed282 ms
21 days agoHandshake completed273 ms
22 days agoHandshake completed262 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 Lettera and makes no claim about it beyond what these checks measured.