_ registry / mcp streamable-http · checked 6h ago

party-plan

https://party-plan.magicteams.ai

Registry code: e24b2b7c8029537c

api record

PartyPlan allocates a party budget across categories, turns an invite list into expected attendance and shopping quantities, builds a dated countdown timeline, and prepares a venue-aware checklist for home or venue parties. All maths only; nothing stored.

endpoint
https://party-plan.magicteams.ai/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is party-plan live?
Yes — it answered the hub's last check (checked 6h ago). It answered 100% of checks over the last 30 days.
Is party-plan free to use?
Yes — the hub reached it with no key and no payment.
What tools does party-plan have?
4 tools: party_checklist, party_timeline, headcount_plan, party_budget.
Is party-plan safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
113ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 329 checks · signed record
  • down → live
  • unknown → live
_ what it is for
used for
  • allocate a party budget
  • estimate party attendance and quantities
  • build party countdown timeline
  • build party checklist
takes → gives
data → data
tools
4 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 4 tools
4 never probed 0 of 4 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • party_checklist reads unknown 15h ago

    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).

    mcp-tool

    {
      "type": "object",
      "required": [
        "venue"
      ],
      "properties": {
        "venue": {
          "enum": [
            "home",
            "venue"
          ],
          "type": "string",
          "description": "'home' for a party at home, 'venue' for a hired venue or hall"
        },
        "extras": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Optional keywords that add themed items: pool, bbq, costume, outdoor, kids, alcohol, potluck, e.g. [\"bbq\",\"kids\"]"
        }
      }
    }
    arguments 23 lines
  • party_timeline reads unknown 24h ago

    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).

    mcp-tool

    {
      "type": "object",
      "required": [
        "event_date"
      ],
      "properties": {
        "guests": {
          "type": "integer",
          "maximum": 1000,
          "minimum": 1,
          "description": "Optional guest count 1-1000; adds a cake-sizing task at T-14"
        },
        "event_date": {
          "type": "string",
          "description": "Party date YYYY-MM-DD, e.g. 2026-12-20"
        },
        "event_type": {
          "type": "string",
          "description": "Optional event label added to the T-21 tasks, e.g. 'birthday', 'bbq' or 'kids party'"
        }
      }
    }
    arguments 22 lines
  • headcount_plan reads unknown 15h ago

    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).

    mcp-tool

    {
      "type": "object",
      "required": [
        "invited"
      ],
      "properties": {
        "invited": {
          "type": "integer",
          "maximum": 1000,
          "minimum": 1,
          "description": "People invited, whole number 1-1000, e.g. 40"
        },
        "children_pct": {
          "type": "number",
          "maximum": 100,
          "minimum": 0,
          "description": "Percent of attendees who are children, 0-100, default 0"
        },
        "expected_decline_pct": {
          "type": "number",
          "maximum": 100,
          "minimum": 0,
          "description": "Percent of invitees expected to decline, 0-100, default 15"
        }
      }
    }
    arguments 26 lines
  • party_budget reads unknown 15h ago

    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).

    mcp-tool

    {
      "type": "object",
      "required": [
        "budget",
        "guests"
      ],
      "properties": {
        "style": {
          "enum": [
            "budget",
            "standard",
            "premium"
          ],
          "type": "string",
          "description": "Spending style that sets the category percentages: 'budget', 'standard' (default) or 'premium'"
        },
        "budget": {
          "type": "number",
          "description": "Total party budget in USD, positive, e.g. 600"
        },
        "guests": {
          "type": "integer",
          "maximum": 500,
          "minimum": 1,
          "description": "Number of guests, whole number 1-500, e.g. 30"
        }
      }
    }
    arguments 28 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id e24b2b7c8029537c.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/e24b2b7c8029537c/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/e24b2b7c8029537c/badge.svg)](https://brick.blue/agent/e24b2b7c8029537c?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
80%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

_ also on magicteams.ai 14 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.

6 more sit on this domain. All of them.