PartyPlan
REMOTE · PARTY-PLAN.MAGICTEAMS.AI
Party budgets, headcount quantities, timelines and checklists. Free.
Available components
Last scanned (14 hours ago)
Scores higher than 69% of remote servers
Reachable. Last reached 23 Oct 2026.
Category Productivity and Notes
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 655 tokens (~163/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability check failed: schema churn in the 19 days we've observed: 0 tool removals, 3 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 19 to 23.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 16.
- 19 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 6 to 9.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 0 to 3.
- 10 Oct 26 −3
- Stability: 0.17 → fail ▼ security
- A breaking change shipped without a version bump: still 1.0.0 ▼ security
- Tool “headcount_plan” rewrote its description, which is the text the model reads security
- Tool “party_budget” rewrote its description, which is the text the model reads security
- Tool “party_checklist” rewrote its description, which is the text the model reads security
- Tool “party_timeline” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- “headcount_plan” changed the type of “invited”: number → integer ▼ functional
- “party_budget” changed the type of “guests”: number → integer ▼ functional
- “party_timeline” changed the type of “guests”: number → integer ▼ functional
- Schema quality: good → excellent functional
- “headcount_plan” reworded the description of “children_pct” cosmetic
- “headcount_plan” reworded the description of “expected_decline_pct” cosmetic
- “headcount_plan” reworded the description of “invited” cosmetic
- “party_budget” reworded the description of “budget” cosmetic
- “party_budget” reworded the description of “guests” cosmetic
- “party_budget” reworded the description of “style” cosmetic
- “party_checklist” reworded the description of “extras” cosmetic
- “party_checklist” reworded the description of “venue” cosmetic
- “party_timeline” reworded the description of “event_date” cosmetic
- “party_timeline” reworded the description of “event_type” cosmetic
- “party_timeline” reworded the description of “guests” cosmetic
- 9 Oct 26 +1
- Schema quality: 122 → 96 ▲ functional
- First check of Tool coverage: 100 functional
- Schema quality: excellent → good functional
- 6 Oct 26 +1
- Stability: unverified → 0.07 ▲ functional
- 4 Oct 26 72
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 23 Oct 2026 · Probed https://party-plan.magicteams.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=magicteams.ai | CN=WE1,O=Google Trust Services,C=US | 4 Oct 2026 | 2 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 1badcf7ed3863a070ee2fb8f87723ebd |
| SANs: magicteams.ai, party-plan.magicteams.ai, *.party-plan.magicteams.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of party-plan.magicteams.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| magicteams.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://party-plan.magicteams.ai/mcp | Verified | 200 | |
| http (plaintext) | http://party-plan.magicteams.ai/mcp | HTTPS enforced | 301 | https://party-plan.magicteams.ai/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
headcount_plan Headcount plan ~146
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).
| Name | Type | Req | Description |
|---|---|---|---|
| children_pct | number | – | Percent of attendees who are children, 0-100, default 0 |
| expected_decline_pct | number | – | Percent of invitees expected to decline, 0-100, default 15 |
| invited | integer | yes | People invited, whole number 1-1000, e.g. 40 |
| Name | Type | Req | Description |
|---|---|---|---|
| adults | integer | yes | Expected adult attendees |
| children | integer | yes | Expected child attendees |
| expected_attendees | integer | yes | Expected attendance after declines (rounded up) |
| invited | integer | yes | Number of people invited |
| note | string | yes | Plain-language explanation of the estimate and buffers |
| quantities | object | yes | Shopping quantities including buffers |
No examples provided.
party_budget Party budget ~143
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).
| Name | Type | Req | Description |
|---|---|---|---|
| budget | number | yes | Total party budget in USD, positive, e.g. 600 |
| guests | integer | yes | Number of guests, whole number 1-500, e.g. 30 |
| style | string | – | Spending style that sets the category percentages: 'budget', 'standard' (default) or 'premium' |
| Name | Type | Req | Description |
|---|---|---|---|
| allocation | array | yes | Budget split per category; amounts sum to the budget |
| budget | number | yes | Total budget, rounded to cents |
| currency | string | yes | Currency of all amounts, always USD |
| guests | integer | yes | Guest count used |
| note | string | yes | Plain-language summary of the allocation |
| per_guest_budget | number | yes | Total budget divided by guests, rounded to cents |
No examples provided.
party_checklist Party checklist ~146
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).
| Name | Type | Req | Description |
|---|---|---|---|
| extras | array | – | Optional keywords that add themed items: pool, bbq, costume, outdoor, kids, alcohol, potluck, e.g. ["bbq","kids"] |
| venue | string | yes | 'home' for a party at home, 'venue' for a hired venue or hall |
| Name | Type | Req | Description |
|---|---|---|---|
| checklist | array | yes | Checklist items grouped by area |
| note | string | yes | Summary of venue adjustments and extras applied |
| venue | string | yes | Venue type the checklist was built for |
No examples provided.
party_timeline Party timeline ~171
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).
| Name | Type | Req | Description |
|---|---|---|---|
| event_date | string | yes | Party date YYYY-MM-DD, e.g. 2026-12-20 |
| event_type | string | – | Optional event label added to the T-21 tasks, e.g. 'birthday', 'bbq' or 'kids party' |
| guests | integer | – | Optional guest count 1-1000; adds a cake-sizing task at T-14 |
| Name | Type | Req | Description |
|---|---|---|---|
| event_date | string | yes | Party date YYYY-MM-DD |
| milestones | array | yes | Countdown milestones from T-42 days to the day itself |
| note | string | yes | How to read the milestone dates |
No examples provided.
How do I install the PartyPlan MCP server?
PartyPlan is a hosted endpoint at https://party-plan.magicteams.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · party-plan.magicteams.ai
claude mcp add --transport http everyai-com-party-plan 'https://party-plan.magicteams.ai/mcp'
What is the PartyPlan MCP server?
PartyPlan is an MCP server listed in the public MCP registry as io.github.everyai-com/party-plan. Party budgets, headcount quantities, timelines and checklists. Free. This page covers its hosted endpoint (https://party-plan.magicteams.ai/mcp).
Is the PartyPlan MCP server safe to use?
PartyPlan scores 75 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the PartyPlan MCP server expose?
PartyPlan exposes 4 tools: party_budget, headcount_plan, party_timeline, party_checklist. Their descriptions and schemas cost roughly 606 tokens of context every time the server is loaded.
Does the PartyPlan MCP server require authentication?
No. We connected to PartyPlan without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the PartyPlan MCP server still maintained?
PartyPlan is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.