# Wedtide wedding seating (remote · wedtide.com)

Seat wedding guests at tables with keep-apart rules; returns an editable plan and seat finder.

- Trust score: 14/100 (low)
- Change this week: −54
- Registry status: active
- Liveness: degraded
- Owner verified: no
- Last scored: 2026-10-23

> **Degraded**: one or more channels of this server are currently unreachable; their trust score is decaying and will reach 0 if they stay down.

## Components

- remote · `wedtide.com`: 14/100 (this document), [markdown](https://verifymcp.io/servers/com-wedtide-seating/api-mcp.md), [page](https://verifymcp.io/servers/com-wedtide-seating/api-mcp)

## Channel facts

- Endpoint: `https://wedtide.com/api/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-10-23.

- **Endpoint Security**: 11/100
  - TLS not yet verified: we couldn't open a connection to check the certificate.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS not yet verified: we couldn't read the response headers to check for it.
  - DNSSEC not yet verified: we couldn't validate it against a resolver.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but we couldn't connect to verify it.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**Unverified: 5 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the Wedtide wedding seating MCP server?

Wedtide wedding seating is a hosted endpoint at https://wedtide.com/api/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 com-wedtide-seating 'https://wedtide.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-wedtide-seating": {
      "url": "https://wedtide.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-wedtide-seating": {
      "type": "http",
      "url": "https://wedtide.com/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-wedtide-seating]
url = "https://wedtide.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-wedtide-seating": {
      "type": "remote",
      "url": "https://wedtide.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-wedtide-seating --url 'https://wedtide.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-wedtide-seating:
    url: "https://wedtide.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-wedtide-seating": {
      "Transport": "http",
      "Url": "https://wedtide.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-wedtide-seating -t streamable-http -u 'https://wedtide.com/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-wedtide-seating": {
      "type": "http",
      "url": "https://wedtide.com/api/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-10-23 (score 14, −14)

The score moved with no change recorded against any check. We would rather say so than guess.

### 2026-10-22 (score 28, −13)

The score moved with no change recorded against any check. We would rather say so than guess.

### 2026-10-21 (score 41, −14)

The score moved with no change recorded against any check. We would rather say so than guess.

### 2026-10-20 (score 55, −14)

The score moved with no change recorded against any check. We would rather say so than guess.

### 2026-10-18 (score 69, 0)

- [security regression] Endpoint reachability: reachable → unreachable
- [security regression] DNSSEC: fail → unverified
- [security regression] Stability: 0.37 → unverified
- [security regression] HSTS header: fail → unverified
- [security regression] Authorization: partial → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] TLS certificate: pass → unverified
- [security regression] Transport: pass → fail
- [security improvement] HTTPS: unverified → pass
- [functional regression] Capabilities: fail → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-10-17 (score 69, +1)

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

### 2026-10-15 (score 68, +1)

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

### 2026-10-13 (score 67, +1)

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

## MCP tools (2)

### `create_seating_plan` (~393 tokens)

Create a wedding seating plan

Arrange a wedding guest list at tables and return a link that opens the plan in Wedtide. Use when the user shares a guest list (pasted names, a spreadsheet, CSV) and wants a seating chart or table assignments. Couples and families written on one line ("Ana & Luis", "The Smiths: John, Mary, Tim (kid)") are kept at the same table; rules keep named guests apart or together. Returns a short summary of who sits at each table and anything that could not be satisfied, plus two links: plan_url opens the full, editable plan in Wedtide (saved on the user's device; they can move people, view the room in 3D, print, export), and finder_url is a page guests open to type their name and see their seat. Nothing is stored on a server; the guest list is encoded in the link.

Input parameters:

- `couple` (string): The couple's names, shown as the plan's title, e.g. "Emma & James".
- `guests` (string, required): The guest list as text. One party per line; "&", "+", "and" or commas join people who arrive together. A line ending in ":" starts a group ("Bride's family:"). "(kid)" marks a child. A CSV or tab-sep…
- `rules` (array): Requests about specific guests, by name as written in the list. "apart" keeps two guests at different tables (exes, feuding relatives); "together" seats them at the same table.
- `seats_per_table` (integer): Seats at each round table. Default 10.
- `setting` (string): The look of the 3D room in Wedtide. Default ballroom.

### `seating_tips` (~139 tokens)

Wedding seating etiquette

Concise, practical wedding seating etiquette: head table or sweetheart table, where parents sit, divorced or feuding parents, kids tables, plus-ones, singles, and how many tables to plan. Use it when the user asks who should sit where or how to handle a delicate seating situation. Optional culture adds notes for some traditions; guests adds a table count.

Input parameters:

- `culture` (string): Optional tradition or region, e.g. "american", "jewish", "latin american", "indian", "chinese". Unknown values get the general guidance.
- `guests` (integer): Optional number of guests, for a table count.

## Diagnostics

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

## Score history

- 2026-10-23: 14
- 2026-10-22: 28
- 2026-10-21: 41
- 2026-10-20: 55
- 2026-10-19: 69
- 2026-10-18: 69
- 2026-10-17: 69
- 2026-10-16: 68
- 2026-10-15: 68
- 2026-10-14: 67
- 2026-10-13: 67
- 2026-10-12: 66
- 2026-10-11: 66
- 2026-10-10: 65
- 2026-10-09: 65
- 2026-10-06: 57

## Common questions

### What is the Wedtide wedding seating MCP server?

Wedtide wedding seating is an MCP server listed in the public MCP registry as com.wedtide/seating. Seat wedding guests at tables with keep-apart rules; returns an editable plan and seat finder. This page covers its hosted endpoint (https://wedtide.com/api/mcp).

### Is the Wedtide wedding seating MCP server safe to use?

Wedtide wedding seating scores 14 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 Wedtide wedding seating MCP server expose?

Wedtide wedding seating exposes 2 tools: create_seating_plan, seating_tips. Their descriptions and schemas cost roughly 532 tokens of context every time the server is loaded.

### Does the Wedtide wedding seating MCP server require authentication?

Its publisher declares no required credentials for Wedtide wedding seating. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

### Is the Wedtide wedding seating MCP server still maintained?

Wedtide wedding seating is still listed in the MCP registry, but we have not been able to reach this channel for several days and its score is decaying. We last reached this channel on 17 October 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://wedtide.com/api/mcp
- Website: https://wedtide.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-wedtide-seating/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-wedtide-seating/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-wedtide-seating/api-mcp