# Latido — wedding vendors & planning (Hungary) (remote · latido.wedding)

Search Hungarian wedding vendors and venues, check a date, estimate a budget, get the checklist.

- Trust score: 62/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-20

## Components

- remote · `latido.wedding`: 62/100 (this document), [markdown](https://verifymcp.io/servers/wedding-latido-latido/latido.md), [page](https://verifymcp.io/servers/wedding-latido-latido/latido)

## Channel facts

- Endpoint: `https://latido.wedding/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.4.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-20.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 39/100
  - 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1516 tokens (~168/item across 9 items; 8 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 97/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 90% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).
  - Supports UI / widget rendering.

**Unverified: 1 category.** A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### Claude

```bash
claude mcp add --transport http wedding-latido-latido https://latido.wedding/mcp
```

### Codex

```toml
[mcp_servers.wedding-latido-latido]
url = "https://latido.wedding/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "wedding-latido-latido": {
      "type": "remote",
      "url": "https://latido.wedding/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add wedding-latido-latido --url https://latido.wedding/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  wedding-latido-latido:
    url: "https://latido.wedding/mcp"
```

### Other

```json
{
  "mcpServers": {
    "wedding-latido-latido": {
      "type": "http",
      "url": "https://latido.wedding/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-20 (score 62)

First indexed and scored.

## MCP tools (8)

### `search_vendors` (~447 tokens)

Search wedding vendors & venues

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 top-level group, a place name (city, county or "Balaton"), maximum price in HUF, minimum seated capacity, a wedding style, or a date the vendor must be free on. Returns 10 results per page in the directory's own ranking; vendors who have not published a price/capacity/availability are kept (unknown is not a "no"). Each result has a public storefront URL — link to it. Does NOT search vendors who have not published a profile.

Input parameters:

- `area` (string): Place name in Hungary — city, county or region ("Budapest", "Somogy", "Siófok"). Matches vendors based there OR travelling vendors who serve it.
- `available_on` (string): Wedding date (YYYY-MM-DD). Drops vendors KNOWN to be booked that day; vendors who do not publish availability are kept.
- `category` (string): A specific subcategory, e.g. farm_barn, photographers, dj, vofely, cake. Narrower than `group`.
- `group` (string): Top-level category: venues, photo_video, music_entertainment, … Use this for "any venue" / "a photographer".
- `locale` (string): Language for labels and copy. Use "hu" when the user writes Hungarian.
- `max_price_huf` (integer): Budget ceiling in HUF. Vendors with no published price are still returned.
- `min_capacity` (integer): Minimum seated guests (venues). Venues with no stated capacity are still returned.
- `page` (integer): 1-based page, 10 results per page.
- `query` (string): Free-text match on the vendor name or tagline, e.g. "Makay" or "vintage". Leave empty to browse.
- `style` (string): Wedding style the vendor works in (boho, rustic, classic, modern, glamour, folk_hu…). One style per search.

### `get_vendor` (~129 tokens)

Get a vendor's public profile

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 to answer detailed questions or to compare shortlisted vendors. Read-only; never returns contact details beyond the public links — the storefront URL is where a couple gets in touch.

Input parameters:

- `locale` (string): Language for labels and copy. Use "hu" when the user writes Hungarian.
- `vendor_id` (string, required): The vendor id returned by search_vendors.

### `list_categories_and_regions` (~113 tokens)

List vendor categories, styles 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 ("vőfély", "pajta", "Balaton") onto a `group`/`category`/`style` value — do not guess keys.

Input parameters:

- `locale` (string): Language for labels and copy. Use "hu" when the user writes Hungarian.

### `check_availability` (~108 tokens)

Check a vendor's availability on a date

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 "busy". Read-only.

Input parameters:

- `date` (string, required): YYYY-MM-DD
- `locale` (string): Language for labels and copy. Use "hu" when the user writes Hungarian.
- `vendor_id` (string, required)

### `estimate_budget` (~251 tokens)

Estimate a Hungarian wedding 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 HUF, the per-line breakdown, the marginal cost of one more guest, and the expected cash-gift income (Hungarian custom: gifts are cash). Use for "mennyibe kerül egy esküvő" questions. Estimates, not quotes; prices are in HUF.

Input parameters:

- `ceremony` (string): civil | church (civil AND church) | abroad | undecided.
- `contingency_pct` (integer)
- `date` (string): Wedding date, if known — a weekday civil ceremony at the registry office is free.
- `guests` (integer, required): Number of guests (adults + children).
- `locale` (string): Language for labels and copy. Use "hu" when the user writes Hungarian.
- `region` (string): budapest | videk (countryside) | unknown.
- `tier` (string): low = budget, mid = typical, high = premium.

### `wedding_checklist` (~223 tokens)

Wedding planning checklist for Hungary

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 is shorter than 12 months. Filter by phase (start/book/shape/finish/week/after) and depth (essentials ≈27 · core ≈93 · everything ≈115). Use for "what should we be doing now" questions.

Input parameters:

- `ceremony` (string): civil | church | abroad | undecided — gates the Hungarian paperwork items.
- `depth` (string)
- `locale` (string): Language for labels and copy. Use "hu" when the user writes Hungarian.
- `phase` (string): Only this phase.
- `planning_started` (string): When planning began (YYYY-MM-DD); defaults to today. Sets how much the 12-month template is compressed.
- `wedding_date` (string): YYYY-MM-DD. Without it, items come in order but undated.

### `search` (~62 tokens)

Search Latido (deep research)

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.

Input parameters:

- `query` (string, required): Free-text query — vendor name, category or place.

### `fetch` (~38 tokens)

Fetch a Latido result (deep research)

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

Input parameters:

- `id` (string, required): A result id from search.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/wedding-latido-latido/latido#diagnostics

## Score history

- 2026-08-20: 62

## Links

- Remote endpoint: https://latido.wedding/mcp
- Website: https://latido.wedding/en/ai
- Changelog RSS feed: https://verifymcp.io/servers/wedding-latido-latido/latido.xml
- Changelog JSON feed: https://verifymcp.io/servers/wedding-latido-latido/latido.json
- HTML version of this page: https://verifymcp.io/servers/wedding-latido-latido/latido