Wedyesday — wedding planning
REMOTE · MCP.WEDYESDAY.COM
Plan a wedding in chat: search vendors, get regional costs, build a checklist and budget.
Available components
Last scanned (11 hours ago)
Scores higher than 94% of remote servers
Reachable. Last reached 7 Nov 2026.
Category Project Management
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2106 tokens (~175/item across 12 items; 12 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 7 Nov 26 0
- Stability: pass → 0.97 functional
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 0
- New tool “get_wedyesday_pricing” functional
- 21 Sept 26 0
- Stability: 0.97 → pass security
- 8 Sept 26 0
- “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” cosmetic
10 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 7 Nov 2026 · Probed https://mcp.wedyesday.com
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.wedyesday.com | CN=YR1,O=Let's Encrypt,C=US | 23 Oct 2026 | 21 Jan 2027 | RSA 2048 | SHA256-RSA | 5877b39b0bafecf766e565151c866541b3d |
| SANs: mcp.wedyesday.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.wedyesday.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| wedyesday.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.wedyesday.com | Verified | 200 | |
| http (plaintext) | http://mcp.wedyesday.com | HTTPS enforced | 308 | https://mcp.wedyesday.com/ |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
add_my_wedding_task Add a wedding task ~123
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.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optional grouping, e.g. "Venue" or "Attire". |
| description | string | – | Optional detail. |
| dueDate | string | – | Due date as YYYY-MM-DD. |
| title | string | yes | What needs doing. |
| weddingId | string | – | Only needed when the account has more than one wedding. |
No output schema declared.
No examples provided.
build_wedding_plan Build a wedding plan ~392
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
No output schema declared.
No examples provided.
complete_my_wedding_task Mark a wedding task done ~102
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.
| Name | Type | Req | Description |
|---|---|---|---|
| note | string | – | Optional note recorded against the completion. |
| taskId | string | yes | Task id from list_my_wedding_tasks. |
| weddingId | string | – | Only needed when the account has more than one wedding. |
No output schema declared.
No examples provided.
create_wedyesday_workspace_link Create a Wedyesday workspace link ~397
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
No output schema declared.
No examples provided.
get_my_guest_list Get my guest list summary ~85
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.
| Name | Type | Req | Description |
|---|---|---|---|
| weddingId | string | – | Only needed when the account has more than one wedding. |
No output schema declared.
No examples provided.
get_my_wedding_budget Get my wedding budget ~63
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.
| Name | Type | Req | Description |
|---|---|---|---|
| weddingId | string | – | Only needed when the account has more than one wedding. |
No output schema declared.
No examples provided.
get_my_wedding_dashboard Get my wedding dashboard ~84
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.
| Name | Type | Req | Description |
|---|---|---|---|
| weddingId | string | – | Only needed when the account has more than one wedding. |
No output schema declared.
No examples provided.
get_wedding_cost_guide Get wedding cost guide ~135
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
get_wedyesday_pricing Get Wedyesday pricing ~126
Get what Wedyesday itself costs in a country — wedding-website add-ons for couples and vendor plans for businesses — in the currency that market is charged in, with a link to that country's published price list. Use this to answer 'how much does Wedyesday cost' instead of converting currencies. Planning tools, publishing a wedding website and enquiring with vendors are free.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | ISO country code: AU, US, GB, NZ or IN. Pass the buyer's country — prices differ per market; defaults to AU when omitted. |
No output schema declared.
No examples provided.
list_my_wedding_tasks List my wedding tasks ~114
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
list_wedding_markets List Wedyesday markets and categories ~88
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.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Optional ISO country code (AU, US, GB, NZ, IN). Supply it to list that market's regions. |
No output schema declared.
No examples provided.
search_wedding_vendors Search wedding vendors ~311
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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". |
No output schema declared.
No examples provided.
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.
remote · mcp.wedyesday.com
claude mcp add --transport http com-wedyesday-mcp-wedyesday 'https://mcp.wedyesday.com/'
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 12 tools: list_wedding_markets, search_wedding_vendors, get_wedding_cost_guide, get_wedyesday_pricing, build_wedding_plan, and 7 more. Their descriptions and schemas cost roughly 2,020 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 7 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Wedyesday — wedding planning MCP server?
VerifyMCP ran 13 checks on Wedyesday — wedding planning, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.