landed

Name: landed
Author: ee.wirt

MCP serverMCP

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

by ee.wirtrepository ↗homepage ↗v0.1.0

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"ee-wirt-landed","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability36/36 checks ok

when	check	result	http	latency	detail
2 h ago	mcp initialize	ok	200	142 ms	server landed 0.1.0 · protocol 2025-03-26 · 3 tools
8 h ago	mcp initialize	ok	200	118 ms	server landed 0.1.0 · protocol 2025-03-26 · 3 tools
15 h ago	mcp initialize	ok	200	220 ms	server landed 0.1.0 · protocol 2025-03-26 · 3 tools
22 h ago	mcp initialize	ok	200	184 ms	server landed 0.1.0 · protocol 2025-03-26 · 3 tools
29 h ago	mcp initialize	ok	200	138 ms	server landed 0.1.0 · protocol 2025-03-26 · 3 tools
2 d ago	mcp initialize	ok	200	191 ms	server landed 0.1.0 · protocol 2025-03-26 · 3 tools
2 d ago	mcp initialize	ok	200	186 ms	server landed 0.1.0 · protocol 2025-03-26 · 3 tools
2 d ago	mcp initialize	ok	200	187 ms	server landed 0.1.0 · protocol 2025-03-26 · 3 tools
2 d ago	mcp initialize	ok	200	119 ms	server landed 0.1.0 · protocol 2025-03-26 · 3 tools
3 d ago	mcp initialize	ok	200	167 ms	server landed 0.1.0 · protocol 2025-03-26 · 3 tools

Tools observed via MCP handshake

verify_write — 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 li
get_receipt — 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 stil
read_log — 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 v

Declared by sources

What the publisher says

Attributed to the source that supplied each field. Treated as claims, not facts.

No long description beyond the summary.

kind Official MCP Registry

name Official MCP Registry

repoUrl Official MCP Registry

summary Official MCP Registry

version Official MCP Registry

description Official MCP Registry

homepageUrl Official MCP Registry

publisherName Official MCP Registry

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

Official MCP Registryee.wirt/landed

first seen 10 d ago · fetched 3 d agoopen ↗

Field history (7 recent events)

10 d ago · declared · summary → "Read-after-write receipts for agents: did your write actually land? Free, signed, re-checkable."
10 d ago · declared · description → "Read-after-write receipts for agents: did your write actually land? Free, signed, re-checkable."
10 d ago · declared · publisherName → "ee.wirt"
10 d ago · declared · homepageUrl → "https://landed.wirt.ee"
10 d ago · declared · repoUrl → "https://github.com/wirt-ee/landed"
10 d ago · declared · version → "0.1.0"
10 d ago · declared · protocols → ["mcp"]

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from