Remote MCP · Endpoint

ee.wirt/landed MCP server

No. ee.wirt/landed answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://landed.wirt.ee/mcp

The last check completed an MCP handshake.

Registry name
ee.wirt/landed
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
562 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Read-after-write receipts for agents: did your write actually land? Free, signed, re-checkable.
Listing
From the official MCP registry (active).
Recent checks of ee.wirt/landed
CheckedResultHandshake
1 hour agoHandshake completed562 ms
22 hours agoHandshake completed375 ms
2 days agoHandshake completed354 ms
3 days agoHandshake completed345 ms
4 days agoHandshake completed362 ms
5 days agoHandshake completed346 ms
6 days agoHandshake completed366 ms
8 days agoHandshake completed348 ms
11 days agoHandshake completed351 ms
13 days agoHandshake completed392 ms
15 days agoHandshake completed380 ms
18 days agoHandshake completed412 ms
20 days agoHandshake completed831 ms
22 days agoHandshake completed410 ms
24 days agoHandshake completed351 ms

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

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 ee.wirt/landed and makes no claim about it beyond what these checks measured.