Find destination wedding venues and vendors, estimate costs, and manage your wedding plans. Includes 19 public discovery and planning tools plus 18 connected wedding tools for wedding details, guests, RSVP totals, events, accommodations and registry progress. Public tools work without sign-in; connected tools use OAuth with PKCE and follow Aisle’s wedding access and membership rules. Individual guest tools only expose guests confirmed as 13 or older and exclude guest notes and dietary details. RSVP totals include all ages. Estimates are planning figures, not supplier quotes or live availability. This connector does not book venues, charge cards or send messages.

MCP readiness

B · 86/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here C+, 70.0/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ

Valid MCP handshake	10/10	initialize and tools/list both answered.
Live MCP endpoint	23/25	Endpoint answers the MCP initialize handshake (5188 ms); very slow response -2.
Protocol revision	8/10	Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28.
Signed descriptor	n/a	No MCP standard defines a signed server descriptor.
Uptime (30 days)	15/15	30/30 probes succeeded over 30 days (100%).
Tool declaration	10/10	Lists 44 tool(s) with descriptions.
Verified identity	5/10	Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Freshness + modern flags	4/5	seen in a source within 7 days.
Auth declaration	2/5	Declares credential scheme: smithery_api_key.

Applicable criteria total 90 points, scaled to 100.

Responsiveness: Very slow (5188 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).

Measured 2026-11-11.

Nine criteria, the same as the A2A readiness score, read from our daily MCP probe (initialize + tools/list) and 30-day probe history. No MCP standard defines a signed server descriptor, so that criterion is n/a and the other 90 points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.

Compared with peers

Against 53,039 reachable MCP servers in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.

Readiness: Higher than 80% of peers; This listing 86 · peer median 81
Latency: Faster than 14% of peers; This listing 778 ms · peer median 326 ms

Where it loses the most points, and how to win them back

Verified identity −5 — Claim the listing and prove control of its domain.
Now: Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Auth declaration −3 — State how to authenticate (an auth scheme, or that none is needed).
Now: Declares credential scheme: smithery_api_key.
Live MCP endpoint −2 — Answer initialize and tools/list at the declared endpoint.
Now: Endpoint answers the MCP initialize handshake (5188 ms); very slow response -2.

How many agent tools actually work · All statistics

Listed in

Directories this entry was found in.

smithery since 2026-10-02 ↗

How to connect

MCP endpoint (streamable-http)

https://server.smithery.ai/aisle/aisle/mcp

JSON-RPC initialize probe

curl -X POST https://server.smithery.ai/aisle/aisle/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'

Homepage

https://aisle.wedding/mcp

Listed at (smithery)

https://aisle.wedding/mcp