landed

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

我該用這個嗎

品質與安全性

A
說明品質
100%
結構描述完整度
100%
命名品質
100%
汙染風險
100%
權限相符程度
100%
協定合規性
100%

根據工具定義與協定合規性的自動化分析。

上下文成本

~590Token(工具定義)
~1.0 KB典型回應大小
極小的注意力影響(128k 上下文的 0.46%)

這是每次將伺服器的工具載入模型上下文時所消耗的約略 token 數量。數量越高,可用於其他工作的注意力就越少。

安裝

一鍵安裝

將以下內容加入你的 `claude_desktop_config.json` 檔案:

{
  "mcpServers": {
    "landed": {
      "url": "https://landed.wirt.ee/mcp"
    }
  }
}

遠端端點

https://landed.wirt.ee/mcpstreamable-http

它能做什麼

工具清單

工具(3)

🟢 唯讀🟡 寫入🔴 刪除⚪ 未知
🟡verify_write(agent, action, url, expect, note)

Did 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 RIGHT NOW from an independent server and returns a signed receipt with the fresh HTTP status and whether the page really contains what you wrote. Call it ONCE, after the write. Do not poll. Give 'expect' a unique substring of what you wrote — without it the receipt only proves the page loads. The receipt is public-by-id and re-checkable later with get_receipt. Limits: 60 calls per agent name per hour; the target must be public http(s); robots.txt is respected; fetches identify themselves honestly.

輸入結構描述

{
  "type": "object",
  "properties": {
    "agent": {
      "type": "string",
      "maxLength": 200,
      "description": "Your stable agent name, e.g. 'fleetname/agent-7'. Receipts are filed under it."
    },
    "action": {
      "type": "string",
      "maxLength": 500,
      "description": "What you did, short, e.g. 'posted-comment' or 'edited-wiki-page'."
    },
    "url": {
      "type": "string",
      "maxLength": 2048,
      "description": "The exact http(s) URL you wrote to — the page the write should be visible on."
    },
    "expect": {
      "type": "string",
      "description": "Substring that must appear on the fetched page for the receipt to say found=true. Use a unique fragment of your write."
    },
    "note": {
      "type": "string",
      "description": "Optional human-readable context stored with the receipt."
    }
  },
  "required": [
    "agent",
    "action",
    "url"
  ]
}
🟡get_receipt(receipt_id)

Fetch 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 you to prove a past write. Receipts are public-by-id: anyone holding the receipt_id can re-check it.

輸入結構描述

{
  "type": "object",
  "properties": {
    "receipt_id": {
      "type": "string",
      "description": "The receipt_id hex string returned by verify_write."
    }
  },
  "required": [
    "receipt_id"
  ]
}
🟢read_log(agent)

Read 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.

輸入結構描述

{
  "type": "object",
  "properties": {
    "agent": {
      "type": "string",
      "maxLength": 200,
      "description": "The agent name whose receipts you want."
    }
  },
  "required": [
    "agent"
  ]
}

社群

為此伺服器評分

證據

近期觀測

已驗證未記錄版本3 個工具