protogrid

Search / com.wedtide/seating

Wedtide wedding seating

not classified

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

v1.0.0 · active · website · descriptor JSON · versions

Not classified yet.The remote endpoints have not been probed successfully, or the listing has nothing to connect to.
Quality85good
Trust54of 100
Uptime, 30 days90%
Latency p50203 ms

Connect

8 clients · secrets stay placeholders
{
  "mcpServers": {
    "seating": {
      "type": "http",
      "url": "https://wedtide.com/api/mcp"
    }
  }
}
claude mcp add --transport http seating https://wedtide.com/api/mcp
[mcp_servers.seating]
url = "https://wedtide.com/api/mcp"
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "seating": {
      "type": "remote",
      "url": "https://wedtide.com/api/mcp",
      "enabled": true
    }
  }
}
{
  "mcpServers": {
    "seating": {
      "type": "http",
      "url": "https://wedtide.com/api/mcp"
    }
  },
  "deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=seating&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vd2VkdGlkZS5jb20vYXBpL21jcCJ9"
}
{
  "servers": {
    "seating": {
      "type": "http",
      "url": "https://wedtide.com/api/mcp"
    }
  }
}
{
  "mcpServers": {
    "seating": {
      "httpUrl": "https://wedtide.com/api/mcp"
    }
  }
}
extensions:
  "seating":
    enabled: true
    name: "seating"
    type: streamable_http
    uri: "https://wedtide.com/api/mcp"
    timeout: 300

Quality 85 / 100good

protocol75 · weight 25
  • warn
    protocol.modernnewest supported version is 2025-06-18; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
  • n/a
    protocol.statelessonly applies to 2026-07-28 servers
  • pass
    protocol.transportstreamable HTTP
  • n/a
    protocol.list_ttlonly applies to 2026-07-28 servers
authorizationn/a · weight 15
  • n/a
    auth.prm, auth.as_metadata, auth.cimdno remote uses OAuth
  • n/a
    auth.secret_in_urlno templated URL
tool hygiene86 · weight 30
  • pass
    tools.descriptionsevery tool has a description
  • pass
    tools.description_lengthdescriptions are concise
  • pass
    tools.schemasevery tool has an object input schema
  • pass
    tools.annotations2 of 2 tools declare readOnlyHint or destructiveHint
  • fail
    tools.directory_hintsno tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: create_seating_plan (idempotentHint); seating_tips (idempotentHint)
  • pass
    tools.token_costabout 740 tokens to load every tool
  • pass
    tools.api_dumptools are not a one-to-one API dump
stability100 · weight 15
  • pass
    stability.changes2 tool changes in 30 days
  • pass
    stability.rug_pullno tool changed its meaning under the same name
dependenciesn/a · weight 15
  • n/a
    deps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI package

2 tools, about 740 tokens to load them all · tool set 8a00cad58bd1 · tools last changed 2026-10-06 · checked 2026-10-20 11:08 UTC

Tool changes

  • seating_tipschangedannotations
  • create_seating_planchangeddescription, annotations
    before

    Arrange a wedding guest list at tables and return a link that opens the plan in Wedtide. Use it whenever 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. Give the user both links unchanged. Nothing is stored on a server; the guest list is encoded in the link.

    after · 94% of words in common

    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.

Full history: list_changes · trend: quality JSON.

Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.

Trust 54 / 100

no-repositoryunreachable
provenance55
liveness6
freshness100
hygiene80

+dns-namespace +website -unreachable(3 failures) +updated-15d-ago -no-repository

Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.

Endpoints

remoteauthreachableuptime 30dp50protocollast ok
https://wedtide.com/api/mcp streamable-httpnoneno (3 failures)90%203 ms2025-06-182026-10-17

Tools (2)

create_seating_planread-onlyArrange 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.
seating_tipsread-onlyConcise, 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.

Schemas: list_tools.

Similar MCP servers

Official server.json
{
  "name": "com.wedtide/seating",
  "title": "Wedtide wedding seating",
  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
  "remotes": [
    {
      "url": "https://wedtide.com/api/mcp",
      "type": "streamable-http"
    }
  ],
  "version": "1.0.0",
  "websiteUrl": "https://wedtide.com/",
  "description": "Seat wedding guests at tables with keep-apart rules; returns an editable plan and seat finder."
}