Wedding Seat MCP server
com.wedding-seat/wedding-plannerwedding-seat.comstreamable-httpv1.0.0Scanned
Anonymous, no-login wedding planning: create a project, add guests, auto-generate a seating plan.
6 tools: 3 change things and 3 only read.
- Reads private data · 1
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
3 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Wedding Seat MCP server can do
The Wedding Seat MCP server is published by wedding-seat.com, a domain the MCP Registry verified. It has 6 tools. It can create or change data (3 tools: create_wedding_project, add_guests and generate_seating), but cannot delete data. 3 tools only read.
1 tool reads private data (get_project_summary).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 11, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
6 tools
Changes things 3Claude Code: ask
add_guestsAdd guests to a project (deduped by name+email).No findings
Why it is in this group
- The name "add_guests" says "add": a word for a change.
Description, as the server wrote it Add guests to a project (deduped by name+email). Provide the projectKey from create_wedding_project and a list of guests.
create_wedding_projectCreate a new anonymous Wedding Seat project (no login).No findings
Why it is in this group
- The name "create_wedding_project" says "create": a word for a change.
Description, as the server wrote it 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.
generate_seatingAuto-generate a reception seating plan: creates round tables and seats every guest with the constraint-aware solver (keeps must-sit-together groups together).No findings
Why it is in this group
- The name "generate_seating" says "generate": a word for a change.
Description, as the server wrote it 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.
Only reads 3Show 3 read-only tools
get_project_summaryRead the current state of a project: guest counts by RSVP status, seating tables/capacity, and budget totals.Reads private dataNo findings
Why it is in this group
- The name "get_project_summary" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "read" and "table": it reads databases.
Description, as the server wrote it Read the current state of a project: guest counts by RSVP status, seating tables/capacity, and budget totals. Read-only.
list_culture_packsList the available wedding culture packs (key, English name, cluster, sides).No findings
Why it is in this group
- The name "list_culture_packs" says "list": a word for reading.
Description, as the server wrote it 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_toolsList Wedding Seat's free planning tools (seating chart, guest list, budget, checklist, invitation wording) with their public URLs.No findings
Why it is in this group
- The name "list_tools" says "list": a word for reading.
Description, as the server wrote it List Wedding Seat's free planning tools (seating chart, guest list, budget, checklist, invitation wording) with their public URLs. Grounding/read-only.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:50 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 3
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.wedding-seat.com/mcp: tools/list returned 6 tools to an anonymous client, including create_wedding_project (write), add_guests (write), generate_seating (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http wedding-planner https://mcp.wedding-seat.com/mcpclaude mcp add --transport http wedding-planner https://mcp.wedding-seat.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__wedding-planner__get_project_summary",
"mcp__wedding-planner__list_culture_packs",
"mcp__wedding-planner__list_tools"
],
"ask": [
"mcp__wedding-planner__create_wedding_project",
"mcp__wedding-planner__add_guests",
"mcp__wedding-planner__generate_seating"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as wedding-planner. Review it before you use it.
Capability tags behind 1 rule
- mcp__wedding-planner__get_project_summary private-data
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.wedding-seat/wedding-planner/verify?hash=63348a393624d392d7ed13032f20dae190459caf3e3bc1c7e2be82600c943ec0" | jq -e '.changed == false'Pinned hash 63348a393624, from Nov 11, 2026, 06:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.wedding-seat/wedding-planner/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.wedding-seat/wedding-planner)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:10 UTC.
Wedding Seat MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Wedding Seat MCP server safe?
- No scan can promise that. What its definitions show: 6 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Wedding Seat MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Wedding Seat MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Wedding Seat MCP server have?
- 6 tools: 3 write, 3 read. create_wedding_project, add_guests, generate_seating, get_project_summary, list_culture_packs and list_tools.
Does the Wedding Seat MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Wedding Seat MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Wedding Seat MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 11, 2026.