# Wedyesday — wedding planning (remote · mcp.wedyesday.com)

Plan a wedding in chat: search vendors, get regional costs, build a checklist and budget.

- Trust score: 87/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- remote · `mcp.wedyesday.com`: 87/100 (this document), [markdown](https://verifymcp.io/servers/com-wedyesday-mcp-wedyesday/mcp.md), [page](https://verifymcp.io/servers/com-wedyesday-mcp-wedyesday/mcp)

## Channel facts

- Endpoint: `https://mcp.wedyesday.com`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-21.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 73/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1980 tokens (~180/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Wedyesday — wedding planning MCP server?

Wedyesday — wedding planning is a hosted endpoint at https://mcp.wedyesday.com/, 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.

### Claude

```bash
claude mcp add --transport http com-wedyesday-mcp-wedyesday 'https://mcp.wedyesday.com/'
```

### Cursor

```json
{
  "mcpServers": {
    "com-wedyesday-mcp-wedyesday": {
      "url": "https://mcp.wedyesday.com/"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-wedyesday-mcp-wedyesday": {
      "type": "http",
      "url": "https://mcp.wedyesday.com/"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-wedyesday-mcp-wedyesday]
url = "https://mcp.wedyesday.com/"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-wedyesday-mcp-wedyesday": {
      "type": "remote",
      "url": "https://mcp.wedyesday.com/",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-wedyesday-mcp-wedyesday --url 'https://mcp.wedyesday.com/' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-wedyesday-mcp-wedyesday:
    url: "https://mcp.wedyesday.com/"
```

### Netclaw

```json
{
  "McpServers": {
    "com-wedyesday-mcp-wedyesday": {
      "Transport": "http",
      "Url": "https://mcp.wedyesday.com/"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-wedyesday-mcp-wedyesday -t streamable-http -u 'https://mcp.wedyesday.com/'
```

### Other

```json
{
  "mcpServers": {
    "com-wedyesday-mcp-wedyesday": {
      "type": "http",
      "url": "https://mcp.wedyesday.com/"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-21 (score 87, 0)

- [security] Stability: 0.97 → pass

### 2026-09-20 (score 87, +1)

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

### 2026-09-18 (score 86, +1)

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

### 2026-09-16 (score 85, +1)

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

### 2026-09-14 (score 84, +1)

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

### 2026-09-11 (score 83, +1)

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

### 2026-09-09 (score 82, +1)

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

### 2026-09-08 (score 81, 0)

- [cosmetic] “build_wedding_plan” reworded the description of “country”
- [cosmetic] “build_wedding_plan” reworded the description of “location”
- [cosmetic] “build_wedding_plan” reworded the description of “region”
- [cosmetic] “create_wedyesday_workspace_link” reworded the description of “country”
- [cosmetic] “create_wedyesday_workspace_link” reworded the description of “location”
- [cosmetic] “create_wedyesday_workspace_link” reworded the description of “region”
- [cosmetic] “get_wedding_cost_guide” reworded the description of “country”
- [cosmetic] “get_wedding_cost_guide” reworded the description of “region”
- [cosmetic] “search_wedding_vendors” reworded the description of “city”
- [cosmetic] “search_wedding_vendors” reworded the description of “country”

## MCP tools (11)

### `list_wedding_markets` (~88 tokens)

List Wedyesday markets and categories

List the countries, regions and vendor categories Wedyesday supports, with the exact values to pass to the other Wedyesday tools. Call this first when you do not already know a valid country code, region slug or vendor category.

Input parameters:

- `country` (string): Optional ISO country code (AU, US, GB, NZ, IN). Supply it to list that market's regions.

### `search_wedding_vendors` (~311 tokens)

Search wedding vendors

Search Wedyesday's directory of wedding vendors — venues, photographers, caterers, florists, celebrants and more. Returns real published listings with ratings, price bands and a link to each profile. Use list_wedding_markets first if you are unsure which category or country code to pass.

Input parameters:

- `category` (string): Vendor category, e.g. "venue" or "photography". One of: venue, photography, videography, catering, flowers, planning, dj, band, ceremony_music, beauty_health, dress_attire, cake, transportation, even…
- `city` (string): City name, e.g. "Melbourne" or "London".
- `country` (string): ISO country code: AU, US, GB, NZ or IN. Pass the couple's country; defaults to AU, the first market with a live vendor directory.
- `limit` (integer): Maximum results, 1-25. Defaults to 8.
- `minRating` (number): Minimum average review rating, 1-5.
- `priceBands` (array): Filter by price band. Any of: budget, standard, premium, luxury, quote_required.
- `query` (string): Free-text search, e.g. "barn" or "documentary style".
- `region` (string): State or region, e.g. "VIC" or "California".

### `get_wedding_cost_guide` (~135 tokens)

Get wedding cost guide

Get typical wedding costs for a region — a low/typical/high total plus a category-by-category breakdown (venue, catering, photography and so on). Use this to answer 'how much does a wedding cost' questions with real regional figures rather than estimates.

Input parameters:

- `country` (string): ISO country code: AU, US, GB, NZ or IN. Pass the couple's country — figures are per market; defaults to AU when omitted.
- `region` (string): Region slug from list_wedding_markets, e.g. "melbourne" or "london". Omit for the national figure.

### `build_wedding_plan` (~392 tokens)

Build a wedding plan

Build a personalised wedding plan: a month-by-month checklist with real due dates, a budget split for the couple's region, and how their budget compares to typical local spend. This is the same planning engine as the Wedyesday website, so nothing here is invented. Nothing is saved and no account is needed — follow up with create_wedyesday_workspace_link when the couple wants to keep it.

Input parameters:

- `budget` (integer): Total budget in whole currency units (e.g. 45000). Omit if the couple does not have one yet — a regional typical figure is used instead.
- `country` (string): ISO country code: AU, US, GB, NZ or IN. Pass the couple's country — the legal steps and budget split depend on it; defaults to AU when omitted.
- `dateMode` (string): "fixed" when the date is set, "season" when only a season and year are known, "undecided" otherwise.
- `eventDate` (string): Wedding date as YYYY-MM-DD. Required when dateMode is "fixed".
- `guestCount` (integer, required): Expected number of guests, 2-2000.
- `location` (string): Where the wedding is, e.g. "Melbourne, VIC" or "London".
- `partnerOne` (string): First partner's first name.
- `partnerTwo` (string): Second partner's first name.
- `priorities` (array): Up to three things that matter most. Values: venue, photography, food, music, flowers, videography, attire, styling.
- `region` (string): Region slug from list_wedding_markets, e.g. "melbourne" or "london". Drives the budget split and legal steps.
- `season` (string): Required when dateMode is "season".
- `seasonYear` (integer): Year for the chosen season.

### `create_wedyesday_workspace_link` (~397 tokens)

Create a Wedyesday workspace link

Turn a wedding plan into a private link the couple can open to save it as a free Wedyesday workspace — checklist, budget, guest list, RSVPs and a wedding website. Pass the same answers used for build_wedding_plan. This creates no account and stores no personal details; the couple signs up themselves when they open the link. Give them the link and tell them it expires in 14 days.

Input parameters:

- `budget` (integer): Total budget in whole currency units (e.g. 45000). Omit if the couple does not have one yet — a regional typical figure is used instead.
- `country` (string): ISO country code: AU, US, GB, NZ or IN. Pass the couple's country — the legal steps and budget split depend on it; defaults to AU when omitted.
- `dateMode` (string): "fixed" when the date is set, "season" when only a season and year are known, "undecided" otherwise.
- `eventDate` (string): Wedding date as YYYY-MM-DD. Required when dateMode is "fixed".
- `guestCount` (integer, required): Expected number of guests, 2-2000.
- `location` (string): Where the wedding is, e.g. "Melbourne, VIC" or "London".
- `partnerOne` (string): First partner's first name.
- `partnerTwo` (string): Second partner's first name.
- `priorities` (array): Up to three things that matter most. Values: venue, photography, food, music, flowers, videography, attire, styling.
- `region` (string): Region slug from list_wedding_markets, e.g. "melbourne" or "london". Drives the budget split and legal steps.
- `season` (string): Required when dateMode is "season".
- `seasonYear` (integer): Year for the chosen season.

### `get_my_wedding_dashboard` (~84 tokens)

Get my wedding dashboard

Get an overview of the signed-in couple's Wedyesday wedding: date, countdown, checklist progress, budget position and what is due next, plus a direct link to their dashboard. Start here for any question about 'my wedding'. Requires a connected Wedyesday account.

Input parameters:

- `weddingId` (string): Only needed when the account has more than one wedding.

### `list_my_wedding_tasks` (~114 tokens)

List my wedding tasks

List tasks from the couple's Wedyesday checklist, newest deadlines first. Filter to what is overdue, due soon, or already done. Requires a connected Wedyesday account.

Input parameters:

- `filter` (string): "open" (default) for everything not done, "overdue", "done", or "all".
- `limit` (integer): Maximum tasks to return, 1-40. Defaults to 15.
- `weddingId` (string): Only needed when the account has more than one wedding.

### `add_my_wedding_task` (~123 tokens)

Add a wedding task

Add a task to the couple's Wedyesday checklist. Confirm the wording and the due date with the couple before calling this — it writes to their real workspace. Requires a connected Wedyesday account.

Input parameters:

- `category` (string): Optional grouping, e.g. "Venue" or "Attire".
- `description` (string): Optional detail.
- `dueDate` (string): Due date as YYYY-MM-DD.
- `title` (string, required): What needs doing.
- `weddingId` (string): Only needed when the account has more than one wedding.

### `complete_my_wedding_task` (~102 tokens)

Mark a wedding task done

Mark a task on the couple's Wedyesday checklist as done. Get the task id from list_my_wedding_tasks first, and confirm with the couple which task they mean. Requires a connected Wedyesday account.

Input parameters:

- `note` (string): Optional note recorded against the completion.
- `taskId` (string, required): Task id from list_my_wedding_tasks.
- `weddingId` (string): Only needed when the account has more than one wedding.

### `get_my_wedding_budget` (~63 tokens)

Get my wedding budget

Get the couple's Wedyesday budget: planned versus actual by category, what is left, and any payments due or overdue. Requires a connected Wedyesday account.

Input parameters:

- `weddingId` (string): Only needed when the account has more than one wedding.

### `get_my_guest_list` (~85 tokens)

Get my guest list summary

Get a summary of the couple's Wedyesday guest list: headcount, groups, how many have contact details on file, plus_ones and children. Guests' email addresses and phone numbers are never returned — those stay in the dashboard. Requires a connected Wedyesday account.

Input parameters:

- `weddingId` (string): Only needed when the account has more than one wedding.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-wedyesday-mcp-wedyesday/mcp#diagnostics

## Score history

- 2026-09-21: 87
- 2026-09-20: 87
- 2026-09-19: 86
- 2026-09-18: 86
- 2026-09-17: 85
- 2026-09-16: 85
- 2026-09-15: 84
- 2026-09-14: 84
- 2026-09-13: 83
- 2026-09-12: 83
- 2026-09-11: 83
- 2026-09-10: 82
- 2026-09-09: 82
- 2026-09-08: 81
- 2026-09-07: 81
- 2026-09-06: 80
- 2026-09-05: 80
- 2026-09-04: 79
- 2026-09-03: 79
- 2026-09-02: 78
- 2026-09-01: 78
- 2026-08-31: 77
- 2026-08-30: 77
- 2026-08-29: 76
- 2026-08-28: 76
- 2026-08-27: 76
- 2026-08-26: 75
- 2026-08-25: 73
- 2026-08-24: 73
- 2026-08-23: 72

## Common questions

### What is the Wedyesday — wedding planning MCP server?

Wedyesday — wedding planning is an MCP server listed in the public MCP registry as com.wedyesday.mcp/wedyesday. Plan a wedding in chat: search vendors, get regional costs, build a checklist and budget. This page covers its hosted endpoint (https://mcp.wedyesday.com).

### Is the Wedyesday — wedding planning MCP server safe to use?

Wedyesday — wedding planning scores 87 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 Wedyesday — wedding planning MCP server expose?

Wedyesday — wedding planning exposes 11 tools: list_wedding_markets, search_wedding_vendors, get_wedding_cost_guide, build_wedding_plan, create_wedyesday_workspace_link, and 6 more. Their descriptions and schemas cost roughly 1,894 tokens of context every time the server is loaded.

### Does the Wedyesday — wedding planning MCP server require authentication?

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

### Is the Wedyesday — wedding planning MCP server still maintained?

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

## Links

- Remote endpoint: https://mcp.wedyesday.com/
- Repository: https://github.com/vritul/wedyesday
- Website: https://www.wedyesday.com/ai
- Changelog RSS feed: https://verifymcp.io/servers/com-wedyesday-mcp-wedyesday/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-wedyesday-mcp-wedyesday/mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-wedyesday-mcp-wedyesday/mcp