Wedtide wedding seating
REMOTE · WEDTIDE.COM
Seat wedding guests at tables with keep-apart rules; returns an editable plan and seat finder.
Available components
Last scanned (6 hours ago)
Scores higher than 4% of remote servers
Unreachable for 6 days in a row. Last reached 17 Oct 2026.
Category Productivity and Notes
Degraded
One or more channels of this server are currently unreachable; their trust score is decaying and will reach 0 if they stay down.
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 Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC not yet verified: we couldn't validate it against a resolver. View diagnostics → Unverified
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
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.
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.
- 23 Oct 26 −14
The score moved with no change recorded against any check. We would rather say so than guess.
- 22 Oct 26 −13
The score moved with no change recorded against any check. We would rather say so than guess.
- 21 Oct 26 −14
The score moved with no change recorded against any check. We would rather say so than guess.
- 20 Oct 26 −14
The score moved with no change recorded against any check. We would rather say so than guess.
- 18 Oct 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- DNSSEC: fail → unverified ▼ security
- Stability: 0.37 → unverified ▼ security
- HSTS header: fail → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- HTTPS: unverified → pass ▲ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 17 Oct 26 +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.
- 15 Oct 26 +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.
- 13 Oct 26 +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.
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 23 Oct 2026 · Probed https://wedtide.com/api/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC inconclusive
Validation of wedtide.com. — Inconclusive
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| wedtide.com. | Error no A/AAAA/CNAME RRset answered for the name |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://wedtide.com/api/mcp | Unreachable | ||
| http (plaintext) | http://wedtide.com/api/mcp | HTTPS enforced |
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 →
create_seating_plan Create a wedding seating plan ~393
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.
| Name | Type | Req | Description |
|---|---|---|---|
| couple | string | – | The couple's names, shown as the plan's title, e.g. "Emma & James". |
| guests | string | yes | 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. |
No output schema declared.
No examples provided.
seating_tips Wedding seating etiquette ~139
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
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.
remote · wedtide.com
claude mcp add --transport http com-wedtide-seating 'https://wedtide.com/api/mcp'
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.