Latido MCP server

• Registry namewedding.latido/latidoverified in the MCP registry

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

• Stateanswerschecked 2026-10-26
• Tools8
• Server calls itselflatido
• Server version0.5.0
• Protocol version2025-06-18

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

• Whether its tools do the product's job has not been judged yet.
• Checked on 2 of the 7 days it takes to judge reliability.

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.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 2 so far
• Answeredmeasuring2 of the 7 daily checks it takes to print a share
• Median first answer552 ms
• Space in an agent's context≈ 2,556 tokensthe definitions of all its tools (8), which an agent carries on every turn
• Tool definitionsA · 94 of 100
• Typed results0 of 8 toolsdeclared outputSchema: results come typed, read once

• Parameters without a description: in 3 of 8

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 →

• search_vendors

  Search Latido's public directory of Hungarian wedding vendors and venues (photographers, venues, DJs, florists, caterers, planners…). Use it whenever someone is looking for a supplier for a wedding in Hungary. Filter by category or…

• get_vendor

  Full public storefront of one vendor or venue from Latido by id (from search_vendors): categories, where they work, price band, capacity, packages with prices, FAQ, links, published reviews and their own description. Use it after a search…

• list_categories_and_regions

  The vocabulary search_vendors understands: the 11 top-level groups with their subcategory keys and labels, the wedding-style keys, and the Hungarian counties with their region ids. Call it once when you need to map what a user said…

• check_availability

  Whether one vendor (by id from search_vendors) is free, tentatively held, or booked on a given date — ONLY for vendors who chose to publish their availability. Most have not; then the answer is "unknown", which means "ask them", never…

• estimate_budget

  A dated, sourced cost estimate for a wedding in Hungary (benchmark set hu-2026.1, as of 2026-08) from guest count, price tier, region and ceremony type — the same engine as latido.wedding/kalkulator. Returns a low/anchor/high total in…

• wedding_checklist

  Latido's planning checklist (Hungarian legal steps included: szándékbejelentés, documents, witnesses, name change), scheduled to a wedding date: every item with its phase, category and due date, compressed proportionally when the runway…

• search

  Free-text search over Latido's public Hungarian wedding vendor directory. Returns result ids for fetch. For filtered search (category, place, budget, capacity, date) prefer search_vendors.

• fetch

  Full public storefront document for one result id from search. For a structured answer prefer get_vendor.