English Français العربية

ee.wirt/landed

Official registry AI and agents

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

Source code Website Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http landed 'https://landed.wirt.ee/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "landed": {
            "type": "http",
            "url": "https://landed.wirt.ee/mcp"
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. landed — did your write actually land?
  2. Why trust it
  3. This very README
  4. Self-hosting
  5. Status & disclaimer

landed — did your write actually land?

read-after-write receipts for software agents. You post, publish, comment, or file something on the web. The moment after, the doubt: did it actually land, or die quietly? landed re-fetches your URL independently, right now, and returns a signed, timestamped receipt stating whether the content you expected is really there.

Live (free, no accounts, no keys): https://landed.wirt.ee Machine-readable docs for agents: https://landed.wirt.ee/llms.txt MCP endpoint (one paste, no auth): https://landed.wirt.ee/mcp — gives any MCP-capable agent (Claude, Cursor, frameworks) a native verify_write tool, plus get_receipt and read_log. See MCP_README.md for client setup.

curl -s -X POST https://landed.wirt.ee/v1/verify \
  -H 'Content-Type: application/json' \
  -d '{"agent":"your-name","action":"posted fix comment",
       "url":"https://example.com/your-post",
       "expect":"the exact substring you wrote"}'

returns

{"ok": true, "found": true, "checked_at": "...",
 "receipt_id": "...", "digest": "sha256 of the fetched bytes",
 "sig": "hmac-sha256 (operator-verifiable)",
 "sig_ed25519": "ed25519 — verify it yourself with GET /v1/pubkey"}
  • GET /v1/pubkey — the Ed25519 public key: anyone can verify a receipt's sig_ed25519 themselves; the canonical form is documented with the key. (sig is HMAC and proves the operator signed — nothing more, nothing less.)
  • digest commits to the bytes the service observed at checked_at, so a reader can tell "landed at t0" apart from "still visible at t1".
  • GET /v1/receipt/<id> — the stored receipt plus a fresh re-verification right now (independent re-fetch), persisted as a timestamped RECHECKED event: later checks append, they never rewrite the first observation
  • GET /v1/log/<agent-name> — last 100 receipts for that name, each re-checkable against the live web

Why trust it

You don't have to. Every claim in a receipt is about a public object — anyone can fetch the URL themselves and compare. The service only supplies what a notary supplies: an independent look and a timestamp. Verifiability replaces trust; a fabricated receipt is exposed by the first person who re-checks it.

Limits: 60 verifications per agent name per hour. Targets are fetched politely (honest User-Agent, robots.txt respected, 10s timeout, 256KB cap, ≤3 redirects). Private/localhost addresses are refused. Requester IPs are never stored.

This very README

The service's first public announcement (an agent message board, 2026-10-12) carries a receipt issued by the service itself — the ad proves the product:

https://landed.wirt.ee/v1/receipt/c0c9b52345f0a78c

Self-hosting

One file of Python stdlib, one SQLite database, no dependencies. See DEPLOY.md (systemd recipe, hardening notes, Cloudflare-tunnel steps). Tests: python3 test_receipts.py (32 checks, fully offline, includes deliberately hostile SSRF attempts that must be refused).

Status & disclaimer

Operated by wirt.ee — named, not anonymous. This is an early experiment in mapping demand for agent infrastructure; the public API may change or vanish. Free tier only for now; nothing is sold.

MIT license — see LICENSE.

Frequently asked questions

What is ee.wirt/landed?

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

How do I install ee.wirt/landed?

It runs as a remote server. In Claude Code: claude mcp add --transport http landed 'https://landed.wirt.ee/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does ee.wirt/landed need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is ee.wirt/landed open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains ee.wirt/landed?

It is published by wirt-ee. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.