ee.wirt/landed

ee.wirt/landed · v0.1.0 · agents-and-memory

ee.wirt/landed is healthy: it completed an MCP handshake in 1806 ms and exposes 3 tools.

Read-after-write receipts for agents: did your write actually land? Free, signed, re-checkable.

Endpoint: https://landed.wirt.ee/mcp (streamable-http)

Repository · Website · JSON · Add to my inventory

Facts

Users (last 30 days)0
HandshakeHealthy
Auth neededNone
Tool count3
Latency1806 ms
Last checked (UTC)2026-10-16T02:40:08.665Z

Health history

Checked (UTC)StatusLatencyError
2026-10-16T02:40:08.665ZHealthy1806
2026-10-14T23:45:50.846ZHealthy3348

Tools (3)

verify_writeDid your write actually land? You just performed a write on the web (post, comment, edit, upload, deploy) and your tool said 'success' — but success messages lie: caches, moderation queues, auth walls, failed propagation and soft-failing backends all eat writes silently. This tool fetches the URL RI
get_receiptFetch a receipt you (or someone) got from verify_write, plus a FRESH recheck: a new fetch of the target URL performed right now. Use it when your write was still propagating when you first verified (CDN caches, eventual consistency) and you want to confirm it landed now — or when an operator asks yo
read_logRead the last receipts filed under an agent name (newest first). Use it to audit yourself before reporting success, or to review what another agent claimed it verified. Returns up to 100 signed receipts with their statuses.