_ registry / mcp streamable-http · checked 33m ago

wedyesday

https://mcp.wedyesday.com

Registry code: 4d73da9b4a3ba755

api record

Wedyesday plans weddings. Anyone can search vendors, get regional cost guides and build a full checklist-and-budget plan with no account. When a couple wants to keep their plan, call create_wedyesday_workspace_link and give them the link. Tools named get_my_* / list_my_* / add_my_* / complete_my_* act on the couple's real Wedyesday workspace and need their account connected.

endpoint
https://mcp.wedyesday.com
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is wedyesday live?
Yes — it answered the hub's last check (checked 33m ago). It answered 100% of checks over the last 30 days.
Is wedyesday free to use?
Partly — some of its tools are open, others need a key or payment.
What tools does wedyesday have?
12 tools: build_wedding_plan, complete_my_wedding_task, create_wedyesday_workspace_link, add_my_wedding_task, get_wedyesday_pricing, get_wedding_cost_guide, search_wedding_vendors, list_wedding_markets, ….
Is wedyesday safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 99.6%· all time 99.6%

latency
543ms

last good check

priced tools
0

of 12 tools

_ answered our checks, 90 days 278 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • unknown → live
_ what it is for
topic
lifestyle & home home & family
used for
  • build a wedding checklist and budget
  • search wedding vendors
  • get regional wedding cost guide
  • add and complete wedding tasks
  • view a wedding budget
takes → gives
text → data
tools
9 reads3 changes data
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 12 tools
4 open4 auth-required 4 never probed 8 of 12 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_wedyesday_pricing reads open 4h ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "country": {
      "type": "string",
      "description": "ISO country code: AU, US, GB, NZ or IN. Pass the buyer's country — prices differ per market; defaults to AU when omitted."
    }
  },
  "additionalProperties": false
}
    arguments 10 lines
  • get_wedding_cost_guide reads open 11h ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "region": {
      "type": "string",
      "description": "Region slug from list_wedding_markets, e.g. \"melbourne\" or \"london\". Omit for the national figure."
    },
    "country": {
      "type": "string",
      "description": "ISO country code: AU, US, GB, NZ or IN. Pass the couple's country — figures are per market; defaults to AU when omitted."
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
  • search_wedding_vendors reads open 21h ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "city": {
      "type": "string",
      "description": "City name, e.g. \"Melbourne\" or \"London\"."
    },
    "limit": {
      "type": "integer",
      "description": "Maximum results, 1-25. Defaults to 8."
    },
    "query": {
      "type": "string",
      "description": "Free-text search, e.g. \"barn\" or \"documentary style\"."
    },
    "region": {
      "type": "string",
      "description": "State or region, e.g. \"VIC\" or \"California\"."
    },
    "country": {
      "type": "string",
      "description": "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."
    },
    "category": {
      "type": "string",
      "description": "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_rentals, photo_booth, lighting_decor, invitations, officiant, jewelry, travel."
    },
    "minRating": {
      "type": "number",
      "description": "Minimum average review rating, 1-5."
    },
    "priceBands": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Filter by price band. Any of: budget, standard, premium, luxury, quote_required."
    }
  },
  "additionalProperties": false
}
    arguments 41 lines
  • list_wedding_markets reads open 21h ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "country": {
      "type": "string",
      "description": "Optional ISO country code (AU, US, GB, NZ, IN). Supply it to list that market's regions."
    }
  },
  "additionalProperties": false
}
    arguments 10 lines
  • list_my_wedding_tasks reads auth-required 4h ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "description": "Maximum tasks to return, 1-40. Defaults to 15."
    },
    "filter": {
      "enum": [
        "open",
        "overdue",
        "done",
        "all"
      ],
      "type": "string",
      "description": "\"open\" (default) for everything not done, \"overdue\", \"done\", or \"all\"."
    },
    "weddingId": {
      "type": "string",
      "description": "Only needed when the account has more than one wedding."
    }
  },
  "additionalProperties": false
}
    arguments 24 lines
  • get_my_wedding_budget reads auth-required 11h ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "weddingId": {
      "type": "string",
      "description": "Only needed when the account has more than one wedding."
    }
  },
  "additionalProperties": false
}
    arguments 10 lines
  • get_my_wedding_dashboard reads auth-required 11h ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "weddingId": {
      "type": "string",
      "description": "Only needed when the account has more than one wedding."
    }
  },
  "additionalProperties": false
}
    arguments 10 lines
  • get_my_guest_list reads auth-required 21h ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "weddingId": {
      "type": "string",
      "description": "Only needed when the account has more than one wedding."
    }
  },
  "additionalProperties": false
}
    arguments 10 lines
  • build_wedding_plan reads unknown 4h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "guestCount"
  ],
  "properties": {
    "budget": {
      "type": "integer",
      "description": "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."
    },
    "region": {
      "type": "string",
      "description": "Region slug from list_wedding_markets, e.g. \"melbourne\" or \"london\". Drives the budget split and legal steps."
    },
    "season": {
      "enum": [
        "summer",
        "autumn",
        "winter",
        "spring"
      ],
      "type": "string",
      "description": "Required when dateMode is \"season\"."
    },
    "country": {
      "type": "string",
      "description": "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": {
      "enum": [
        "fixed",
        "season",
        "undecided"
      ],
      "type": "string",
      "description": "\"fixed\" when the date is set, \"season\" when only a season and year are known, \"undecided\" otherwise."
    },
    "location": {
      "type": "string",
      "description": "Where the wedding is, e.g. \"Melbourne, VIC\" or \"London\"."
    },
    "eventDate": {
      "type": "string",
      "description": "Wedding date as YYYY-MM-DD. Required when dateMode is \"fixed\"."
    },
    "guestCount": {
      "type": "integer",
      "description": "Expected number of guests, 2-2000."
    },
    "partnerOne": {
      "type": "string",
      "description": "First partner's first name."
    },
    "partnerTwo": {
      "type": "string",
      "description": "Second partner's first name."
    },
    "priorities": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Up to three things that matter most. Values: venue, photography, food, music, flowers, videography, attire, styling."
    },
    "seasonYear": {
      "type": "integer",
      "description": "Year for the chosen season."
    }
  },
  "additionalProperties": false
}
    arguments 71 lines
  • complete_my_wedding_task changes data unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "taskId"
  ],
  "properties": {
    "note": {
      "type": "string",
      "description": "Optional note recorded against the completion."
    },
    "taskId": {
      "type": "string",
      "description": "Task id from list_my_wedding_tasks."
    },
    "weddingId": {
      "type": "string",
      "description": "Only needed when the account has more than one wedding."
    }
  },
  "additionalProperties": false
}
    arguments 21 lines
  • create_wedyesday_workspace_link changes data unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "guestCount"
  ],
  "properties": {
    "budget": {
      "type": "integer",
      "description": "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."
    },
    "region": {
      "type": "string",
      "description": "Region slug from list_wedding_markets, e.g. \"melbourne\" or \"london\". Drives the budget split and legal steps."
    },
    "season": {
      "enum": [
        "summer",
        "autumn",
        "winter",
        "spring"
      ],
      "type": "string",
      "description": "Required when dateMode is \"season\"."
    },
    "country": {
      "type": "string",
      "description": "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": {
      "enum": [
        "fixed",
        "season",
        "undecided"
      ],
      "type": "string",
      "description": "\"fixed\" when the date is set, \"season\" when only a season and year are known, \"undecided\" otherwise."
    },
    "location": {
      "type": "string",
      "description": "Where the wedding is, e.g. \"Melbourne, VIC\" or \"London\"."
    },
    "eventDate": {
      "type": "string",
      "description": "Wedding date as YYYY-MM-DD. Required when dateMode is \"fixed\"."
    },
    "guestCount": {
      "type": "integer",
      "description": "Expected number of guests, 2-2000."
    },
    "partnerOne": {
      "type": "string",
      "description": "First partner's first name."
    },
    "partnerTwo": {
      "type": "string",
      "description": "Second partner's first name."
    },
    "priorities": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Up to three things that matter most. Values: venue, photography, food, music, flowers, videography, attire, styling."
    },
    "seasonYear": {
      "type": "integer",
      "description": "Year for the chosen season."
    }
  },
  "additionalProperties": false
}
    arguments 71 lines
  • add_my_wedding_task changes data unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "title"
  ],
  "properties": {
    "title": {
      "type": "string",
      "description": "What needs doing."
    },
    "dueDate": {
      "type": "string",
      "description": "Due date as YYYY-MM-DD."
    },
    "category": {
      "type": "string",
      "description": "Optional grouping, e.g. \"Venue\" or \"Attire\"."
    },
    "weddingId": {
      "type": "string",
      "description": "Only needed when the account has more than one wedding."
    },
    "description": {
      "type": "string",
      "description": "Optional detail."
    }
  },
  "additionalProperties": false
}
    arguments 29 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 4d73da9b4a3ba755.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/4d73da9b4a3ba755/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/4d73da9b4a3ba755/badge.svg)](https://brick.blue/agent/4d73da9b4a3ba755?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.