Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Latido — wedding vendors & planning (Hungary)

REMOTE · LATIDO.WEDDING

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

Available components

0 this week 78 Trust /100

Last scanned (17 hours ago)

Scores higher than 71% of remote servers

Reachable. Last reached 21 Nov 2026.

Category E-commerce

Trust breakdown (7 categories)

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 → Why this is hard to 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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. 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
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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
  • Supports UI / widget rendering.Pass
What we tested

Checks we ran (14)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol
  • Capabilities

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 9 Nov 26 0
    • Stability: 0.97 → pass security
  • 8 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 19 Sept 26 0
    • Stability: 0.97 → pass security
Diagnostics

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 21 Nov 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 22 Oct 2026 20 Jan 2027 ECDSA 256 ECDSA-SHA256 3f366cde9d0d6c0f13207469e24aa218
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

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of latido.wedding. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
wedding. DS published 41906 13 Verified
latido.wedding. No DS 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

Background: How OAuth 2.1 works in the 2026 MCP spec →

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
MCP tools · 8 exposed · ~1,371 tokens

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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
check_availability ~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.

NameTypeReqDescription
datestringyesYYYY-MM-DD
localestring–Language for labels and copy. Use "hu" when the user writes Hungarian.
vendor_idstringyes–

No output schema declared.

No examples provided.

estimate_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.

NameTypeReqDescription
ceremonystring–civil | church (civil AND church) | abroad | undecided.
contingency_pctinteger––
datestring–Wedding date, if known — a weekday civil ceremony at the registry office is free.
guestsintegeryesNumber of guests (adults + children).
localestring–Language for labels and copy. Use "hu" when the user writes Hungarian.
regionstring–budapest | videk (countryside) | unknown.
tierstring–low = budget, mid = typical, high = premium.

No output schema declared.

No examples provided.

fetch ~38

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

NameTypeReqDescription
idstringyesA result id from search.

No output schema declared.

No examples provided.

get_vendor ~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.

NameTypeReqDescription
localestring–Language for labels and copy. Use "hu" when the user writes Hungarian.
vendor_idstringyesThe vendor id returned by search_vendors.

No output schema declared.

No examples provided.

list_categories_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.

NameTypeReqDescription
localestring–Language for labels and copy. Use "hu" when the user writes Hungarian.

No output schema declared.

No examples provided.

search ~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.

NameTypeReqDescription
querystringyesFree-text query — vendor name, category or place.

No output schema declared.

No examples provided.

search_vendors ~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.

NameTypeReqDescription
areastring–Place name in Hungary — city, county or region ("Budapest", "Somogy", "Siófok"). Matches vendors based there OR travelling vendors who serve it.
available_onstring–Wedding date (YYYY-MM-DD). Drops vendors KNOWN to be booked that day; vendors who do not publish availability are kept.
categorystring–A specific subcategory, e.g. farm_barn, photographers, dj, vofely, cake. Narrower than `group`.
groupstring–Top-level category: venues, photo_video, music_entertainment, … Use this for "any venue" / "a photographer".
localestring–Language for labels and copy. Use "hu" when the user writes Hungarian.
max_price_hufinteger–Budget ceiling in HUF. Vendors with no published price are still returned.
min_capacityinteger–Minimum seated guests (venues). Venues with no stated capacity are still returned.
pageinteger–1-based page, 10 results per page.
querystring–Free-text match on the vendor name or tagline, e.g. "Makay" or "vintage". Leave empty to browse.
stylestring–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 ~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.

NameTypeReqDescription
ceremonystring–civil | church | abroad | undecided — gates the Hungarian paperwork items.
depthstring––
localestring–Language for labels and copy. Use "hu" when the user writes Hungarian.
phasestring–Only this phase.
planning_startedstring–When planning began (YYYY-MM-DD); defaults to today. Sets how much the 12-month template is compressed.
wedding_datestring–YYYY-MM-DD. Without it, items come in order but undated.

No output schema declared.

No examples provided.

Install

How do I install the Latido — wedding vendors & planning (Hungary) MCP server?

Latido — wedding vendors & planning (Hungary) is a hosted endpoint at https://latido.wedding/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · latido.wedding

# add to Claude Code
claude mcp add --transport http wedding-latido-latido 'https://latido.wedding/mcp'
Common questions

What is the Latido — wedding vendors & planning (Hungary) MCP server?

Latido — wedding vendors & planning (Hungary) is an MCP server listed in the public MCP registry as wedding.latido/latido. Search Hungarian wedding vendors and venues, check a date, estimate a budget, get the checklist. This page covers its hosted endpoint (https://latido.wedding/mcp).

Is the Latido — wedding vendors & planning (Hungary) MCP server safe to use?

Latido — wedding vendors & planning (Hungary) scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Latido — wedding vendors & planning (Hungary) MCP server expose?

Latido — wedding vendors & planning (Hungary) exposes 8 tools: search_vendors, get_vendor, list_categories_and_regions, check_availability, estimate_budget, and 3 more. Their descriptions and schemas cost roughly 1,371 tokens of context every time the server is loaded.

Does the Latido — wedding vendors & planning (Hungary) MCP server require authentication?

No. We connected to Latido — wedding vendors & planning (Hungary) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Latido — wedding vendors & planning (Hungary) MCP server still maintained?

Latido — wedding vendors & planning (Hungary) is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Latido — wedding vendors & planning (Hungary) MCP server?

VerifyMCP ran 14 checks on Latido — wedding vendors & planning (Hungary), covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.