Home / MCP registry index / ai.nyna/mcp
nyna — AI wedding planner
ai.nyna/mcp in the official MCP registry.
Endpoint https://nyna.ai/mcp. Source: github.com/Bros-AI/nyna-mcp.
The registry describes it as: Wedding provider directory, gift ideas, and a couple's own wedding plan behind OAuth.
We read its 23 tools on 2026-10-26. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
list_provider_categories list_cities search_providers get_provider list_gift_categories search_gift_ideas get_wedding update_wedding get_checklist set_checklist_item get_guests add_guests get_day_of_timeline get_credit_balance suggest_menu suggest_day_schedule parse_guest_list set_run_sheet get_provider_profile update_provider_profile get_provider_inquiries get_provider_stats quote_cost
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/ai-nyna-mcp)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.