Latido — wedding vendors & planning (Hungary)
REMOTE · LATIDO.WEDDING · SCANNED AUG 20
Search Hungarian wedding vendors and venues, check a date, estimate a budget, get the checklist.
Available components
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. How we score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability39
- 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 90% of tool parameters carry a description.Partial
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
- Supports UI / widget rendering.Pass
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.
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · latido.wedding
claude mcp add --transport http wedding-latido-latido https://latido.wedding/mcp
[mcp_servers.wedding-latido-latido] url = "https://latido.wedding/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"wedding-latido-latido": {
"type": "remote",
"url": "https://latido.wedding/mcp",
"enabled": true
}
}
} openclaw mcp add wedding-latido-latido --url https://latido.wedding/mcp --transport streamable-http
mcp_servers:
wedding-latido-latido:
url: "https://latido.wedding/mcp" {
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Aug 26 62
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Aug 2026 · Probed https://latido.wedding/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=latido.wedding | CN=WE1,O=Google Trust Services,C=US | 26 Jun 2026 | 24 Sept 2026 | ECDSA 256 | ECDSA-SHA256 | 5bfce8328c42f8e70ec0866748c5c580 |
| SANs: latido.wedding | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
DNSSEC insecure
Validation of latido.wedding. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| wedding. | present | 52771 | 8 | Verified |
| latido.wedding. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://latido.wedding/mcp | Verified | 200 | |
| http (plaintext) | http://latido.wedding/mcp | HTTPS enforced | 301 | https://latido.wedding/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
check_availability Check a vendor's availability on a date ~108
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.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | YYYY-MM-DD |
| locale | string | – | Language for labels and copy. Use "hu" when the user writes Hungarian. |
| vendor_id | string | yes | – |
No output schema declared.
No examples provided.
estimate_budget Estimate a Hungarian wedding budget ~251
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
No output schema declared.
No examples provided.
fetch Fetch a Latido result (deep research) ~38
Full public storefront document for one result id from search. For a structured answer prefer get_vendor.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | A result id from search. |
No output schema declared.
No examples provided.
get_vendor Get a vendor's public profile ~129
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.
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string | – | Language for labels and copy. Use "hu" when the user writes Hungarian. |
| vendor_id | string | yes | The vendor id returned by search_vendors. |
No output schema declared.
No examples provided.
list_categories_and_regions List vendor categories, styles and regions ~113
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.
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string | – | Language for labels and copy. Use "hu" when the user writes Hungarian. |
No output schema declared.
No examples provided.
search Search Latido (deep research) ~62
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.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Free-text query — vendor name, category or place. |
No output schema declared.
No examples provided.
search_vendors Search wedding vendors & venues ~447
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
wedding_checklist Wedding planning checklist for Hungary ~223
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.