Vivah (Wedding)

Vivah (Wedding) — connector documentation

• MCP endpoint: https://vivah.connectorbay.com/mcp
• REST API: POST https://vivah.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://vivah.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://vivah.connectorbay.com/health · Tool schemas: https://vivah.connectorbay.com/tools.json
• Publisher: Unify Dynamics LLC · connectorbay.com/vivah · agent@connectorbay.com

What Vivah (Wedding) is for

"Vivah" is the Hindi/Sanskrit word for a wedding. This connector is a fully local Indian wedding rituals and planning reference — what a given ceremony means and when it typically happens, how customs shift from one regional tradition to the next, and the practical planning tools (a timeline checklist, a guest-count estimator, a budget-allocation guide, an attire guide and gift-etiquette norms) that come up in almost every conversation about planning or understanding an Indian wedding — gathered in one place instead of a scroll through a dozen wedding-blog listicles of uneven quality.

What it does

A single ritual's description, significance, and typical timing/sequence placement, across 20 ceremonies spanning the pre-wedding, wedding-day and post-wedding stages — haldi, mehendi, sangeet, ganesh puja, baraat, jaimala/varmala, kanyadaan, saat phere/mangal phera (the seven vows), sindoor daan, mangalsutra, vidaai, and more (ritual_info); a keyword search across ritual names, descriptions, significance and traditions (ritual_search); an overview and distinctive ritual notes for seven regional traditions — North Indian/Hindi-belt, Punjabi, Bengali, Gujarati, Marathi, Tamil/South Indian, and Kashmiri Pandit (rituals_by_region); a full planning-timeline checklist covering venue, catering, invitations, attire and rituals booking, from about six months out through the wedding day, filterable to one point in the timeline (wedding_checklist); a rough, capacity-based suggested invite count across a few no-show scenarios (guest_list_estimator); a rough percentage-based allocation of a total budget across venue, catering, attire, decor, photography, jewelry and miscellaneous (budget_breakdown_guide); what's typically worn at each ceremony — haldi's yellow, mehendi's green, a wedding day's red/bridal color, a reception's often- different outfit (attire_guide); traditional gifting norms like odd-denomination cash gifts (gift_etiquette_guide); and a glossary of about a dozen core terms — baraat, shagun, trousseau, mandap, pheras, vidaai, and more (wedding_glossary).

What it is not

Not a universal rulebook. Hindu wedding custom varies enormously by region, religion, caste, community and individual family, and this connector covers common, widely-documented convention rather than any single family's or community's exact practice — always framed as "commonly," "by convention," or "in many communities," never as the one correct way to do it. The planning tools (the checklist, the guest-list estimator, and the budget guide in particular) are rough starting-point aids for a conversation with your own family, priest or planner, not a substitute for their judgment, and the budget guide is not financial advice.

Tools

Rituals

ritual_info — A single wedding ritual's description, significance, and typical timing/sequence placement. Use for "what is the haldi ceremony", "what happens during kanyadaan", "when does vidaai happen". Args: name.

ritual_search — Search wedding rituals by keyword across their name, description, significance and associated traditions. Use for "which rituals involve fire", "find rituals about the bride leaving home". Args: query.

Regional Traditions

rituals_by_region — A regional wedding tradition's overview and distinctive ritual notes (North Indian/Hindi-belt, Punjabi, Bengali, Gujarati, Marathi, Tamil/South Indian, or Kashmiri Pandit), plus which of this connector's rituals are associated with that region. Use for "what's different about a Bengali wedding", "Punjabi wedding traditions". Args: region.

Planning

wedding_checklist — A wedding-planning timeline checklist covering venue, catering, invitations, attire and rituals booking, from about six months out through the wedding day. Pass months_before to get just the closest milestone, or omit it for the full timeline. Use for "what should I be doing 3 months before my wedding", "give me a full wedding planning checklist". Args: months_before.

guest_list_estimator — A rough, capacity-based suggested invite count across a few no-show scenarios. A planning aid only, not a guarantee of attendance. Use for "how many people should I invite for a 300-seat hall". Args: venue_capacity.

budget_breakdown_guide — A rough, percentage-based allocation of a total wedding budget across venue, catering, attire, decor, photography, jewelry and miscellaneous. A general starting-point guideline, not a fixed rule or financial advice. Use for "how should I split a 20 lakh wedding budget". Args: total_budget.

Reference

attire_guide — What's typically worn at a given wedding ceremony (colors and attire style), phrased as common convention — real choices vary by region, family and personal taste. Use for "what should I wear to a haldi ceremony", "what color is worn at an Indian wedding". Args: ceremony.

gift_etiquette_guide — Traditional Indian wedding gift-giving norms — odd-denomination cash gifts, jewelry customs, return gifts and more — phrased as common custom, not a universal rule. Use for "how much cash should I gift at an Indian wedding", "wedding gift etiquette".

wedding_glossary — Definitions of common Indian wedding terms (baraat, shagun, trousseau, mandap, pheras, vidaai, and more). Use for "what does baraat mean", "what's a mandap". 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/vivah/support

Vivah (Wedding) — Privacy Policy

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

What Vivah (Wedding) is. Vivah (Wedding) is a connector (an MCP server and REST API) that AI assistants and personal agents call on your behalf for a fully local Indian wedding rituals and planning reference — ritual meanings, regional variation notes, a planning checklist, a guest-list estimator, a budget guide, an attire guide, gift etiquette, and a glossary. You interact with your assistant; the assistant sends us only the arguments needed for that one lookup or calculation.

What we receive. The arguments of each tool call — a ritual name or search keyword, a region name, a planning-timeline point, a venue capacity or budget figure, a ceremony name, 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, guest count or budget figure 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 financial or event-planning advice. Budget and guest-count figures returned by this connector are rough planning aids computed from the numbers you supply; we do not receive or retain those numbers beyond the single request used to compute the answer.

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

Vivah (Wedding) — Terms of Service

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

1. The Service. Vivah (Wedding) returns a fully local Indian wedding rituals and planning reference — ritual descriptions, significance and timing; regional variation notes; a planning-timeline checklist; a guest-list estimator; a budget-allocation guide; an attire guide; gift-etiquette norms; and a glossary. It is accessed through an AI assistant or directly over MCP or HTTP.
2. Cultural reference, not a universal rule. Hindu wedding custom varies significantly by region, religion, caste, community and family. 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 financial, legal or event-planning advice. wedding_checklist, guest_list_estimator and budget_breakdown_guide are rough planning aids based on general assumptions and commonly cited percentage splits. They are not a guarantee of attendance, cost, or timeline, and are not a substitute for professional financial, legal or event-planning advice, or for your own family's, priest's or planner'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/vivah

Vivah (Wedding) support

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

• MCP endpoint: https://vivah.connectorbay.com/mcp
• REST API: https://vivah.connectorbay.com/openapi.json
• Live status: https://vivah.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. Vivah (Wedding) never asks for them.