wedding.aisle/aisle

Est-ce que wedding.aisle/aisle est sûr ?

Au dernier audit MCP Hub, le serveur MCP « wedding.aisle/aisle » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 44 outils

• add_my_accommodation≈ 584 tokens

  Adds an unpriced room under a property in the selected wedding. The property is named by the id of a place already in the wedding or by a name, which uses the place with that name or starts a new one; a room name is required. An id that names no place in the wedding returns a not-found result. The new room has no payment requirement. Results return the saved room and its place's id and name, and say whether the call created that place. A new place is ordered by name among places that have not been reordered, so it is listed first once the properties have been reordered. Requires sign-in and an Aisle membership.

  Paramètres, retour & exemple (12)

  Paramètres

  • capacity · number · optionnel
    How many it sleeps
  • room_name · string · requis
    The room, e.g. "Garden Suite"
  • room_type · string · optionnel
    e.g. "Double", "Suite"
  • wedding_id · string · optionnel
    Identifier of a wedding the signed-in account can manage. Required when the account has multiple weddings.
  • description · string · optionnel
    Room description
  • property_id · string · optionnel
    Identifier of a place already in the selected wedding, as an alternative to property_name.
  • check_in_date · string · optionnel
    Check-in date (ISO format)
  • check_in_time · string · optionnel
    e.g. 3:00 PM
  • property_name · string · optionnel
    The property this room belongs to, e.g. "Castel Fragsburg". A name no place has starts a new place. Either this or property_id.
  • check_in_notes · string · optionnel
    Check-in notes
  • check_out_date · string · optionnel
    Check-out date (ISO format)
  • check_out_time · string · optionnel
    e.g. 11:00 AM

  Exemple d'appel

  {"name": "add_my_accommodation", "arguments": {"room_name": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• add_my_event≈ 443 tokens

  Creates an event in the selected wedding, with its name, type, date, time and optional venue, dress code and description. Requires sign-in and an Aisle membership.

  Paramètres, retour & exemple (10)

  Paramètres

  • date · string · requis
    Event start. A time with no offset, such as 2027-06-12T18:00, is the wedding's local time; one ending in Z or an offset is that exact instant.
  • name · string · requis
    Event name
  • type · string · optionnel · welcome_dinner | ceremony | reception | brunch | rehearsal | cocktail_hour | after_party | activity
    Event type
  • all_day · boolean · optionnel
    True for an all-day item with a day and no time, such as a travel day or a free day. Send date as the day (2027-06-12) and end_time as its last day for one that runs several days; a time sent with it is dropped.
  • end_time · string · optionnel
    Event end time, read the same way as date.
  • dress_code · string · optionnel
    Dress code (e.g. Black Tie, Smart Casual)
  • venue_name · string · optionnel
    Venue name for this event
  • wedding_id · string · optionnel
    Identifier of a wedding the signed-in account can manage. Required when the account has multiple weddings.
  • description · string · optionnel
    Event description
  • venue_address · string · optionnel
    Venue address

  Exemple d'appel

  {"name": "add_my_event", "arguments": {"date": "texte", "name": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• add_my_guest≈ 365 tokens

  Adds a guest to the selected wedding after explicit confirmation that the person is 13 or older, before collection of their name or contact details. First and last names are required; phone and email are optional. Results return the saved guest details. Age cannot be inferred from names or relationships. Guest notes and dietary details are unsupported. Requires sign-in and an Aisle membership.

  Paramètres, retour & exemple (6)

  Paramètres

  • email · string · optionnel
    Optional guest email address.
  • phone · string · optionnel
    Guest phone number, including + and its country code
  • age_band · string · requis
    Explicit confirmation that the guest is 13 or older, obtained before their name or contact details. Other age bands are ineligible.
  • last_name · string · requis
    Guest last name
  • first_name · string · requis
    Guest first name
  • wedding_id · string · optionnel
    Identifier of a wedding the signed-in account can manage. Required when the account has multiple weddings.

  Exemple d'appel

  {"name": "add_my_guest", "arguments": {"age_band": "texte", "last_name": "texte", "first_name": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• create_my_wedding≈ 416 tokens

  Creates the signed-in couple’s first wedding after explicit confirmation, using both partner names and an optional date, location and venue. Unknown date and location may be omitted. Existing weddings are returned without changes; accounts with multiple weddings are asked which to use. Creates a private preview with no membership purchase, site publication, partner invitations or marketing-email enrollment. Account sign-up happens in the secure browser connection, never through tool arguments.

  Paramètres, retour & exemple (6)

  Paramètres

  • location · string · optionnel
    Chosen wedding location. Omit when undecided.
  • confirmed · boolean · requis
    True only after the couple confirms creating their wedding with these details.
  • venue_name · string · optionnel
    Booked venue name. Omit if the couple has not booked a venue.
  • wedding_date · string · optionnel
    Wedding date as YYYY-MM-DD. Omit when undecided.
  • partner1_name · string · requis
    First partner’s chosen name.
  • partner2_name · string · requis
    Second partner’s chosen name.

  Exemple d'appel

  {"name": "create_my_wedding", "arguments": {"confirmed": true, "partner1_name": "texte", "partner2_name": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• generate_wedding_hashtags≈ 300 tokens

  Generates deduplicated wedding hashtag suggestions from partner names, surnames, year and place, ordered by a deterministic score. Suggestions are not registrations or availability checks.

  Paramètres, retour & exemple (6)

  Paramètres

  • year · integer · optionnel
    Wedding year for dated variants (e.g. 2027)
  • place · string · optionnel
    Wedding place for location variants (e.g. "Amalfi")
  • last_name_a · string · optionnel
    That partner’s last name, classics build on this surname
  • last_name_b · string · optionnel
    The other partner’s last name, adds puns, blends, and couple variants
  • first_name_a · string · optionnel
    One partner’s first name (e.g. "Maya")
  • first_name_b · string · optionnel
    The other partner’s first name

  Exemple d'appel

  {"name": "generate_wedding_hashtags", "arguments": {"year": 1, "place": "texte", "last_name_a": "texte", "last_name_b": "texte", "first_name_a": "texte", "first_name_b": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_alcohol_estimate≈ 369 tokens

  Estimates wedding bar quantities from guest count, event duration and drink mix, with bottles and cases rounded up. Quantities follow planning rules of thumb and are not a guarantee of consumption. This tool does not purchase alcohol.

  Paramètres, retour & exemple (6)

  Paramètres

  • mix · string · optionnel · wine-led | balanced | beer-led | spirit-forward
    Bar mix across wine, beer, and spirits (default: balanced)
  • crowd · string · optionnel · light | average | spirited
    How much the crowd drinks (default: average)
  • hours · integer · optionnel
    Hours of open bar (default: 5)
  • guest_count · integer · optionnel
    Total number of wedding guests
  • non_drinkers · integer · optionnel
    Guests in guest_count who will not drink alcohol (default: 0). The bar and the toast are sized for the rest.
  • champagne_toast · boolean · optionnel
    Whether the estimate includes one flute of champagne per guest for a toast. Default: true.

  Exemple d'appel

  {"name": "get_alcohol_estimate", "arguments": {"mix": "wine-led", "crowd": "light", "hours": 1, "guest_count": 1, "non_drinkers": 1, "champagne_toast": true}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_budget_estimate≈ 383 tokens

  Estimates a whole destination wedding budget in USD by guest count, place and style tier, from Aisle’s modelled wedding cost index. Accepts a destination or a country; a destination without a row of its own is priced at its country and the result says so. Results include a line-by-line breakdown, a typical total and the range most weddings land in. Places the index does not cover return coverage information. Figures are modelled estimates, not supplier quotes or prices from booked weddings.

  Paramètres, retour & exemple (4)

  Paramètres

  • style · string · optionnel · budget | mid-range | luxury
    Wedding style tier (default: mid-range)
  • country · string · optionnel
    Country name, used when no destination slug is given. Priced from that country as a whole.
  • destination · string · optionnel
    Place slug for a destination or a country in Aisle’s wedding cost index, such as amalfi-coast, tuscany, santorini, italy or mexico. A destination without a row of its own, such as tulum or bali, is priced at its country and the result says so.
  • guest_count · integer · optionnel
    Total number of wedding guests

  Exemple d'appel

  {"name": "get_budget_estimate", "arguments": {"style": "budget", "country": "texte", "destination": "texte", "guest_count": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_cash_gift_suggestion≈ 294 tokens

  Returns an illustrative low, typical and high cash wedding gift range in USD based on relationship, attending party, travel and wedding-party role. Results describe US etiquette conventions, not obligations. This tool does not transfer money.

  Paramètres, retour & exemple (4)

  Paramètres

  • party · string · optionnel · solo | couple | family
    Who attends: solo (default), couple, or family
  • travel · string · optionnel · local | domestic-travel | destination
    local (default), domestic-travel, or destination
  • relationship · string · optionnel
    Relationship to the couple: coworker, acquaintance, friend, close-friend, family or immediate-family. An absent value returns the available options.
  • in_wedding_party · boolean · optionnel
    Is the giver in the wedding party?

  Exemple d'appel

  {"name": "get_cash_gift_suggestion", "arguments": {"party": "solo", "travel": "local", "relationship": "texte", "in_wedding_party": true}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_day_of_timeline≈ 262 tokens

  Builds a draft wedding-day schedule around the ceremony time, first-look preference and reception duration. Times use standard planning offsets rather than confirmed vendor, venue or sunset schedules.

  Paramètres, retour & exemple (3)

  Paramètres

  • first_look · boolean · optionnel
    Whether the couple does a first look before the ceremony (default: true)
  • ceremony_time · string · optionnel
    Ceremony start time, 24-hour ("16:00") or "4pm" / "4:30 PM" style; a bare hour with no am/pm is read as PM
  • reception_hours · ? · optionnel
    Length of cocktail hour + reception in hours: 4, 5, or 6 (default: 5)

  Exemple d'appel

  {"name": "get_day_of_timeline", "arguments": {"first_look": true, "ceremony_time": "texte", "reception_hours": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_dress_code_guide≈ 170 tokens

  Returns a wedding dress code definition, clothing examples and invitation wording, or lists the available dress codes when none is specified. Results include the corresponding Aisle guide link.

  Paramètres, retour & exemple (1)

  Paramètres

  • dress_code · string · optionnel
    Optional dress code name, matched approximately. An absent value returns the available codes.

  Exemple d'appel

  {"name": "get_dress_code_guide", "arguments": {"dress_code": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_guest_travel_estimate≈ 576 tokens

  Estimates round-trip flights and lodging in USD for guest groups departing from supported US metros. Stay length and guests per room can be set, and default to the destination’s typical stay in a private room per guest. Each priced group gives a typical figure and a low-to-high range. Partial totals include only priced groups; unpriced guests and unsupported origins are reported separately. The urlRestoresEstimate field states whether the returned web link restores the supplied groups. Estimates are not live fares or bookings.

  Paramètres, retour & exemple (4)

  Paramètres

  • groups · array · optionnel
    Guest groups by departure city
  • nights · integer · optionnel
    Nights in the room, 1 to 30. Defaults to the destination's typical stay, shown as typicalStayNights on each group.
  • destination · string · optionnel
    Destination slug. Supported: algarve, amalfi-coast, argentina, aruba, aspen, bahamas, bali, barbados, barcelona, bermuda, cabo, cancun, cape-town, capri, charleston, cinque-terre, colombia, costa-rica, cotswolds, dominican-republic, dubrovnik, fiji, hawaii, iceland, ireland, jamaica, japan, kenya, lake-como, maldives, mallorca, maui, montenegro, morocco, mykonos, napa-valley, new-zealand, paris, peru, provence, puerto-rico, punta-cana, ravello, santorini, savannah, scottish-highlands, sorrento, sri-lanka, st-lucia, swiss-alps, thailand, dolomites, tulum, turks-and-caicos, tuscany, us-virgin-islands, vietnam.
  • guests_per_room · integer · optionnel
    Guests sharing each room, 1 to 4. Defaults to 1, a private room per guest; 2 prices couples sharing.

  Exemple d'appel

  {"name": "get_guest_travel_estimate", "arguments": {"groups": [], "nights": 1, "destination": "texte", "guests_per_room": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_invitation_wording≈ 556 tokens

  Composes wedding invitation text for a hosting situation and formality, using supplied names, event details and optional reception wording. With no scenario, it lists available options. Wording follows etiquette conventions rather than legal requirements.

  Paramètres, retour & exemple (13)

  Paramètres

  • date · string · optionnel
    Date as it should read, e.g. "Saturday, the twelfth of June"
  • time · string · optionnel
    Time as it should read, e.g. "at four o’clock in the afternoon"
  • scenario · string · optionnel
    Hosting-situation key. An absent value returns the available scenarios and formality options.
  • formality · string · optionnel
    Register key: formal, modern, casual, or playful
  • host_names · string · optionnel
    Host names for scenarios that include hosts. Two hosting parties are separated by " / ".
  • venue_name · string · optionnel
    Venue name
  • hosts_child · string · optionnel · couple_a | couple_b
    Partner whose parents are hosting. Defaults to couple_b for grooms-parents and couple_a for brides-parents or divorced-parents. Partner names never determine parentage.
  • couple_a_name · string · optionnel
    One partner’s full name
  • couple_b_name · string · optionnel
    The other partner’s full name
  • worship_space · boolean · optionnel
    Formal register: is the ceremony in a house of worship?
  • reception_note · string · optionnel
    Optional final line, e.g. "Reception to follow"
  • venue_location · string · optionnel
    Venue town and country
  • child_relationship · string · optionnel · child | daughter | son
    Relationship word for the hosts’ child. Defaults to child for divorced-parents, daughter for brides-parents and son for grooms-parents.

  Exemple d'appel

  {"name": "get_invitation_wording", "arguments": {"date": "texte", "time": "texte", "scenario": "texte", "formality": "texte", "host_names": "texte", "venue_name": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_my_accommodation≈ 306 tokens

  Returns one identified room in the selected wedding, with its property, description, capacity, status, stay details and stored price and deposit overrides, plus its place's id, name, stored room-choice override and effective mode. Missing, removed and other-wedding rooms return the same not-found result. Guest assignments and occupant identities are excluded. Requires sign-in.

  Paramètres, retour & exemple (2)

  Paramètres

  • wedding_id · string · optionnel
    Identifier of a wedding the signed-in account can manage. Required when the account has multiple weddings.
  • accommodation_id · string · requis
    Identifier of a room in the selected wedding.

  Exemple d'appel

  {"name": "get_my_accommodation", "arguments": {"accommodation_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_my_event≈ 280 tokens

  Returns one identified event in the selected wedding, with its name, type, date, time, venue, dress code and description, the ids of other events whose times overlap it, and the dress-code guide entry its dress code matches. Missing and other-wedding events return the same not-found result. Requires sign-in.

  Paramètres, retour & exemple (2)

  Paramètres

  • event_id · string · requis
    Identifier of an event in the selected wedding.
  • wedding_id · string · optionnel
    Identifier of a wedding the signed-in account can manage. Required when the account has multiple weddings.

  Exemple d'appel

  {"name": "get_my_event", "arguments": {"event_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_my_guest≈ 292 tokens

  Returns one identified guest recorded as 13 or older in the selected wedding, with saved names, contact preferences (a "defaulted" list names any nobody chose), language, RSVP status and timestamps. Missing, other-wedding, under-13 and unconfirmed-age records return the same not-found result. Guest notes and dietary details are excluded. Requires sign-in.

  Paramètres, retour & exemple (2)

  Paramètres

  • guest_id · string · requis
    Identifier of a guest in the selected wedding.
  • wedding_id · string · optionnel
    Identifier of a wedding the signed-in account can manage. Required when the account has multiple weddings.

  Exemple d'appel

  {"name": "get_my_guest", "arguments": {"guest_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_my_wedding≈ 198 tokens

  Returns the signed-in account's selected wedding details, including partner names, date, location and venue, the city and country picked in settings, and the destination to pass to the budget and guest travel estimates for the wedding's own place. Access is limited to weddings the account can manage.

  Paramètres, retour & exemple (1)

  Paramètres

  • wedding_id · string · optionnel
    Identifier of a wedding the signed-in account can manage. Required when the account has multiple weddings.

  Exemple d'appel

  {"name": "get_my_wedding", "arguments": {"wedding_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_my_wedding_stats≈ 214 tokens

  Returns aggregate wedding statistics, including guest totals across all age bands, RSVP counts, event counts and registry progress. Responded counts attending and declined guests; outstanding counts pending and maybe guests; the response rate is responded as a percentage of all guests. Guest identities and individual event answers are excluded. Requires sign-in.

  Paramètres, retour & exemple (1)

  Paramètres

  • wedding_id · string · optionnel
    Identifier of a wedding the signed-in account can manage. Required when the account has multiple weddings.

  Exemple d'appel

  {"name": "get_my_wedding_stats", "arguments": {"wedding_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_packing_list≈ 188 tokens

  Returns a destination wedding packing list by climate and role, covering clothing, weather essentials, travel documents and practical supplies.

  Paramètres, retour & exemple (2)

  Paramètres

  • role · string · optionnel · bride | groom | guest
    Your role at the wedding (default: guest)
  • climate · string · optionnel · tropical | mediterranean | temperate | cold
    Destination climate type (default: tropical)

  Exemple d'appel

  {"name": "get_packing_list", "arguments": {"role": "bride", "climate": "tropical"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_planning_timeline≈ 164 tokens

  Returns a destination wedding planning timeline organized by months before the wedding, from venue planning through day-of logistics.

  Paramètres, retour & exemple (1)

  Paramètres

  • months_out · integer · optionnel
    Months until the wedding day (filters to show only relevant tasks)

  Exemple d'appel

  {"name": "get_planning_timeline", "arguments": {"months_out": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_vendor_details≈ 202 tokens

  Returns a published wedding vendor by its slug, including services, descriptions, FAQs, ratings, photos and website links. The result states whether the description, services and FAQs were generated by Aisle from public information or supplied by the vendor, gives a price band only when the vendor supplied one, whether the vendor chose its category, and where the rating comes from.

  Paramètres, retour & exemple (1)

  Paramètres

  • slug · string · optionnel
    Unique slug identifying a published Aisle vendor.

  Exemple d'appel

  {"name": "get_vendor_details", "arguments": {"slug": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_venue_details≈ 332 tokens

  Returns a published wedding venue by its slug, including photos, highlights, travel information, planning estimates and available sourced facts with provenance, with each price also given as numbers, its currency and what it is per. Cost estimates are the ones the venue page shows, so a response gives one price for the venue and names any older estimate it left out. An estimators block names the destination the budget and guest travel estimators accept for the venue, the country when its area has no budget row, and covered destinations in the same country when travel has no figures for its area. When a slug is not a published venue, the result says whether it was never listed or was taken down, and suggests published venues: by name for a slug that does not exist, or the listing of the same name and the closest venues for one taken down. Estimates are not supplier quotes or live availability.

  Paramètres, retour & exemple (1)

  Paramètres

  • slug · string · optionnel
    Unique slug identifying a published Aisle venue.

  Exemple d'appel

  {"name": "get_venue_details", "arguments": {"slug": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_wedding_checklist≈ 165 tokens

  Returns destination wedding planning milestones across eight phases, from eighteen months before the wedding through the day itself. An optional month limit narrows the milestones shown.

  Paramètres, retour & exemple (1)

  Paramètres

  • months_out · number · optionnel
    Months until the wedding, returns only phases due within this window

  Exemple d'appel

  {"name": "get_wedding_checklist", "arguments": {"months_out": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_who_pays_split≈ 224 tokens

  Calculates percentages and amounts for dividing a wedding budget among the couple and their families under a selected model, with each amount also given as a whole-dollar USD number. Traditional assignments describe etiquette conventions, not obligations. This tool does not transfer money.

  Paramètres, retour & exemple (2)

  Paramètres

  • model · string · optionnel · traditional | even-split | both-families | couple
    Contribution model to split by (default: traditional)
  • total_budget · number · optionnel
    Total wedding budget in USD

  Exemple d'appel

  {"name": "get_who_pays_split", "arguments": {"model": "traditional", "total_budget": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_my_accommodations≈ 228 tokens

  Lists the selected wedding's places, including empty places with ids, position, arrangement, active and archived room counts, whether each place can be removed, stored room-choice overrides and effective modes, plus room descriptions, capacity, status, stay details, stored price and deposit overrides in property order. Guest assignments and occupant identities are excluded. Requires sign-in.

  Paramètres, retour & exemple (1)

  Paramètres

  • wedding_id · string · optionnel
    Identifier of a wedding the signed-in account can manage. Required when the account has multiple weddings.

  Exemple d'appel

  {"name": "list_my_accommodations", "arguments": {"wedding_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_my_events≈ 394 tokens

  Lists the selected wedding's events in date order with their dates, times, venues, dress codes and descriptions. Optional filters narrow results by event type or by a range of calendar days in the wedding's time zone; the total counts the events returned. Each event names the other events whose times overlap it. Requires sign-in.

  Paramètres, retour & exemple (4)

  Paramètres

  • to · string · optionnel
    Last day to include, as YYYY-MM-DD in the wedding's time zone.
  • from · string · optionnel
    First day to include, as YYYY-MM-DD in the wedding's time zone.
  • type · ? · optionnel
    Filter by event type, one type or a list such as ["ceremony", "reception"].
  • wedding_id · string · optionnel
    Identifier of a wedding the signed-in account can manage. Required when the account has multiple weddings.

  Exemple d'appel

  {"name": "list_my_events", "arguments": {"to": "texte", "from": "texte", "type": "texte", "wedding_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_my_guests≈ 544 tokens

  Lists guests in the selected wedding who are recorded as 13 or older, with saved names, contact preferences (a "defaulted" list names any nobody chose), language, RSVP status and timestamps. Optional filters narrow results by RSVP status, language or name, and results can be ordered by name or by most recent update, RSVP reply or addition; per-status counts cover every listed guest before filtering. Guests under 13 or with unconfirmed ages are excluded, as are guest notes and dietary details. Requires sign-in.

  Paramètres, retour & exemple (5)

  Paramètres

  • sort · string · optionnel · name | recently_updated | recently_responded | recently_added
    Order of the guests. "name" (the default) is last name then first. "recently_updated", "recently_responded" and "recently_added" put the newest first, by updatedAt, rsvpRespondedAt and createdAt; guests with no time sort last, by name.
  • search · string · optionnel
    Search guests by name. A first name, a last name, or the whole name all match, and accents are ignored, so Ines finds Inês.
  • language · string · optionnel
    Filter by a language name or code, such as Spanish or es. Empty string selects guests with no recorded language. Supported languages: English (en), Spanish (es), French (fr), Italian (it), German (de), Portuguese (pt), Polish (pl).
  • wedding_id · string · optionnel
    Identifier of a wedding the signed-in account can manage. Required when the account has multiple weddings.
  • rsvp_status · ? · optionnel
    Filter by RSVP status, one status or a list such as ["pending", "maybe"] for everyone yet to confirm.

  Exemple d'appel

  {"name": "list_my_guests", "arguments": {"sort": "name", "search": "texte", "language": "texte", "wedding_id": "texte", "rsvp_status": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_my_registry≈ 180 tokens

  Lists the selected wedding's registry and honeymoon fund items, descriptions, goal amounts and received totals. Donor identities are excluded. This tool does not collect contributions or initiate payments. Requires sign-in.

  Paramètres, retour & exemple (1)

  Paramètres

  • wedding_id · string · optionnel
    Identifier of a wedding the signed-in account can manage. Required when the account has multiple weddings.

  Exemple d'appel

  {"name": "list_my_registry", "arguments": {"wedding_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_vendor_categories≈ 152 tokens

  Lists every wedding vendor category and its published listing count, optionally filtered by location. A category with no listings is included with a count of 0.

  Paramètres, retour & exemple (1)

  Paramètres

  • location · string · optionnel
    Location slug to filter vendor counts (e.g. "austin-tx")

  Exemple d'appel

  {"name": "list_vendor_categories", "arguments": {"location": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_venue_countries≈ 134 tokens

  Lists countries with published wedding venues on Aisle and the number of venues in each country, broken down by venue type and by searchable price band, with a count of venues that have no price band.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "list_venue_countries", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• place_my_guests_in_rooms≈ 1020 tokens

  Places many guests in the selected wedding's rooms in one call, from a rule (reply, group, named guests, optionally limited to a place or rooms) or from a list of rooms and guests. Rooms are filled to their bed counts with each household kept together; held-back and full rooms are skipped, and a rule places only guests not yet in a room. Only guests recorded as 13 or older are placed. Results list who was placed in each room with its occupancy, and every skipped guest with a reason. By default it only plans and places no one; guests are placed when dry_run is false. At most 200 guests are placed per call. Requires sign-in and an Aisle membership.

  Paramètres, retour & exemple (5)

  Paramètres

  • fill · object · optionnel
    A rule the server packs into open rooms. Only guests not yet in a room are considered. Exclusive with assignments.
  • dry_run · boolean · optionnel
    When true or omitted, reports the placements and skipped guests that would result and places no one. Set to false to place guests.
  • wedding_id · string · optionnel
    Identifier of a wedding the signed-in account can manage. Required when the account has multiple weddings.
  • assignments · array · optionnel
    Your own list of rooms and guests; can move guests already placed. Exclusive with fill.
  • set_rsvp_status · string · optionnel · pending | attending | declined | maybe
    Also record this reply for every guest who lands in a room.

  Exemple d'appel

  {"name": "place_my_guests_in_rooms", "arguments": {"fill": {}, "dry_run": true, "wedding_id": "texte", "assignments": [], "set_rsvp_status": "pending"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• remove_my_accommodation≈ 394 tokens

  Removes an identified room and its guest assignments from the selected wedding, subject to payment and checkout safeguards. Uncharged checkouts without a payment method require confirmed cancellation. Completed, refunded or processing payments and active checkouts with a card prevent removal. Payment history is retained. The place is retained unless remove_empty_place is set and the place has no other rooms or retained history; otherwise empty places require a separate explicit removal. Requires sign-in and an Aisle membership.

  Paramètres, retour & exemple (3)

  Paramètres

  • wedding_id · string · optionnel
    Identifier of a wedding the signed-in account can manage. Required when the account has multiple weddings.
  • accommodation_id · string · requis
    Identifier of the room to remove from the selected wedding.
  • remove_empty_place · boolean · optionnel
    When true, also removes the room’s place if it has no other rooms or retained room history. Defaults to false, which keeps the place.

  Exemple d'appel

  {"name": "remove_my_accommodation", "arguments": {"accommodation_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• remove_my_event≈ 241 tokens

  Removes an identified event from the selected wedding and returns the removed event's id and name. Requires sign-in and an Aisle membership.

  Paramètres, retour & exemple (2)

  Paramètres

  • event_id · string · requis
    Identifier of the event to remove from the selected wedding.
  • wedding_id · string · optionnel
    Identifier of a wedding the signed-in account can manage. Required when the account has multiple weddings.

  Exemple d'appel

  {"name": "remove_my_event", "arguments": {"event_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• remove_my_guest≈ 264 tokens

  Removes an identified guest already recorded as 13 or older from the selected wedding and returns the removed guest's id and name. Guests under 13 or with unconfirmed ages are ineligible. Requires sign-in and an Aisle membership.

  Paramètres, retour & exemple (2)

  Paramètres

  • guest_id · string · requis
    Identifier of the guest to remove from the selected wedding.
  • wedding_id · string · optionnel
    Identifier of a wedding the signed-in account can manage. Required when the account has multiple weddings.

  Exemple d'appel

  {"name": "remove_my_guest", "arguments": {"guest_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• remove_my_place≈ 508 tokens

  Removes one or several identified empty places from the selected wedding and its property order, and returns the order that remains. The places list supplies their ids. With several, each place is removed or kept on its own, and the result lists which were removed and which kept, with the reason. A dry run reports the same without removing anything. This removes any recommendation or booking link on a removed place. Any rooms, including archived history, prevent removal. No rooms or payments are deleted. Requires sign-in and an Aisle membership.

  Paramètres, retour & exemple (4)

  Paramètres

  • dry_run · boolean · optionnel
    When true, reports which of the named places would be removed and which kept, with reasons, and removes nothing. Defaults to false.
  • place_id · string · optionnel
    Identifier of the empty property to remove, from the selected wedding’s places list. Provide this or place_ids.
  • place_ids · array · optionnel
    Identifiers of several empty properties to remove, from the selected wedding’s places list. Only these are considered. Provide this or place_id.
  • wedding_id · string · optionnel
    Identifier of a wedding the signed-in account can manage. Required when the account has multiple weddings.

  Exemple d'appel

  {"name": "remove_my_place", "arguments": {"dry_run": true, "place_id": "texte", "place_ids": [], "wedding_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• reorder_my_places≈ 317 tokens

  Sets the order of all properties on the selected wedding's guest site and accommodation screen. The complete list is required, as property ids from the places list or as names; name matching ignores case and surrounding spaces. Results and refusals give the order as ids with names. Partial or invalid lists are refused with the current order. Requires sign-in and an Aisle membership.

  Paramètres, retour & exemple (3)

  Paramètres

  • place_ids · array · optionnel
    Complete list of property ids from the selected wedding’s places list, in the intended display order. Provide this or place_names.
  • wedding_id · string · optionnel
    Identifier of a wedding the signed-in account can manage. Required when the account has multiple weddings.
  • place_names · array · optionnel
    Complete list of property names in the selected wedding, in the intended display order. Provide this or place_ids.

  Exemple d'appel

  {"name": "reorder_my_places", "arguments": {"place_ids": [], "wedding_id": "texte", "place_names": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• search_guides≈ 239 tokens

  Searches Aisle wedding planning guides by keywords and returns up to 10 relevant excerpts with links to the full articles and the date each guide was last revised, at most 3 from any one guide unless a different per-guide limit is supplied.

  Paramètres, retour & exemple (2)

  Paramètres

  • query · string · optionnel
    Search query keywords (e.g. "legal requirements Italy", "budget tips", "what to wear")
  • max_per_guide · integer · optionnel
    How many sections one guide may hold among the 10 results (default 3). 1 gives one entry per guide; 10 ranks sections with no per-guide limit.

  Exemple d'appel

  {"name": "search_guides", "arguments": {"query": "texte", "max_per_guide": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• search_vendors≈ 756 tokens

  Searches published wedding vendors by category, location and price range. Results include business details and listing links, with totals and pagination; summary omits descriptions and images. Each result states whether its content was generated by Aisle from public information or is managed by the vendor, where its rating comes from, whether its category was chosen by the vendor or assigned by Aisle’s search, and the domain of its website. A price band is reported, and matched by the price filter, only when the vendor supplied it. Results can be filtered by minimum Google rating and review count, and ordered by name, rating or review count. When a location holds fewer than five matching vendors, the result lists nearby locations within 150km that hold more, with counts and distances. A location search also gives each vendor’s distance from the middle of that location’s listings, since the listed city is the place searched rather than the vendor’s own town. Vendors in the same category and location that share a website or phone number are named on each other’s results as possible duplicates. This search does not check live availability or make bookings.

  Paramètres, retour & exemple (9)

  Paramètres

  • sort · string · optionnel · name | rating | reviews
    Result order: name (default), rating (highest first, ties broken by review count) or reviews (most reviewed first).
  • limit · integer · optionnel
    Results per page, from 1 to 50 (default 50).
  • offset · integer · optionnel
    Number of results to skip; nextOffset from the previous page continues the result set.
  • summary · boolean · optionnel
    Return compact comparison fields without descriptions and images (default false).
  • category · string · optionnel
    Vendor category filter, fuzzy-matched. One of: photographer, videographer, florist, caterer, dj, band, planner, coordinator, hair_makeup, cake_bakery, officiant, rentals_decor, stationery, transportation.
  • location · string · optionnel
    Location slug filter (e.g. "austin-tx", "london-uk")
  • min_rating · number · optionnel
    Only vendors with at least this Google rating, out of 5. Unrated vendors are left out.
  • min_reviews · integer · optionnel
    Only vendors with at least this many Google reviews.
  • price_range · string · optionnel · $ | $$ | $$$ | $$$$
    Price range filter: $ (budget) to $$$$ (luxury). Matches only listings whose vendor gave a band; generated listings have none.

  Exemple d'appel

  {"name": "search_vendors", "arguments": {"sort": "name", "limit": 1, "offset": 1, "summary": true, "category": "texte", "location": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• search_venues≈ 658 tokens

  Searches published destination wedding venues by country, venue type, guest capacity and price range, optionally leaving out unverified imported listings. Results include descriptions, photos and listing links, with totals and pagination; summary omits descriptions and images. Unknown capacity and unverified imported price bands are null. This search does not check live availability or make bookings.

  Paramètres, retour & exemple (10)

  Paramètres

  • type · string · optionnel · villa | hotel | estate | beach | restaurant | garden | castle | resort
    Venue type filter
  • limit · integer · optionnel
    Results per page, from 1 to 50 (default 50).
  • offset · integer · optionnel
    Number of results to skip; nextOffset from the previous page continues the result set.
  • country · string · optionnel
    Country name (e.g. "Italy", "Mexico"). A two-letter ISO code ("GR") or the country's own name ("Italia", "España") also works; appliedFilters.country gives the English name matched.
  • summary · boolean · optionnel
    Return compact comparison fields without descriptions and images (default false).
  • price_range · string · optionnel · $ | $$ | $$$ | $$$$
    Price range filter: $ (budget) to $$$$ (luxury)
  • capacity_max · integer · optionnel
    Upper end of your guest range. Matches venues with a known capacityMin no larger than this; unknown capacity is excluded.
  • capacity_min · integer · optionnel
    Lower end of your guest range. Matches venues with a known capacityMax at least this large; unknown capacity is excluded.
  • include_unknown_capacity · boolean · optionnel
    With capacity_min or capacity_max, also keep venues whose capacity is unknown (null) instead of leaving them out. Most imported listings have no known capacity. Default false.
  • exclude_unverified_imports · boolean · optionnel
    Leave out unverified imported listings (descriptionStatus "unverified_import"), which carry no description and usually no capacity or price. Default false.

  Exemple d'appel

  {"name": "search_venues", "arguments": {"type": "villa", "limit": 1, "offset": 1, "country": "texte", "summary": true, "price_range": "$"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• set_my_property_room_selection≈ 402 tokens

  Sets room choice for one Hosted property in the selected wedding. The property is identified by id or an exact, unambiguous name; matching ignores case and surrounding spaces. A non-null mode selects couple assignment or guest choice. Null restores the legacy wedding fallback. Other properties retain their settings. Results return the property id, stored override and effective mode. Requires sign-in and an Aisle membership.

  Paramètres, retour & exemple (4)

  Paramètres

  • wedding_id · string · optionnel
    Identifier of a wedding the signed-in account can manage. Required when the account has multiple weddings.
  • property_id · string · optionnel
    Identifier of a property in the selected wedding.
  • property_name · string · optionnel
    Exact property name, ignoring case and surrounding spaces. Duplicate names require a property identifier.
  • room_selection_mode · ? · requis
    Property room choice: couple_assigned means the couple assigns rooms; guest_choice means guests choose available rooms. Null clears the override and follows the legacy wedding setting. A non-null choice requires a Hosted property.

  Exemple d'appel

  {"name": "set_my_property_room_selection", "arguments": {"room_selection_mode": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• set_my_site_address≈ 227 tokens

  Changes the selected wedding's guest-site address within aisle.wedding, retaining redirects from its previous address. Addresses use 2 to 63 lowercase letters, numbers or hyphens and must be available and unreserved. Requires sign-in and an Aisle membership.

  Paramètres, retour & exemple (2)

  Paramètres

  • address · string · requis
    The new address, without the aisle.wedding/ in front of it, for example maya-and-theo
  • wedding_id · string · optionnel
    Identifier of a wedding the signed-in account can manage. Required when the account has multiple weddings.

  Exemple d'appel

  {"name": "set_my_site_address", "arguments": {"address": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• update_my_accommodation≈ 961 tokens

  Updates supplied room details, pricing, payment requirements or deposit and balance schedules in the selected wedding. Omitted fields remain unchanged. Null clears the room type, description, stay dates, check-in and check-out times or check-in notes. Setting a price enables payment unless explicitly disabled; zero makes the room free. Results return the saved room details, identify saved changes with their previous values and describe whether payment is available. This tool does not initiate a charge. Requires sign-in and an Aisle membership.

  Paramètres, retour & exemple (19)

  Paramètres

  • status · string · optionnel · available | unavailable
    unavailable takes the room out of the block
  • capacity · number · optionnel
    How many it sleeps
  • room_name · string · optionnel
    The room name
  • room_type · ? · optionnel
    e.g. "Double", "Suite", or null to clear it
  • price_unit · string · optionnel · room | night | party | head | open
    What the amount buys
  • wedding_id · string · optionnel
    Identifier of a wedding the signed-in account can manage. Required when the account has multiple weddings.
  • description · ? · optionnel
    Room description, or null to clear it
  • deposit_unit · string · optionnel · percent | amount
    How the deposit is stated: "amount" for a flat sum, "percent" for a share of whatever the room comes to
  • price_amount · ? · optionnel
    The rate, or null to clear it, or 0 to make it free
  • check_in_date · ? · optionnel
    Check-in date (ISO format), or null to clear it
  • check_in_time · ? · optionnel
    e.g. 3:00 PM, or null to clear it
  • check_in_notes · ? · optionnel
    Check-in notes, or null to clear it
  • check_out_date · ? · optionnel
    Check-out date (ISO format), or null to clear it
  • check_out_time · ? · optionnel
    e.g. 11:00 AM, or null to clear it
  • deposit_amount · ? · optionnel
    What guests pay up front, with the rest due by balance_due_date. Null clears the schedule so the room is paid whole; 0 takes this room off a schedule its property sets.
  • accommodation_id · string · requis
    Identifier of the room to update in the selected wedding.
  • balance_due_date · ? · optionnel
    YYYY-MM-DD, the day payment is due. Beside a deposit it dates the rest; on a room with no deposit it dates the whole price. Without it the room still charges, but nothing chases it.
  • deposit_due_date · ? · optionnel
    YYYY-MM-DD, the day the deposit is due. Without it the guest site says the deposit is due now. A date after balance_due_date is dropped.
  • requires_payment · boolean · optionnel
    Whether guests pay for this room

  Exemple d'appel

  {"name": "update_my_accommodation", "arguments": {"accommodation_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• update_my_event≈ 638 tokens

  Updates supplied name, type, schedule, venue, dress code or description fields for an identified event in the selected wedding. Omitted fields and existing invitations and responses remain unchanged. Null clears the end time, venue, address, dress code or description. Results identify saved changes with their previous values. Requires sign-in and an Aisle membership.

  Paramètres, retour & exemple (11)

  Paramètres

  • date · string · optionnel
    Event start. A time with no offset, such as 2027-06-12T18:00, is the wedding's local time; one ending in Z or an offset is that exact instant.
  • name · string · optionnel
    Event name
  • type · string · optionnel · welcome_dinner | ceremony | reception | brunch | rehearsal | cocktail_hour | after_party | activity
    Event type
  • all_day · boolean · optionnel
    True for an all-day item with a day and no time, such as a travel day or a free day. Send date as the day (2027-06-12) and end_time as its last day for one that runs several days; a time sent with it is dropped.
  • end_time · ? · optionnel
    Event end time, read the same way as date., or null to clear it
  • event_id · string · requis
    Identifier of the event to update in the selected wedding.
  • dress_code · ? · optionnel
    Dress code (e.g. Black Tie, Smart Casual), or null to clear it
  • venue_name · ? · optionnel
    Venue name for this event, or null to clear it
  • wedding_id · string · optionnel
    Identifier of a wedding the signed-in account can manage. Required when the account has multiple weddings.
  • description · ? · optionnel
    Event description, or null to clear it
  • venue_address · ? · optionnel
    Venue address, or null to clear it

  Exemple d'appel

  {"name": "update_my_event", "arguments": {"event_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• update_my_guest≈ 675 tokens

  Updates supplied name, contact, RSVP, communication preferences or language for a guest already recorded as 13 or older in the selected wedding. The guest identifier is required. Results return the saved guest details, including cleared values. This tool cannot change age bands, guest notes or dietary details. Requires sign-in and an Aisle membership.

  Paramètres, retour & exemple (10)

  Paramètres

  • email · string · optionnel
    Updated email address. Empty string clears it.
  • phone · string · optionnel
    Updated phone number, including + and its country code. Empty string clears it.
  • guest_id · string · requis
    Identifier of a guest in the selected wedding.
  • language · string · optionnel
    Which language this guest reads. A language name ("Spanish") or a code ("es", "pt"); both store the same value. Decides the language their guest site opens in, and which version of a message they get. Empty string clears it, which is not the same as 'en': a cleared guest follows the site's own language and their browser. Records a fact; translates nothing. Supported languages: English (en), Spanish (es), French (fr), Italian (it), German (de), Portuguese (pt), Polish (pl).
  • last_name · string · optionnel
    Updated last name
  • first_name · string · optionnel
    Updated first name
  • wedding_id · string · optionnel
    Identifier of a wedding the signed-in account can manage. Required when the account has multiple weddings.
  • rsvp_status · string · optionnel · pending | attending | declined | maybe
    RSVP status
  • broadcast_channel · string · optionnel · either | email | sms
    How this guest asked to be reached by messages sent to everyone: 'email' for email only, 'sms' for text only, 'either' for no preference.
  • preferred_transport · string · optionnel · sms | whatsapp
    Which wire a text to this guest takes. 'sms' reaches US and Canadian numbers only; 'whatsapp' reaches any number and is the answer for a guest abroad. The guest can also choose on the wedding site.

  Exemple d'appel

  {"name": "update_my_guest", "arguments": {"guest_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• update_my_wedding≈ 649 tokens

  Updates supplied wedding settings and can publish or unpublish the guest site. Omitted fields remain unchanged; nullable dates, location, venue and display name can be cleared. Partner names cannot be empty. Results identify saved changes with their previous values, every saved setting, the resulting couple display name and site address. Requires sign-in and an Aisle membership.

  Paramètres, retour & exemple (10)

  Paramètres

  • location · ? · optionnel
    Wedding location, or null to clear it
  • venue_name · ? · optionnel
    Venue name, or null to clear it
  • wedding_id · string · optionnel
    Identifier of a wedding the signed-in account can manage. Required when the account has multiple weddings.
  • is_published · boolean · optionnel
    Guest-site visibility. True publishes the site at its address; false returns it to a private draft and hides it from guests, including those with an existing link.
  • wedding_date · ? · optionnel
    Wedding date as a calendar day, YYYY-MM-DD, with no time and no zone, or null to clear it
  • partner1_name · string · optionnel
    First partner name. Cannot be emptied, only replaced
  • partner2_name · string · optionnel
    Second partner name. Cannot be emptied, only replaced
  • wedding_end_date · ? · optionnel
    Wedding end date as a calendar day, YYYY-MM-DD, with no time and no zone, or null to clear it
  • couple_display_name · ? · optionnel
    Custom display name for the couple. Null restores the combined partner names. A custom value remains unchanged when individual partner names change.
  • room_selection_mode · string · optionnel · couple_assigned | guest_choice
    Legacy bulk room choice: sets the wedding fallback and clears every property override, even when the supplied value matches the current wedding setting. Individual Hosted properties have their own room-choice setting. couple_assigned means the couple assigns rooms; guest_choice means guests choose available rooms and can pay once payouts are connected.

  Exemple d'appel

  {"name": "update_my_wedding", "arguments": {"location": "texte", "venue_name": "texte", "wedding_id": "texte", "is_published": true, "wedding_date": "texte", "partner1_name": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://aisle.wedding/api/claude/mcp