# Latido — wedding vendors & planning (Hungary)

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

- name: wedding.latido/latido
- version: 0.4.0
- connection class: R0 (autonomous)
- trust: 80/100 flags: no-repository
- quality: 96/100 (strong)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/wedding.latido%2Flatido
- tools: https://api.protogrid.dev/v1/servers/wedding.latido%2Flatido/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

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


## Trust

- hygiene: 80
- liveness: 100
- freshness: 85
- provenance: 55
- drivers: +dns-namespace +website +reachable +uptime-100% ~updated-62d-ago -no-repository
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 96/100 (strong)

### protocol: 88 (weight 25)

- pass `protocol.modern`: supports 2026-07-28 (server/discover)
- pass `protocol.stateless`: answers without a session
- pass `protocol.transport`: streamable HTTP
- warn `protocol.list_ttl`: tools/list declares ttlMs 0, so clients re-fetch it on every use

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 100 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 8 of 8 tools declare readOnlyHint or destructiveHint
- pass `tools.directory_hints`: every tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHint
- pass `tools.token_cost`: about 2,639 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: 100 (weight 15)

- pass `stability.changes`: no tool changes in 30 days
- pass `stability.rug_pull`: no tool changed its meaning under the same name

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 8, about 2,639 tokens to load them all
- tool set hash: 4c895ccc06e0f83710b670f1ea7c83fe
- badge: [![protogrid quality](https://protogrid.dev/badge/wedding.latido/latido.svg)](https://protogrid.dev/servers/wedding.latido/latido)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

_No tool definition changes recorded._

## Remotes

- https://latido.wedding/mcp (streamable-http, auth none, reachable true, uptime30d 1)

## Packages

_none_

## Tools (8)

- `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 "busy". Read-only.
- `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 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.
- `fetch`: Full public storefront document for one result id from search. For a structured answer prefer get_vendor.
- `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 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.
- `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 ("vőfély", "pajta", "Balaton") onto a `group`/`category`/`style` value — do not guess keys.
- `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.
- `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 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.
- `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 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.