Skip to content
Wirt OÜ logo

Wirt OÜ MCP server

Which MCP servers are Wirt OÜ's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-27

← Back to Wirt OÜ

Whose server it is
  • Registry nameee.wirt/landedverified in the MCP registry

The registry name sits under wirt.ee. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-27
  • Stateanswerschecked 2026-10-27
  • Tools3
  • Server calls itselflanded
  • Server version0.1.0
  • Protocol version2025-03-26

On 2026-10-27 the server answered initialize and tools/list without a sign-in. First answer in 561 ms.

Should an agent connect itSkip it
  • Its tools do none of the product's use cases we checked: upgrade OpenStack clusters across successive release versions; migrate Ceph storage clusters between major versions; configure high-availability VyOS firewalls on owned hardware.
  • Checked on 6 of the 7 days it takes to judge reliability.

Once connected

  • verify_write change data without a sign-in: anyone with the address can call them.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 6, the first on 2026-10-27
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 6 so far
  • What an agent can do with it0 of 3 use cases
  • Use1 GitHub stars
  • Answeredmeasuring6 of the 7 daily checks it takes to print a share
  • Median first answer581 ms
  • Space in an agent's context≈ 707 tokensthe definitions of all its tools (3), which an agent carries on every turn
  • Tool definitionsB · 83 of 100
  • Typed results0 of 3 toolsdeclared outputSchema: results come typed, read once
  • Not saying whether it only reads or can destroy: 3 of 3

What an agent can do with it

  • cannot · upgrade OpenStack clusters across successive release versions
  • cannot · migrate Ceph storage clusters between major versions
  • cannot · configure high-availability VyOS firewalls on owned hardware

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

  • Tools that change data, on a server that answers without a sign-in: verify_write

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers3 tools · read 2026-10-27
  • 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 lie: caches, moderation queues, auth walls, failed propagation and soft-failing…

  • 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 still propagating when you first verified (CDN caches, eventual consistency) and…

  • 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 verified. Returns up to 100 signed receipts with their statuses. The agent…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

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

Add it

Claude Code, in a terminal

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

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://landed.wirt.ee/mcp as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.