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.

Zola

REMOTE · MCP.ZOLA.COM

Find US wedding vendors, registry gifts and invitations, and Zola's wedding planning answers.

Available components

69 Trust /100

Last scanned (16 hours ago)

Scores higher than 53% 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 Security63
  • 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 enforcement could not be verified: the plaintext port answered with HTTP 403, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
  • 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 Usability80
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 3030 tokens (~189/item across 16 items; 15 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 Management13
  • Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 15 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 16 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 (13)

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

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 403, which proves neither a plaintext path nor enforcement.

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.

  • 20 Nov 26 0
    • Server version: 1.0.55 → 1.0.56 functional
  • 19 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 17 Nov 26 68

    First indexed and scored.

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://mcp.zola.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.zola.com CN=Amazon RSA 2048 M01,O=Amazon,C=US 2 Oct 2026 17 Apr 2027 RSA 2048 SHA256-RSA 53cdd9d5bd12ad70db02ef6889d3de3
SANs: *.zola.com
CN=Amazon RSA 2048 M01,O=Amazon,C=US (CA) CN=Amazon Root CA 1,O=Amazon,C=US 23 Aug 2022 23 Aug 2030 RSA 2048 SHA256-RSA 77312380b9d6688a33b1ed9bf9ccda68e0e0f
CN=Amazon Root CA 1,O=Amazon,C=US (CA) CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US 25 May 2015 31 Dec 2037 RSA 2048 SHA256-RSA 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.zola.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
zola.com. 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://mcp.zola.com/mcp Verified 200
http (plaintext) http://mcp.zola.com/mcp Inconclusive 403
MCP tools · 15 exposed · ~2,921 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
zola_estimate_wedding_alcohol ~327

Zola's general estimate of how much alcohol to buy for a wedding bar: the total drinks, the bottles of wine, the 750 ml bottles of liquor, the cases of beer, and the champagne for a toast. It counts 1.5 drinks per guest who drinks in the first hour and 1 drink each hour after, multiplied by 0.75 for a crowd that drinks below average and 1.5 for a crowd that drinks above average. The pours are the standard US pours: 5 oz of wine, 1.5 oz of liquor, 12 oz of beer. The default mix is 50% wine, 30% liquor, and 20% beer. For a beer-and-wine bar, give a mix with 0% liquor. It gives no cost.

NameTypeReqDescription
champagne_toastboolean–Add 1 glass of champagne per guest who drinks for the toast. Default false
crowdstring–How much the guests drink. Default average
guest_countintegeryesNumber of guests
hoursnumberyesHours of the bar, with the cocktail hour, in half hours, from 1 to 12
mix_percentobject–Share of the drinks for each type, in percent, that adds up to 100. Default 50% wine, 30% liquor, 20% beer
non_drinkersinteger–Guests in guest_count who will not drink alcohol, with the guests under 21. Default 0
NameTypeReqDescription
assumptionsobjectyesThe values that the estimate uses
beerobjectyesBeer
champagne_toastobject–Champagne for the toast, only with champagne_toast
crowdstringyesHow much the guests drink
drinking_guestsnumberyesGuests who drink: the bar and the toast are for them
guest_countnumberyesNumber of guests
hoursnumberyesHours of the bar
liquorobjectyesLiquor
non_drinkersnumberyesGuests who do not drink alcohol
sourcesarrayyesThe Zola article, and the Moët page for a toast
total_drinksnumberyesDrinks for the whole bar, rounded up. The toast is not in it
wineobjectyesWine

No examples provided.

zola_estimate_wedding_budget ~205

Use this when the user asks how much a wedding costs in general, or how to split a budget. Zola's general estimate of the total cost of a wedding in a US city, state, or wedding market, and the typical cost of each budget category (venue, catering, photographer, and more), from Zola data. Not for finding vendors. Do not use for the couple's own budget, costs or payments: use zola_get_my_budget.

NameTypeReqDescription
guest_countinteger–Number of guests. Omit when the user did not say.
locationstring–City and state (for example 'Chicago, IL'), a state ('Texas'), or a wedding market ('Long Island'). Omit for a United States estimate.
total_budgetinteger–The couple's own total budget, in whole US dollars, from 1,000 to 10,000,000. When given, the categories split this total.
NameTypeReqDescription
categoriesarray–Typical cost of each budget category
estimate_locationstring–The place that the estimate is for. It can be the state or the country when Zola has no data for the requested place.
guest_countnumber–Guest count of the estimate
guest_count_notestring–Why the guest count of the estimate is not the requested count
location_candidatesarray–The places that match the requested name, when there is more than one
requested_locationstring–The place name that was asked for
statusstringyesestimate: the estimate is in this result. ambiguous_location: more than one place matches. location_not_found: Zola does not know the place.
totalobject–Estimated total wedding cost
total_budget_centsnumber–The couple's own total budget, in cents. When present, the categories split this total.

No examples provided.

zola_find_couple ~156

Find the Zola wedding website and registry of one couple, for a guest who knows the couple. Give the first and last name of one partner, and the name of the other partner or the year and month of the wedding. Gives the links of one couple only, from the couples who let guests find them on zola.com. When no single couple matches, gives the zola.com couple search.

NameTypeReqDescription
first_partnerstringyesThe first and last name of one partner
second_partnerstring–The name of the other partner
wedding_monthstring–The year and month of the wedding, YYYY-MM, for example 2027-06. Necessary when second_partner is not given
NameTypeReqDescription
names_on_zolastring–With found_close_names only: the Zola spelling of the names that the user gave
registry_urlstring–The couple's Zola registry
search_urlstring–With not_found: the zola.com couple search for the names given
statusstringyesfound: one couple with the names given. found_close_names: one couple with names that are near the names given, which the user must make sure of. not_found: no single couple matches, so use search_url
website_urlstring–The couple's Zola wedding website
wedding_monthstring–The month of the wedding, for example 'June 2027'

No examples provided.

zola_get_planning_timeline_template ~188

Use this when the user asks what a couple usually does by when, for a wedding date. Zola's general planning timeline template, dated: the planning milestones for a wedding date and a wedding format (traditional, small, destination, elopement, or courthouse). Each milestone has a start date and a due date, counted back from the wedding date, and a status relative to today: late, now, later, or after the wedding. A milestone that applies only in some cases, for example a honeymoon, is marked optional. Do not use for the couple's own tasks or progress: use zola_get_my_checklist or zola_get_my_planning_overview.

NameTypeReqDescription
formatstring–Wedding format. The default is traditional.
wedding_datestringyesWedding date, YYYY-MM-DD. From today to 5 years after today.
NameTypeReqDescription
formatstringyesWedding format of the timeline
milestonesarrayyesThe milestones of the format, late and now first, then by due date
todaystringyesThe day that the statuses are relative to, YYYY-MM-DD (UTC)
wedding_datestringyesWedding date, YYYY-MM-DD

No examples provided.

zola_get_support_options ~82

Get the contact details for Zola customer support: email, phone number, support hours, and the Zola Help Center, plus the contacts for wedding vendors, product vendors, and the press. Use when the user asks how to contact Zola, or needs a person to solve a problem with an order, a payment, or a Zola account.

Input schema present but exposes no named parameters.

NameTypeReqDescription
emailstringyesZola customer support email address
help_center_urlstringyesZola Help Center with answers to common questions
hoursstringyesWhen customer support answers email and phone, in US Eastern Time (IANA time zone America/New_York)
other_contactsarrayyesContacts for vendors and the press. Couples and guests use email and phone
phonestringyesZola customer support phone number, in the US, with the country code

No examples provided.

zola_get_tipping_guide ~139

Zola's general tipping guide: how much couples tip wedding vendors (caterer, hair and makeup, photographer, videographer, DJ or band, planner, drivers, officiant, florist, delivery and setup teams), from Zola's tipping guide and Zola's 2026 Wedding Spend Survey. With a vendor type and its service cost, also gives the tip range in US dollars.

NameTypeReqDescription
service_costnumber–What the vendor costs, in US dollars. Only with vendor_type, for a vendor with a percent tip.
vendor_typestring–Vendor type. Omit for all vendor types.
NameTypeReqDescription
sourceobjectyesThe Zola article that gives these values
vendorsarrayyesThe tips for each vendor type

No examples provided.

zola_get_vendor_details ~78

Get detailed information about a specific wedding vendor on Zola including pricing, packages, FAQs, reviews, and more. Use the vendor slug from search results.

NameTypeReqDescription
slugstringyesThe vendor slug (e.g., 'brooklyn-winery', 'stanley-productions-inc'). This is the URL-friendly identifier for the vendor.
NameTypeReqDescription
badgesarray–Vendor badges and awards
descriptionstring–Full description of the vendor
faqsarray–Frequently asked questions
headlinestring–Short tagline or headline
locationobject–Location information
namestringyesVendor business name
packagesarray–Available packages
pricingobject–Pricing information
reviewsobject–Review summary
slugstringyesURL-friendly identifier
vendor_urlstring–URL to vendor's Zola page

No examples provided.

zola_get_wedding_day_timeline_template ~140

Use this when the user asks for an example schedule of a wedding day. Zola's general wedding day timeline template, from the guest arrival to the farewell, moved to the given ceremony time. The example day starts 1 hour before the ceremony and ends 5 hours after it, so the ceremony time must be from 07:00 to 19:00. Do not use for the times of the couple's own events: use zola_get_my_wedding_events.

NameTypeReqDescription
ceremony_timestringyesCeremony time, HH:MM, 24-hour, from 07:00 to 19:00
NameTypeReqDescription
ceremony_timestringyesCeremony time, HH:MM, 24-hour
eventsarrayyesThe events of the wedding day, in time order
sourceobjectyesThe Zola article that gives these values

No examples provided.

zola_get_who_pays_guide ~70

Zola's general guide to who traditionally pays for each wedding cost (the bride's parents, the groom's parents, the couple, the wedding party, or the guests), and how couples pay for their wedding today, from Zola's guide. It gives no percentages.

Input schema present but exposes no named parameters.

NameTypeReqDescription
factsarrayyesHow couples pay for their wedding today
itemsarrayyesWedding costs and who traditionally pays for each
sourceobjectyesThe Zola article that gives these values

No examples provided.

zola_search_help_articles ~169

Use this when the user asks how a Zola product or service works. Zola's general help articles from the Zola Help Center, about Zola's own products and services: the registry, gift orders and shipping, cash funds and fees, the wedding website, invitations and paper orders, the guest list, the vendor marketplace, and the Zola account. Not for general wedding advice. Do not use for the state of the couple's own orders, gifts, cash fund or store credit: use zola_get_my_order_history, zola_get_my_gift_tracker, zola_get_my_cash_fund_status or zola_get_my_credits.

NameTypeReqDescription
querystringyesThe question about Zola, for example 'How do guests ship a gift to my address?'
NameTypeReqDescription
help_center_urlstringyesThe Zola Help Center
resultsarrayyesThe best help articles, best first
statusstringyesno_results when the help center has no answer for the question

No examples provided.

zola_search_invitations ~173

Search the Zola paper shop for wedding invitations, save the dates, thank-you cards, and other wedding paper, by color, motif, and finish (foil, letterpress, custom photo). Each design links its page on zola.com.

NameTypeReqDescription
card_typestringyesThe kind of card
colorsarray–Colors, for example 'green' or 'dusty blue'. A search without a match gives the available colors
custom_photoboolean–Only designs with the couple's photo
foilboolean–Only designs with foil
letterpressboolean–Only letterpress designs
motifsarray–Motifs or styles, for example 'floral' or 'barn & country'. A search without a match gives the available motifs
NameTypeReqDescription
available_colorsarrayyesColor values for the colors filter
available_motifsarrayyesMotif values for the motifs filter
card_typestringyesThe card type of the search
designsarrayyesThe matching designs, in the zola.com shop order
statusstringyesno_results when no design matches the filters
totalnumberyesNumber of designs that match on zola.com

No examples provided.

zola_search_registry_products ~101

Search the products of the Zola registry shop, for registry ideas or a gift: kitchen, home, travel, experiences, and more, with the price and the product page. Not for finding a couple's own registry.

NameTypeReqDescription
max_priceinteger–The highest price in whole US dollars
querystringyesWhat to find, with the type, brand, color, or style, for example 'cast iron dutch oven'
NameTypeReqDescription
productsarrayyesThe matching products of the Zola registry shop
search_urlstring–The zola.com shop search, when the products of the search are all above max_price
statusstringyesno_results when no product of the Zola registry shop matches

No examples provided.

zola_search_vendors ~930

Browse and search wedding vendor listings on Zola by type, location, price, and style. Returns vendor profiles with photos, ratings, and pricing. Supports venues, photographers, videographers, florists, bands and DJs, hair and makeup, caterers, cakes and desserts, planners, bar services, officiants, and other services such as attire, dance floors, and floral preservation. Only call this tool if the user is looking to find or compare specific vendors, not for general wedding planning advice.

NameTypeReqDescription
citystring–City name to search in (optional)
filtersobject–Map of filter keys to arrays of filter values. Available filters vary by vendor_type. Can be null or omitted if no filters are needed. venue filters: - "venue-service-level": ["venue-service-level-a…
limitnumber–Number of results to return. Always use 8 unless user explicitly specifies a different number (max: 20)
max_price_centsnumber–Maximum price in cents (optional)
max_venue_capacitynumber–Maximum venue guest capacity (only for venue)
min_price_centsnumber–Minimum price in cents (optional)
min_venue_capacitynumber–Minimum venue guest capacity (only for venue)
offsetnumber–Results to skip for pagination (max: 200). Always use 0 unless user requests pagination
statestring–State code (e.g., 'NY', 'CA') to search in (optional)
target_datesarray–Target wedding dates in ISO 8601 format
vendor_typestringyesType of wedding vendor to search for
NameTypeReqDescription
location_candidatesarray–The places that match the city, with ambiguous_location
search_paramsobjectyesSearch parameters used
statusstring–Why there are no vendors: Zola has no location for the city, or more than one place has the name
totalnumberyesTotal number of vendors returned
vendorsarrayyesSummary of matching vendors

No examples provided.

zola_search_wedding_advice ~87

Search the Zola expert advice articles for wedding planning and etiquette: dress codes, invitation wording, traditions, ceremony and reception ideas, and how-to guides. Each result links its Zola article. Not for questions about Zola's own products and orders.

NameTypeReqDescription
querystringyesThe wedding planning topic or question, for example 'what does black tie optional mean'
NameTypeReqDescription
resultsarrayyesThe best Zola expert advice articles, best first
statusstringyesno_results when no Zola article matches

No examples provided.

zola_suggest_cash_gift_amount ~76

Zola's general guideline for how much a guest spends on a wedding gift, in cash or from the registry, for the guest's relationship to the couple, and the average wedding gift from Zola's 2026 First Look Report.

NameTypeReqDescription
relationshipstringyesThe guest's relationship to the couple
NameTypeReqDescription
average_gift_usdnumberyesAverage wedding gift in Zola's 2026 First Look Report, in US dollars
high_usdnumberyesHigh end of Zola's guideline, in US dollars
low_usdnumberyesLow end of Zola's guideline, in US dollars
most_guestsobjectyesWhat most guests spend, from Zola's 2026 First Look Report
open_ended_highbooleanyesTrue when the guideline is high_usd or more
relationshipstringyesThe guest's relationship to the couple
sourceobjectyesThe Zola article that gives these values

No examples provided.

Install

How do I install the Zola MCP server?

Zola is a hosted endpoint at https://mcp.zola.com/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 · mcp.zola.com

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

What is the Zola MCP server?

Zola is an MCP server listed in the public MCP registry as com.zola/zola. Find US wedding vendors, registry gifts and invitations, and Zola's wedding planning answers. This page covers its hosted endpoint (https://mcp.zola.com/mcp).

Is the Zola MCP server safe to use?

Zola scores 69 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 Zola MCP server expose?

Zola exposes 15 tools: zola_search_vendors, zola_get_vendor_details, zola_estimate_wedding_budget, zola_get_planning_timeline_template, zola_get_tipping_guide, and 10 more. Their descriptions and schemas cost roughly 2,921 tokens of context every time the server is loaded.

Does the Zola MCP server require authentication?

No. We connected to Zola without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Zola MCP server still maintained?

Zola 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 Zola MCP server?

VerifyMCP ran 13 checks on Zola, covering TLS certificate, Authorization, HSTS header, DNSSEC and 9 more. One item could not be completed, a gap on our side rather than a finding about Zola: HTTPS. 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.