Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
Wedyesday — wedding planning is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
tool-list score
12
tools declared
remote
at its publisher
—
calls last 7d
What it does
Plan a wedding in chat: search vendors, get regional costs, build a checklist and budget.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http wedyesday-wedding-planning-mcp https://mcp.wedyesday.com
# 2 — ask your agent for something these tools do
# list_wedding_markets, search_wedding_vendors, get_wedding_cost_guide and 9 more
Wedyesday — wedding planning costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
WEAll 1 server
wedyesday1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http wedyesday-wedding-planning-mcp https://mcp.wedyesday.comReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
12 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| country | string | no | Optional ISO country code (AU, US, GB, NZ, IN). Supply it to list that market's regions. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| category | string | no | 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, event |
| city | string | no | City name, e.g. "Melbourne" or "London". |
| country | string | no | 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 | no | Maximum results, 1-25. Defaults to 8. |
| minRating | number | no | Minimum average review rating, 1-5. |
| priceBands | array | no | Filter by price band. Any of: budget, standard, premium, luxury, quote_required. |
| query | string | no | Free-text search, e.g. "barn" or "documentary style". |
| region | string | no | State or region, e.g. "VIC" or "California". |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| country | string | no | 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 | no | Region slug from list_wedding_markets, e.g. "melbourne" or "london". Omit for the national figure. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| country | string | no | ISO country code: AU, US, GB, NZ or IN. Pass the buyer's country — prices differ per market; defaults to AU when omitted. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| budget | integer | no | 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 | no | 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. |
| eventDate | string | no | Wedding date as YYYY-MM-DD. Required when dateMode is "fixed". |
| dateMode | string | no | "fixed" when the date is set, "season" when only a season and year are known, "undecided" otherwise. |
| guestCount | integer | yes | Expected number of guests, 2-2000. |
| location | string | no | Where the wedding is, e.g. "Melbourne, VIC" or "London". |
| partnerOne | string | no | First partner's first name. |
| partnerTwo | string | no | Second partner's first name. |
| priorities | array | no | Up to three things that matter most. Values: venue, photography, food, music, flowers, videography, attire, styling. |
| region | string | no | Region slug from list_wedding_markets, e.g. "melbourne" or "london". Drives the budget split and legal steps. |
| season | string | no | Required when dateMode is "season". |
| seasonYear | integer | no | Year for the chosen season. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| budget | integer | no | 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 | no | 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. |
| eventDate | string | no | Wedding date as YYYY-MM-DD. Required when dateMode is "fixed". |
| dateMode | string | no | "fixed" when the date is set, "season" when only a season and year are known, "undecided" otherwise. |
| guestCount | integer | yes | Expected number of guests, 2-2000. |
| location | string | no | Where the wedding is, e.g. "Melbourne, VIC" or "London". |
| partnerOne | string | no | First partner's first name. |
| partnerTwo | string | no | Second partner's first name. |
| priorities | array | no | Up to three things that matter most. Values: venue, photography, food, music, flowers, videography, attire, styling. |
| region | string | no | Region slug from list_wedding_markets, e.g. "melbourne" or "london". Drives the budget split and legal steps. |
| season | string | no | Required when dateMode is "season". |
| seasonYear | integer | no | Year for the chosen season. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| weddingId | string | no | Only needed when the account has more than one wedding. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| filter | string | no | "open" (default) for everything not done, "overdue", "done", or "all". |
| limit | integer | no | Maximum tasks to return, 1-40. Defaults to 15. |
| weddingId | string | no | Only needed when the account has more than one wedding. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| category | string | no | Optional grouping, e.g. "Venue" or "Attire". |
| description | string | no | Optional detail. |
| dueDate | string | no | Due date as YYYY-MM-DD. |
| title | string | yes | What needs doing. |
| weddingId | string | no | Only needed when the account has more than one wedding. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| note | string | no | Optional note recorded against the completion. |
| taskId | string | yes | Task id from list_my_wedding_tasks. |
| weddingId | string | no | Only needed when the account has more than one wedding. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| weddingId | string | no | Only needed when the account has more than one wedding. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| weddingId | string | no | Only needed when the account has more than one wedding. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Wedyesday — wedding planning or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 93 / 100
Release 1.0.0 · scanned 20 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings0 threat · 0 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digestcb2b6ddbb91631443427422e261385371085df49ddc93f44929695d96fd96e7e
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| list_wedding_markets | no tags | |
| search_wedding_vendors | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_wedding_cost_guide | no tags | |
| get_wedyesday_pricing | no tags | |
| build_wedding_plan | no tags | |
| create_wedyesday_workspace_link | state-write | state-write: declares readOnlyHint: false |
| get_my_wedding_dashboard | no tags | |
| list_my_wedding_tasks | no tags | |
| add_my_wedding_task | state-write | state-write: declares readOnlyHint: false |
| complete_my_wedding_task | state-write | state-write: declares readOnlyHint: false |
| get_my_wedding_budget | no tags | |
| get_my_guest_list | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digestcb2b6ddbb9163144
Scanned2026-10-20
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Wedyesday — wedding planning can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.