# Wedding Seat (remote · mcp.wedding-seat.com)

Anonymous, no-login wedding planning: create a project, add guests, auto-generate a seating plan.

- Trust score: 70/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `mcp.wedding-seat.com`: 70/100 (this document), [markdown](https://verifymcp.io/servers/com-wedding-seat-wedding-planner/mcp.md), [page](https://verifymcp.io/servers/com-wedding-seat-wedding-planner/mcp)

## Channel facts

- Endpoint: `https://mcp.wedding-seat.com/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-08-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - 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**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 456 tokens (~76/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http com-wedding-seat-wedding-planner https://mcp.wedding-seat.com/mcp
```

### Codex

```toml
[mcp_servers.com-wedding-seat-wedding-planner]
url = "https://mcp.wedding-seat.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-wedding-seat-wedding-planner": {
      "type": "remote",
      "url": "https://mcp.wedding-seat.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-wedding-seat-wedding-planner --url https://mcp.wedding-seat.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-wedding-seat-wedding-planner:
    url: "https://mcp.wedding-seat.com/mcp"
```

### Other

```json
{
  "mcpServers": {
    "com-wedding-seat-wedding-planner": {
      "type": "http",
      "url": "https://mcp.wedding-seat.com/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-08-03 (score 70, +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-08-01 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 68, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 68, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 67, +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-07-27 (score 66, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 65)

First indexed and scored.

## MCP tools (6)

### `create_wedding_project` (~149 tokens)

Create a wedding project

Create a new anonymous Wedding Seat project (no login). Returns a projectKey (your secret handle for all later calls) plus the workspace URL the couple opens in a browser. The projectKey is the ONLY way to access the project again — keep it.

Input parameters:

- `culture` (string): Culture-pack key from list_culture_packs; omit to auto-pick
- `date` (string): Reception date, ISO 8601 (YYYY-MM-DD)
- `locale` (string): UI language code (e.g. en, sr, de); defaults to en
- `names` (string): Couple's names, e.g. 'Ana & Marko' — becomes the project title

### `add_guests` (~65 tokens)

Add guests

Add guests to a project (deduped by name+email). Provide the projectKey from create_wedding_project and a list of guests.

Input parameters:

- `guests` (array, required): Guests to add
- `projectKey` (string, required): The projectKey returned by create_wedding_project

### `generate_seating` (~101 tokens)

Generate a seating plan

Auto-generate a reception seating plan: creates round tables and seats every guest with the constraint-aware solver (keeps must-sit-together groups together). Returns how many were seated and a link to the visual editor.

Input parameters:

- `projectKey` (string, required): The projectKey returned by create_wedding_project
- `seatsPerTable` (integer): Seats per table (default 8)
- `tables` (integer): Number of tables; omit to size automatically

### `get_project_summary` (~53 tokens)

Get project summary

Read the current state of a project: guest counts by RSVP status, seating tables/capacity, and budget totals. Read-only.

Input parameters:

- `projectKey` (string, required): The projectKey returned by create_wedding_project

### `list_culture_packs` (~48 tokens)

List culture packs

List the available wedding culture packs (key, English name, cluster, sides). Use a pack key as the `culture` argument to create_wedding_project. Grounding/read-only.

### `list_tools` (~40 tokens)

List Wedding Seat tools

List Wedding Seat's free planning tools (seating chart, guest list, budget, checklist, invitation wording) with their public URLs. Grounding/read-only.

## Diagnostics

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

## Score history

- 2026-08-03: 70
- 2026-08-02: 69
- 2026-08-01: 69
- 2026-07-31: 68
- 2026-07-30: 68
- 2026-07-29: 67
- 2026-07-28: 66
- 2026-07-27: 66
- 2026-07-26: 65

## Links

- Remote endpoint: https://mcp.wedding-seat.com/mcp
- Repository: https://github.com/naturalnet/wedding-seat-app
- Website: https://wedding-seat.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-wedding-seat-wedding-planner/mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-wedding-seat-wedding-planner/mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/com-wedding-seat-wedding-planner/mcp