Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
nyna — AI wedding planner is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
tool-list score
23
tools declared
remote
at its publisher
—
calls last 7d
What it does
Wedding provider directory, gift ideas, and a couple's own wedding plan behind OAuth.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http nyna-ai-wedding-planner-mcp https://nyna.ai/mcp
# 2 — ask your agent for something these tools do
# list_provider_categories, list_cities, search_providers and 20 more
nyna — AI wedding planner costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
NYAll 1 server
nyna1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http nyna-ai-wedding-planner-mcp https://nyna.ai/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
23 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
[Free] Lists the kinds of wedding provider nyna indexes (venues, caterers, photographers…) — costs no credits and returns the closed set of category slugs that search_providers takes as category, each with its English and French name and its nyna page. Any category value outside this set is refused with the valid list.
No parameter schema on file.
[Free] Lists the featured cities — the ones with a nyna directory page — optionally filtered by region — costs no credits and returns city slugs, country, region and page. This is not the limit of coverage: search_providers takes any city, town or place name in the world as city ("Gardanne", "Bouc-Bel-Air 13320", "Istanbul"), and geocodes it once; the featured cities are simply the ones with a b
| Parameter | Type | Required | Notes |
|---|---|---|---|
| region | string | no | europe | north-america | asia | oceania | middle-east | latin-america | africa |
| featured_only | boolean | no | only the cities nyna features on the homepage |
| limit | integer | no | — |
[Free] Searches wedding providers — venues, caterers, photographers, florists and more — around any city or place in the world, by category and free text — costs no credits and returns up to 50 providers with address, distance from the city centre, Google rating, review count and nyna page, plus how old the index is. city is any city, town or place name ("Aix-en-Provence", "Gardanne", "Bouc-Bel-
| Parameter | Type | Required | Notes |
|---|---|---|---|
| category | string | no | a slug from list_provider_categories; omitted = every category |
| city | string | no | any city, town or place name in the world, e.g. "Gardanne" or "Bouc-Bel-Air 13320"; adding the country helps for small towns |
| q | string | no | free text: a name, a speciality or a cuisine, e.g. "halal", "turkish", "bastide" |
| min_rating | number | no | only providers rated at or above this |
| radius_km | number | no | search radius around the city centre in km, 5–100, default 25 |
| sort | string | no | relevance (default) | rating | reviews |
| limit | integer | no | default 20 |
[Free] Reads one provider by the id search_providers returns — costs no credits and returns at least what the search result held: name, address, city, category, Google rating and review count (from nyna’s index, or live from Google Places when the index has none and today’s budget allows), whether the listing is claimed, and — for a claimed listing — the owner’s description, services, website and
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | the provider id from search_providers |
[Free] Lists the gift categories and the countries the gift catalogue is localised for — costs no credits and returns the closed sets of slugs that search_gift_ideas takes as category and country.
No parameter schema on file.
[Free] Searches the wedding-gift ideas couples added to their nyna registries, by category, country, title and price — costs no credits and returns up to 50 ideas with price, currency, image and a store link (some links carry an affiliate tag that never changes the ordering), plus catalogue_size, how many ideas the catalogue holds for that country: it is a grown catalogue, not a store feed, and
| Parameter | Type | Required | Notes |
|---|---|---|---|
| category | string | no | — |
| country | string | no | defaults to france |
| q | string | no | free text matched against the title |
| max_price | number | no | — |
| limit | integer | no | default 20 |
[Sign-in required] Reads the connected account’s wedding — costs no credits and returns the date, venue, budget, guest count and theme in a writable half (exactly the fields update_wedding accepts, under the same names) plus a derived half with days remaining, guest totals and checklist progress. A member’s role decides what comes back: the budget is omitted for a role without budget:view.
No parameter schema on file.
[Sign-in required] Updates the wedding’s details — date, venue, budget, guest count, theme, notes — as a merge patch — costs no credits and returns the fields changed and whether the wedding was created by this call. Omitted fields are left alone; a value that contradicts what the couple said in nyna’s chat comes back as conflict and is written only when sent again within 15 minutes; share-contr
| Parameter | Type | Required | Notes |
|---|---|---|---|
| coupleNames | string | no | — |
| weddingDate | string | no | YYYY-MM-DD (e.g. 2027-06-12), or YYYY-MM when only the month is known (e.g. 2027-06), or YYYY for a year alone. Never invent a day the couple did not give. Empty string clears the date. |
| venue | string | no | — |
| venueName | string | no | — |
| theme | string | no | — |
| notes | string | no | — |
| budget | number | no | — |
| budgetMin | number | no | — |
| budgetMax | number | no | — |
| guestCount | integer | no | — |
| ceremonyType | string | no | — |
| ceremonyLocation | string | no | — |
| idempotency_key | string | no | any string of your choosing; the first result under it is returned again for 10 minutes |
[Sign-in required] Reads the couple’s checklist — costs no credits and returns each item with its id, title, status, due date and category, plus the totals (all, done, to do) so nothing has to be counted.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| status | string | no | default all |
| limit | integer | no | — |
[Sign-in required] Marks one checklist item done or not done — costs no credits and returns the item with its previous and new state. The item is addressed by the id get_checklist returns (stable even when the list changes) or by its index for items without an id; an item that does not exist is refused rather than created.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | no | the id from get_checklist (stable) |
| index | integer | no | the index from get_checklist, when the item has no id |
| done | boolean | yes | — |
| idempotency_key | string | no | any string of your choosing; the first result under it is returned again for 10 minutes |
[Sign-in required] Reads the guest list — costs no credits and returns each guest with RSVP status, side and table, plus head-count totals by status so nothing has to be tallied.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| rsvp | string | no | default all; the same values the app itself stores |
| limit | integer | no | — |
[Sign-in required] Appends up to 100 named guests to the guest list in one write — costs no credits and returns the names added, the names skipped as duplicates and the new total. Existing guests are left untouched, the whole batch is validated before anything is written, and a member whose role only proposes guests gets proposals recorded for the couple instead of additions.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| guests | array | yes | up to 100 guests per call |
| idempotency_key | string | no | any string of your choosing; the first result under it is returned again for 10 minutes |
[Sign-in required] Reads the wedding-day plan — costs no credits and returns the run sheet, vendor coordination status, guest figures, readiness score and flags, and the days remaining; what has not been filled in is named rather than guessed at.
No parameter schema on file.
[Sign-in required] Reads the connected account’s credit balance — costs no credits and returns the balance, the price of each metered action in the nyna app, and the list of MCP tools that spend credits (none today).
No parameter schema on file.
[Sign-in required] Generates a wedding menu — cocktail, starters, mains, desserts, drinks, cake and a children’s menu — sized to the connected account’s guest count, theme and budget — costs no credits (rate-limited to 10 generations a minute) and returns the menu for review; nothing is written to the wedding.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| prompt | string | yes | what the couple wants, e.g. "seasonal, vegetarian-friendly, autumn wedding" |
| language | string | no | language for the reply; default English |
| dietary | string | no | dietary needs to accommodate |
[Sign-in required] Generates a 10–15 event wedding-day timeline in 24h time, shaped by the connected account’s venue, ceremony type and guest count — costs no credits (rate-limited to 10 generations a minute) and returns the schedule for review; set_run_sheet is the separate call that writes one to the wedding.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| prompt | string | yes | the shape of the day, e.g. "church at 15:00, reception at the château, 120 guests" |
| language | string | no | language for the reply; default English |
[Sign-in required] Parses a pasted guest list — one per line or comma-separated, with or without emails and phones — into structured guests with detected roles — costs no credits (rate-limited to 10 a minute) and returns them for review; add_guests is the separate call that saves the ones kept.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| text | string | yes | the pasted list, up to 6000 characters |
| language | string | no | — |
[Sign-in required] Writes a reviewed timeline to the wedding as the day-of run sheet, replacing the one there — costs no credits and returns the number of events saved and the number replaced. Times are 24h HH:MM in chronological order; an out-of-order sheet is refused before anything is written.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| events | array | yes | — |
| idempotency_key | string | no | any string of your choosing; the first result under it is returned again for 10 minutes |
[Partner] Reads the connected provider account’s own listing — costs no credits and returns an editable half (exactly the fields update_provider_profile accepts, under the same names: description, services, price range, website, Instagram, phone) and a derived half nyna decides (business name, category, city, plan, verification, featuring, status).
No parameter schema on file.
[Partner] Updates the connected provider’s listing — description, services, price range, website, Instagram, phone — as a merge patch — costs no credits and returns the fields changed. Omitted fields are left alone; plan, verification, featuring and status are refused by name because they are sold or earned, never self-assigned.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| description | string | no | — |
| website | no | — | |
| string | no | — | |
| phone | string | no | — |
| services | array | no | — |
| photos | array | no | — |
| priceRange | object | no | — |
| idempotency_key | string | no | any string of your choosing; the first result under it is returned again for 10 minutes |
[Partner] Reads the enquiries couples sent through the connected provider’s nyna listing, newest first — costs no credits and returns each enquiry (sender name, message, wedding date, status) plus totals by status so the pipeline needs no counting.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| status | string | no | default all |
| limit | integer | no | default 25 |
[Partner] Reads the connected provider’s listing performance over a chosen window — costs no credits and returns views, enquiries and conversion for the window actually measured, naming any figure nyna does not collect rather than returning a null nobody can interpret.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| days | integer | no | window in days; default 30 |
[Free] Quotes a tool before it is called — costs no credits and returns the credits a successful call spends (0 for every tool today), the scopes it needs, the rate limits it runs under, its annotations and whether it accepts an idempotency_key. Nothing is charged on failure for any tool, so there is nothing to refund.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tool | string | yes | a tool name from tools/list |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install nyna — AI wedding planner or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 93 / 100
Release 2.0.0 · scanned 22 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings0 threat · 0 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digestd8b15351188ae92e2283073a9e48403c6e4dd589127c378b9e0b60e4102e41e4
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| list_provider_categories | no tags | |
| list_cities | no tags | |
| search_providers | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_provider | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| list_gift_categories | no tags | |
| search_gift_ideas | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_wedding | no tags | |
| update_wedding | state-write | state-write: declares readOnlyHint: false |
| get_checklist | no tags | |
| set_checklist_item | state-write | state-write: declares readOnlyHint: false |
| get_guests | no tags | |
| add_guests | state-write | state-write: declares readOnlyHint: false |
| get_day_of_timeline | no tags | |
| get_credit_balance | no tags | |
| suggest_menu | no tags | |
| suggest_day_schedule | no tags | |
| parse_guest_list | no tags | |
| set_run_sheet | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| get_provider_profile | no tags | |
| update_provider_profile | state-write | state-write: declares readOnlyHint: false |
| get_provider_inquiries | no tags | |
| get_provider_stats | no tags | |
| quote_cost | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digestd8b15351188ae92e
Scanned2026-10-22
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 2.0.0.
2.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish nyna — AI wedding planner can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.