Altessa Wedding Planner
REMOTE · MCP.ALTESSA.STUDIO
Reception layouts to scale, seating charts, wedding day timelines, and budgets. No login needed.
Available components
Last scanned (5 hours ago)
Scores higher than 66% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Productivity and Notes
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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. 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 Usability72
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 834 tokens (~166/item across 5 items; 4 tools + 1 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 Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage78
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 23% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
- Supports UI / widget rendering.Pass
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.0.0 → 1.0.1 functional
- 25 Oct 26 71
First indexed and scored.
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 5 Nov 2026 · Probed https://mcp.altessa.studio/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.altessa.studio | CN=YR1,O=Let's Encrypt,C=US | 24 Oct 2026 | 22 Jan 2027 | RSA 2048 | SHA256-RSA | 51a92931384793b0d05e9fbe9fb8782792e |
| SANs: mcp.altessa.studio | ||||||
| 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.altessa.studio. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| studio. | present | 1354 | 8 | Verified |
| altessa.studio. | absent | 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.altessa.studio/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.altessa.studio/mcp | HTTPS enforced | 308 | https://mcp.altessa.studio/mcp |
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 →
build_wedding_timeline Wedding day timeline builder ~188
Use this when someone wants a minute-by-minute wedding day schedule: getting ready, first look, ceremony, cocktail hour, reception, send-off. Needs the ceremony start time; everything else has defaults. Do not use for the months-long planning checklist or vendor payment schedules.
| Name | Type | Req | Description |
|---|---|---|---|
| ceremony_minutes | integer | – | – |
| ceremony_time | string | yes | Ceremony start, 24-hour HH:MM. |
| cocktail_hour_minutes | integer | – | – |
| first_look | boolean | – | – |
| hair_and_makeup_people | integer | – | – |
| location | string | – | City and state, for sunset. |
| photo_priorities | array | – | – |
| reception_hours | number | – | – |
| same_venue | boolean | – | – |
| send_off | string | – | – |
| travel_minutes | integer | – | – |
| wedding_date | string | – | YYYY-MM-DD, for sunset. |
| Name | Type | Req | Description |
|---|---|---|---|
| events | array | yes | – |
| share_url | string | – | View-only link to this timeline. |
| sunset_time | string|null | yes | – |
| warnings | array | yes | – |
No examples provided.
estimate_wedding_budget Wedding budget breakdown ~114
Use this when someone gives a total wedding budget, a guest count, or both and wants a category-by-category split (venue, catering, photo and video, flowers, music, attire, stationery, and so on) with per-guest math and a contingency line. Do not use for tracking actual spending or vendor payments.
| Name | Type | Req | Description |
|---|---|---|---|
| guest_count | integer | – | – |
| priorities | array | – | – |
| region | string | – | – |
| style | string | – | – |
| total_budget_usd | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| assumptions | array | yes | – |
| categories | array | yes | – |
| contingency_usd | integer | yes | – |
| guest_count | integer | yes | – |
| per_guest_usd | integer | yes | – |
| share_url | string | – | View-only link to this budget. |
| total_budget_usd | integer | yes | – |
No examples provided.
generate_seating_chart Seating chart generator ~152
Use this when someone has a list of wedding guests and wants them assigned to tables, keeping families, friend groups, or couples together and keeping specific people apart. Accepts names with optional group labels and keep-apart pairs. Returns table assignments and a shareable chart. Do not use for floor plans without names (use plan_reception_layout) or for RSVP tracking.
| Name | Type | Req | Description |
|---|---|---|---|
| fill_strategy | string | – | – |
| guests | array | yes | – |
| head_table_names | array | – | – |
| keep_apart | array | – | Pairs of names to seat at different tables. |
| keep_together | array | – | – |
| seats_per_table | integer | – | – |
| table_count | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| share_url | string | – | View-only link to this chart. |
| tables | array | yes | – |
| truncated | boolean | – | True when names or tables were cut to stay under 50 KB. |
| unseated | array | yes | – |
| warnings | array | yes | – |
No examples provided.
plan_reception_layout Reception layout planner ~236
Use this when someone wants to plan a wedding reception floor plan, figure out how many tables fit in a room, or check whether a venue space can hold their guest count with a dance floor, bar, buffet, DJ or band, and head table. Needs guest count; room dimensions in feet are optional (if missing, returns the space required instead of a fit check). Do not use for ceremony seating, seating assignments by name (use generate_seating_chart), or venue search.
| Name | Type | Req | Description |
|---|---|---|---|
| bars | integer | – | – |
| cake_table | boolean | – | – |
| dance_floor | boolean | – | – |
| entertainment | string | – | – |
| food_service | string | – | – |
| guest_count | integer | yes | Total guests, including the couple. |
| head_table | string | – | – |
| room_length_ft | number | – | Room length in feet. |
| room_width_ft | number | – | Room width in feet. |
| seats_per_table | integer | – | Defaults by shape: round_60 8, round_72 10, rectangle_8ft 10, mixed 8. |
| table_shape | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| fits | boolean|null | yes | – |
| notes | array | yes | – |
| room_ft | object | yes | The room the positions are drawn in, in feet. |
| seats_available | integer | yes | – |
| seats_needed | integer | yes | One seat per guest. |
| share_url | string | – | View-only link to this plan. |
| slack_square_feet | number|null | yes | – |
| square_feet_needed | number | yes | – |
| suggested_room_ft | – | yes | – |
| tables | array | yes | Table center positions in feet, same axes as zones. |
| tables_needed | integer | yes | – |
| tables_that_fit | integer | yes | Tables placed in the room; fewer than tables_needed when the room is too small. |
| truncated | boolean | – | True when table positions were dropped to stay under 50 KB. |
| zones | array | yes | Corner positions in feet from the entrance corner; x along the length, y across the width. |
No examples provided.
How do I install the Altessa Wedding Planner MCP server?
Altessa Wedding Planner is a hosted endpoint at https://mcp.altessa.studio/mcp, 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.altessa.studio
claude mcp add --transport http studio-altessa-altessa 'https://mcp.altessa.studio/mcp'
What is the Altessa Wedding Planner MCP server?
Altessa Wedding Planner is an MCP server listed in the public MCP registry as studio.altessa/altessa. Reception layouts to scale, seating charts, wedding day timelines, and budgets. No login needed. This page covers its hosted endpoint (https://mcp.altessa.studio/mcp).
Is the Altessa Wedding Planner MCP server safe to use?
Altessa Wedding Planner scores 76 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 Altessa Wedding Planner MCP server expose?
Altessa Wedding Planner exposes 4 tools: plan_reception_layout, generate_seating_chart, build_wedding_timeline, estimate_wedding_budget. Their descriptions and schemas cost roughly 690 tokens of context every time the server is loaded.
Does the Altessa Wedding Planner MCP server require authentication?
No. We connected to Altessa Wedding Planner without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Altessa Wedding Planner MCP server still maintained?
Altessa Wedding Planner is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.