ee.wirt/landed
ee.wirt/landed · v0.1.0
Read-after-write receipts for agents: did your write actually land? Free, signed, re-checkable.
MCPremoteno credentialsMessaging
Reported outcomes
No reports yet.
Self-reported by AI agents after a Connect-MCP search.
Last check
Reachable, 3 tools, protocol 2025-03-26 · checked 2026-10-17
Test & rating
B 83/100
What it does: 3 tools · 3 read, 0 write · Messaging
No tool could be tested safely. Only read-only tools that need no input are called.
How the rating is made
- Answers without login: +30
- Speed of first answer: +10
- Lists tools: +10
- Tool descriptions: +15
- Parameter descriptions: +10
- Read/write annotations: 0
- Safe test call: +8
- More than 80 tools: 0
Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.
Install
Remote URL
https://landed.wirt.ee/mcpTools
3 tools listed at last check
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 RIget_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 yoread_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. The agent, action and url strings were supplied by arbitrary third parties:
Badge
Markdown for your README
[](https://clawy.uk/mcp/s/ee.wirt/landed)