# Altessa Wedding Planner (remote · mcp.altessa.studio)

Reception layouts to scale, seating charts, wedding day timelines, and budgets. No login needed.

- Trust score: 76/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `mcp.altessa.studio`: 76/100 (this document), [markdown](https://verifymcp.io/servers/studio-altessa-altessa/mcp.md), [page](https://verifymcp.io/servers/studio-altessa-altessa/mcp)

## Channel facts

- Endpoint: `https://mcp.altessa.studio/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 72/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 78/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 23% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).
  - Supports UI / widget rendering.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http studio-altessa-altessa 'https://mcp.altessa.studio/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "studio-altessa-altessa": {
      "url": "https://mcp.altessa.studio/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "studio-altessa-altessa": {
      "type": "http",
      "url": "https://mcp.altessa.studio/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.studio-altessa-altessa]
url = "https://mcp.altessa.studio/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "studio-altessa-altessa": {
      "type": "remote",
      "url": "https://mcp.altessa.studio/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add studio-altessa-altessa --url 'https://mcp.altessa.studio/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  studio-altessa-altessa:
    url: "https://mcp.altessa.studio/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "studio-altessa-altessa": {
      "Transport": "http",
      "Url": "https://mcp.altessa.studio/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add studio-altessa-altessa -t streamable-http -u 'https://mcp.altessa.studio/mcp'
```

### Other

```json
{
  "mcpServers": {
    "studio-altessa-altessa": {
      "type": "http",
      "url": "https://mcp.altessa.studio/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 76, +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.

### 2026-11-02 (score 75, +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.

### 2026-10-30 (score 74, +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.

### 2026-10-28 (score 73, +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.

### 2026-10-26 (score 72, +1)

- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 1.0.0 → 1.0.1

### 2026-10-25 (score 71)

First indexed and scored.

## MCP tools (4)

### `plan_reception_layout` (~236 tokens)

Reception layout planner

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.

Input parameters:

- `bars` (integer)
- `cake_table` (boolean)
- `dance_floor` (boolean)
- `entertainment` (string)
- `food_service` (string)
- `guest_count` (integer, required): 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)

Output parameters:

- `fits` (boolean|null)
- `notes` (array)
- `room_ft` (object): The room the positions are drawn in, in feet.
- `seats_available` (integer)
- `seats_needed` (integer): One seat per guest.
- `share_url` (string): View-only link to this plan.
- `slack_square_feet` (number|null)
- `square_feet_needed` (number)
- `suggested_room_ft`
- `tables` (array): Table center positions in feet, same axes as zones.
- `tables_needed` (integer)
- `tables_that_fit` (integer): 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): Corner positions in feet from the entrance corner; x along the length, y across the width.

### `generate_seating_chart` (~152 tokens)

Seating chart generator

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.

Input parameters:

- `fill_strategy` (string)
- `guests` (array, required)
- `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)

Output parameters:

- `share_url` (string): View-only link to this chart.
- `tables` (array)
- `truncated` (boolean): True when names or tables were cut to stay under 50 KB.
- `unseated` (array)
- `warnings` (array)

### `build_wedding_timeline` (~188 tokens)

Wedding day timeline builder

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.

Input parameters:

- `ceremony_minutes` (integer)
- `ceremony_time` (string, required): 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.

Output parameters:

- `events` (array)
- `share_url` (string): View-only link to this timeline.
- `sunset_time` (string|null)
- `warnings` (array)

### `estimate_wedding_budget` (~114 tokens)

Wedding budget breakdown

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.

Input parameters:

- `guest_count` (integer)
- `priorities` (array)
- `region` (string)
- `style` (string)
- `total_budget_usd` (integer)

Output parameters:

- `assumptions` (array)
- `categories` (array)
- `contingency_usd` (integer)
- `guest_count` (integer)
- `per_guest_usd` (integer)
- `share_url` (string): View-only link to this budget.
- `total_budget_usd` (integer)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/studio-altessa-altessa/mcp#diagnostics

## Score history

- 2026-11-05: 76
- 2026-11-04: 76
- 2026-11-03: 75
- 2026-11-02: 75
- 2026-11-01: 74
- 2026-10-31: 74
- 2026-10-30: 74
- 2026-10-29: 73
- 2026-10-28: 73
- 2026-10-27: 72
- 2026-10-26: 72
- 2026-10-25: 71

## Common questions

### 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.

## Links

- Remote endpoint: https://mcp.altessa.studio/mcp
- Website: https://www.altessa.studio/plugins
- Changelog RSS feed: https://verifymcp.io/servers/studio-altessa-altessa/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/studio-altessa-altessa/mcp.json
- HTML version of this page: https://verifymcp.io/servers/studio-altessa-altessa/mcp