Zafaf (Wedding)

Zafaf (Wedding) — connector documentation

• MCP endpoint: https://zafaf.connectorbay.com/mcp
• REST API: POST https://zafaf.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://zafaf.connectorbay.com/openapi.json
• Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
• Authentication: none required. An optional Authorization: Bearer <key> raises rate limits.
• Health: https://zafaf.connectorbay.com/health · Tool schemas: https://zafaf.connectorbay.com/tools.json
• Publisher: Unify Dynamics LLC · connectorbay.com/zafaf · agent@connectorbay.com

What Zafaf (Wedding) is for

"Zafaf" is the general Arabic word for a wedding. This connector is a fully local Arab wedding traditions and planning reference — what a given custom means and when it typically happens, how celebrations differ across Levantine, Gulf/Khaleeji, Egyptian and Maghrebi tradition, and the practical planning tools (a full end-to-end event timeline, a planning-timeline checklist, an attire guide, and gift/mahr guidance) that come up in almost every conversation about planning or understanding an Arab wedding — gathered in one place instead of a scroll through wedding blogs of uneven quality and accuracy.

What it does

A single ritual or custom's description, significance, and typical timing/sequence placement, across 16 items spanning the pre-wedding, contract, wedding-day and post-wedding stages — khitba, shabka, jaha, katb al-kitab, laylat al-henna, sahra, al-dazza, hammam al-arusa, neggafa, amariya, zaffat al-arees, zaffat al-aroosa, kosha, ardah, walima and sabahiye (ritual_info); a keyword search across names, descriptions, significance and associated regions (ritual_search); an overview and distinctive notes for four regional traditions — Levantine, Gulf/Khaleeji, Egyptian, and Maghrebi (traditions_by_region); the typical end-to-end sequence of events across an Arab wedding celebration, from the engagement through the wedding day to post-wedding customs (wedding_timeline); what's typically worn by role — bride, groom or guests — and how that varies by region (attire_guide); the zaffa procession tradition, its typical instruments, its style, and its connection to dabke and (in the Gulf) the ardah (music_and_zaffa_guide); the mahr explained factually and neutrally as a customary, contractual gift with no universal or expected amount, plus guest gift-giving customs (gift_and_dowry_customs); a full planning-timeline checklist covering venue, catering, invitations, attire and these traditions' specific touchpoints (planning_checklist); and a glossary of 15 core terms — mahr, katb al-kitab, zaffa, laylat al-henna, dabke, ardah, and more (wedding_glossary).

What it is not

Not a universal rulebook, and not religious or legal guidance. Arab wedding custom varies enormously by country, family, personal practice and religious observance, and this connector covers common, widely documented convention rather than any single family's or country's exact practice — always framed as "commonly," "by convention," or "in many families," never as the one correct way to do it. The marriage-contract custom (katb al-kitab) and the mahr are described strictly as customary and legal practice — never as a religious ruling, and the mahr is never given a specific amount, range, or currency figure, since it is fundamentally a matter of personal and family agreement, not a fixed price. The planning checklist is a rough starting-point aid for a conversation with your own family or officiant, not a substitute for their judgment.

Tools

Rituals

ritual_info — A single Arab wedding ritual or custom's description, significance, and typical timing/sequence placement. Use for "what is katb al-kitab", "what happens during the henna night", "when does the zaffa happen". Args: name.

ritual_search — Search Arab wedding rituals and customs by keyword across their name, description, significance and associated regions. Use for "which customs involve music", "find rituals about the bride's procession". Args: query.

Regional Traditions

traditions_by_region — A regional Arab wedding tradition's overview and distinctive notes (Levantine, Gulf/Khaleeji, Egyptian, or Maghrebi), plus which of this connector's rituals are associated with that region. Use for "what's different about a Gulf wedding", "tell me about Moroccan wedding traditions". Args: region.

Timeline & Planning

wedding_timeline — The typical end-to-end sequence of events across an Arab wedding celebration: engagement (khitba), the marriage contract (katb al-kitab), the henna night, wedding-day events (the zaffa, the walima), and post-wedding customs — in order, with typical timing for each. A typical shape, not a fixed schedule; the contract stage in particular can move earlier or later depending on family and country. Use for "what's the order of events at an Arab wedding", "walk me through a typical Arab wedding".

planning_checklist — A full wedding-planning timeline checklist, from about six months out through the wedding day, covering venue, catering, invitations, attire and the specific touchpoints of these traditions — laylat al-henna, the zaffa band, and the katb al-kitab paperwork and officiant. Use for "give me an Arab wedding planning checklist", "what should I be doing a month before my wedding".

Reference

attire_guide — What's typically worn at an Arab wedding by role — bride, groom or guests — and how that varies across Levantine, Gulf/Khaleeji, Egyptian and Maghrebi tradition, phrased as common convention. Omit role for the full guide across all three. Use for "what should the groom wear to a Khaleeji wedding", "what does a Moroccan bride wear". Args: role.

music_and_zaffa_guide — The zaffa wedding-procession tradition: typical instruments, its call-and-response singing style (no lyrics reproduced), its connection to Levantine dabke, and regional variation (the Gulf's ardah, Egypt's band-led scale, Maghrebi neggafa-led processions). Use for "what instruments are used in a zaffa", "what's the connection between dabke and the zaffa".

gift_and_dowry_customs — The mahr explained factually and neutrally — a customary, contractual gift from the groom to the bride agreed as part of the marriage contract, in whatever form and scale the couple and families agree, with no universal or expected amount ever stated here — plus guest gift-giving customs (cash gifts, gold from close family, return favors). Optionally pass a region for a region-specific note. Use for "what is the mahr", "how much should the mahr be" (this connector explains what it is and how it's set, and deliberately does not answer with a figure), "what do guests typically give at an Arab wedding". Args: region.

wedding_glossary — Definitions of common Arab wedding terms (mahr, katb al-kitab, zaffa, laylat al-henna, dabke, ardah, neggafa, and more). Use for "what does mahr mean", "what's dabke". Args: term.

Conventions

• Read-only. Every tool reads public data or computes; nothing is written anywhere and nothing about the user is stored.
• Result envelope. ok: true with data, or ok: false with a structured error (bad_input, not_found, upstream_error). degraded lists optional sources that were unreachable.
• Rate limits. Free tier 60 tool calls/minute and 300/day per user (keyed on the user identifier supplied by the host agent, else client IP); Pro keys raise this. Over-limit calls return HTTP 429 with Retry-After. initialize and tools/list are never counted.

Support

agent@connectorbay.com · connectorbay.com/zafaf/support

Zafaf (Wedding) — Privacy Policy

Effective 24 September 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What Zafaf (Wedding) is. Zafaf (Wedding) is a connector (an MCP server and REST API) that AI assistants and personal agents call on your behalf for a fully local Arab wedding traditions and planning reference — ritual meanings, regional variation notes, a full event timeline, a planning checklist, an attire guide, gift and mahr guidance, and a glossary. You interact with your assistant; the assistant sends us only the arguments needed for that one lookup.

What we receive. The arguments of each tool call — a ritual name or search keyword, a region name, an attire role, or a glossary term — the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant, and a Pro API key if you have one), and standard server logs.

Everything is answered from bundled, hand-authored reference files and nothing is stored. No request is forwarded to any third party — there is no upstream call at all, live or otherwise — and no query is logged in request bodies, recorded, or used to train anything.

What we do not receive or store. We do not receive your conversation with the assistant or your name, and we do not build a profile from your queries: each request is answered independently and nothing carries over between requests. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting-provider access logs, which contain IP addresses and request paths but not request bodies, are retained for up to 30 days for security and abuse prevention.

Sub-processors. None — the entire dataset is bundled with the server and answered locally. Hosting: Vercel (United States regions).

Legal bases and your rights. Our processing is necessary to provide the service you request through your assistant. Because we store no personal data beyond short-lived logs, requests to access, correct or delete personal data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. We do not sell or share personal information and do not use your data to train models.

Not religious, legal or financial guidance. Zafaf (Wedding) is a descriptive cultural and planning reference. It does not issue religious rulings on marriage or the marriage contract, does not provide legal advice, and never suggests a specific mahr amount — these are matters for the couple's own religious authority, legal counsel and family agreement.

Changes. We will post changes here with a new effective date.

Zafaf (Wedding) — Terms of Service

Effective 24 September 2026. These terms govern use of the Zafaf (Wedding) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

1. The Service. Zafaf (Wedding) returns a fully local Arab wedding traditions and planning reference — ritual descriptions, significance and timing; regional variation notes; a full event timeline; a planning-timeline checklist; an attire guide; gift and mahr guidance; and a glossary. It is accessed through an AI assistant or directly over MCP or HTTP.
2. Cultural reference, not a universal rule. Arab wedding custom varies significantly by country, family, personal practice and religious observance. Content here reflects commonly documented convention, hand-authored by the publisher, and is offered as a general reference — not a claim that any single practice described is universal, mandatory, or the only correct way to observe a tradition.
3. Not religious, legal or financial advice. The marriage-contract custom (katb al-kitab) and the mahr are described strictly as customary and legal practice, never as a religious ruling, and no mahr amount is ever suggested as typical or expected. planning_checklist is a rough planning aid based on general assumptions. Nothing here is a substitute for professional religious, legal or financial advice, or for your own family's or officiant's judgment.
4. Acceptable use. Automated use within the published rate limits is welcome.
5. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time.
6. Data. Our Privacy Policy describes what we process. In short: your query is answered from bundled reference files, and nothing is stored.
7. Pro keys. Optional Pro API keys are issued at our discretion, are personal to the holder and may be revoked for abuse.
8. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any wedding-planning decision made using its guidance. Our total liability is limited to US $100.
9. Governing law. California law; venue in San Mateo County, California.
10. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/zafaf

Zafaf (Wedding) support

Email agent@connectorbay.com. We answer within two business days.

• MCP endpoint: https://zafaf.connectorbay.com/mcp
• REST API: https://zafaf.connectorbay.com/openapi.json
• Live status: https://zafaf.connectorbay.com/health

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. Zafaf (Wedding) never asks for them.