Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Landed

by wirt-eeversion 0.1.0i★ –iRuns in the cloud
Registry nameee.wirt/landed

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 2 passed Fail
  • Runs on the maker’s server: what you ask it goes through their server.
  • The registry lists no key to fill in.

You need

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

  1. Open Settings → Connectors
  2. Press Add custom connector
  3. Paste the address below and press Add
  4. If it asks you to sign in, sign in with the maker
SettingsConnectors1+ Add2https://…3
https://landed.wirt.ee/mcp

Run this in your terminal

claude mcp add --transport http landed https://landed.wirt.ee/mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

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

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "landed": {
      "type": "http",
      "url": "https://landed.wirt.ee/mcp"
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

  1. Open ChatGPT on the web → Settings → Connectors (Apps)
  2. Press Create or Add (some plans need Developer mode under Advanced first)
  3. Paste the address below, give it a name and save
  4. If it asks you to sign in, sign in with the maker
SettingsConnectors1+ Create2https://…3
https://landed.wirt.ee/mcp

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

The server did not answer when we last checked, so we could not read its tools.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified against the domain wirt.ee (the registry checks domain ownership)

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • ✕ Fail

    Endpoint responds

    Did not respond within 6 seconds when we checked

  • – Not applicable

    Sign-in with OAuth

    Did not respond within 6 seconds when we checked

  • … Not checked yet

    No hidden instructions in tool descriptions

    Not checked yet; we read the tool list when we check the endpoint

Compared with others in Otheri

  • More stars than 0% of the other 18431 servers in this category
  • Published to the registry more recently than 63% of the other 18431 servers in this category
  • Basic checks equal to or better than 22% of the other 18431 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Landed safe?

It passed 1 of 2 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.0) reached the registry 26 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Filesystem MCP

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago
Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated 3 days ago
Install

Filesystem MCP server for AI assistants.

Runs on your computerUpdated today
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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/ — 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/ — 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.

Ask PopNx