# PartyPlan

> Party budgets, headcount quantities, timelines and checklists. Free.

- name: io.github.everyai-com/party-plan
- version: 1.0.0
- connection class: R0 (autonomous)
- trust: 89/100 flags: duplicate-repo
- quality: 79/100 (good)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/io.github.everyai-com%2Fparty-plan
- tools: https://api.protogrid.dev/v1/servers/io.github.everyai-com%2Fparty-plan/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "party-plan": {
      "type": "http",
      "url": "https://party-plan.magicteams.ai/mcp"
    }
  }
}
```


## Trust

- hygiene: 80
- liveness: 98
- freshness: 100
- provenance: 80
- drivers: +repository +namespace-matches-repo +reachable +uptime-95% +updated-16d-ago -duplicate-repo(15 names)
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 79/100 (good)

### protocol: 88 (weight 25)

- pass `protocol.modern`: supports 2026-07-28 (server/discover)
- pass `protocol.stateless`: answers without a session
- pass `protocol.transport`: streamable HTTP
- warn `protocol.list_ttl`: tools/list carries no ttlMs, so clients re-fetch it

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 100 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 4 of 4 tools declare readOnlyHint or destructiveHint
- pass `tools.directory_hints`: every tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHint
- pass `tools.token_cost`: about 855 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: 25 (weight 15)

- warn `stability.changes`: 8 tool changes in 30 days
- fail `stability.rug_pull`: 8 tools kept their name but changed most of their description in 30 days; review before trusting them

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 4, about 855 tokens to load them all
- tool set hash: e9d15ad1ff27fea873c4c50412ff956d
- tools last changed: 2026-10-10T13:26:28.360Z
- badge: [![protogrid quality](https://protogrid.dev/badge/io.github.everyai-com/party-plan.svg)](https://protogrid.dev/servers/io.github.everyai-com/party-plan)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

- 2026-10-10 `party_checklist` changed (description, inputSchema, outputSchema, annotations) **meaning changed**
  - before: Generate a party checklist by category for a home or venue. Use when planning a party, NOT when planning a party budget.
  - after: Generate a supplies and prep checklist grouped by area (food and drink, decorations, music and activities, practical, safety) for a home or venue party, with extra items for keywords like pool, bbq, costume, outdoor, kids, alcohol or potluck. Use when preparing what to buy and set up. Do NOT use for a dated plan (use party_timeline).
- 2026-10-10 `party_timeline` changed (description, inputSchema, outputSchema, annotations) **meaning changed**
  - before: Generate a party timeline for a specific event date. Use when planning a party with multiple tasks. Do NOT use when budgeting for the party, use party_budget instead.
  - after: Build a dated countdown plan for a party, with task lists at 6 weeks, 4, 3, 2 and 1 week, 3 days, the day before and the day itself. Use when the date is set and the host needs to know what to do when. Do NOT use for spending (use party_budget) or a categorized supplies list (use party_checklist).
- 2026-10-10 `headcount_plan` changed (description, inputSchema, outputSchema, annotations) **meaning changed**
  - before: Calculate expected attendance and shopping quantities from an invite list. Use when RSVPs start arriving; use party_budget to estimate costs.
  - after: Estimate how many invited guests will attend (adults vs children) and the food, drink, cake, favor and plate quantities to buy, with standard buffers. Use when sizing the shopping list from an invite count. Do NOT use for spending (use party_budget) or a dated to-do plan (use party_timeline).
- 2026-10-10 `party_budget` changed (description, inputSchema, outputSchema, annotations) **meaning changed**
  - before: Calculate a party budget split across categories and per-guest spend. Use when planning what to spend before booking; use headcount_plan to estimate guest count.
  - after: Allocate a total party budget (USD) across seven categories (venue, food and drink, cake, decorations, entertainment, favors, contingency) by spending style, with per-guest spend and saving tips. Use when deciding what to spend before booking. Do NOT use to estimate attendance or food quantities (use headcount_plan).
- 2026-10-06 `party_checklist` changed (title, description, outputSchema, annotations) **meaning changed**
  - before: Build a checklist grouped by food and drink, decorations, music and activities, practical items and safety, tailored to a home or venue party. Optional extras keywords (pool, bbq, costume, outdoor, kids, alcohol, potluck) add specific items and safety notes.
  - after: Generate a party checklist by category for a home or venue. Use when planning a party, NOT when planning a party budget.
- 2026-10-06 `party_timeline` changed (title, description, outputSchema, annotations) **meaning changed**
  - before: Build a countdown plan for a party date: dated milestones at T-42, T-28, T-21, T-14, T-7, T-3, T-1 days and the day itself, each with tasks covering venue, invitations, menu, cake, decorations, confirmations, setup and the day-of run sheet.
  - after: Generate a party timeline for a specific event date. Use when planning a party with multiple tasks. Do NOT use when budgeting for the party, use party_budget instead.
- 2026-10-06 `headcount_plan` changed (title, description, outputSchema, annotations) **meaning changed**
  - before: Turn an invite list into expected attendance and shopping quantities: mains portions, drinks, cake slices, favors and plates with standard buffers. Use once RSVPs start arriving; attendance assumes adults only unless children_pct is given.
  - after: Calculate expected attendance and shopping quantities from an invite list. Use when RSVPs start arriving; use party_budget to estimate costs.
- 2026-10-06 `party_budget` changed (title, description, outputSchema, annotations) **meaning changed**
  - before: Allocate a party budget across venue, food and drink, cake, decorations, entertainment, favors and contingency, with per-guest spend and category tips. Use when planning what to spend before booking; style picks the split (budget, standard or premium).
  - after: Calculate a party budget split across categories and per-guest spend. Use when planning what to spend before booking; use headcount_plan to estimate guest count.

Full history: https://api.protogrid.dev/v1/servers/io.github.everyai-com%2Fparty-plan/changes

## Remotes

- https://party-plan.magicteams.ai/mcp (streamable-http, auth none, reachable true, uptime30d 0.9516129)

## Packages

_none_

## Tools (4)

- `headcount_plan`: Estimate how many invited guests will attend (adults vs children) and the food, drink, cake, favor and plate quantities to buy, with standard buffers. Use when sizing the shopping list from an invite count. Do NOT use for spending (use party_budget) or a dated to-do plan (use party_timeline).
- `party_budget`: Allocate a total party budget (USD) across seven categories (venue, food and drink, cake, decorations, entertainment, favors, contingency) by spending style, with per-guest spend and saving tips. Use when deciding what to spend before booking. Do NOT use to estimate attendance or food quantities (use headcount_plan).
- `party_checklist`: Generate a supplies and prep checklist grouped by area (food and drink, decorations, music and activities, practical, safety) for a home or venue party, with extra items for keywords like pool, bbq, costume, outdoor, kids, alcohol or potluck. Use when preparing what to buy and set up. Do NOT use for a dated plan (use party_timeline).
- `party_timeline`: Build a dated countdown plan for a party, with task lists at 6 weeks, 4, 3, 2 and 1 week, 3 days, the day before and the day itself. Use when the date is set and the host needs to know what to do when. Do NOT use for spending (use party_budget) or a categorized supplies list (use party_checklist).