Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

WhoIsBringing — Group Event & Potluck Item Coordinator

REMOTE · API.WHOISBRINGING.COM

Organize group events, braais, and potlucks with live item checklists and guest coordination.

+3 this week 69 Trust /100

Last scanned (10 hours ago)

Scores higher than 54% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Productivity and Notes

Trust breakdown (7 categories)

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 Security63
Transport & Reachability100
Schema Quality & AI Usability70
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 404 tokens (~80/item across 5 items; 5 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 93% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 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 supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

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.

  • 5 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 3 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Nov 26 −6
    • Authorization: partial → unverified ▼ security
    • Tool “add_checklist_items” rewrote its description, which is the text the model reads security
    • Tool “claim_checklist_item” rewrote its description, which is the text the model reads security
    • Tool “create_event_checklist” rewrote its description, which is the text the model reads security
    • Tool “get_event_checklist” rewrote its description, which is the text the model reads security
    • Tool “suggest_event_template” rewrote its description, which is the text the model reads security
    • Tool coverage: 100% → 93% ▼ functional
    • Schema quality: fail → pass ▲ functional
    • Schema quality: excellent → good functional
    • “add_checklist_items” reworded the description of “event_id” cosmetic
    • “add_checklist_items” reworded the description of “items” cosmetic
    • “claim_checklist_item” reworded the description of “claimed_by_name” cosmetic
    • “claim_checklist_item” reworded the description of “event_id” cosmetic
    • “claim_checklist_item” reworded the description of “item_id” cosmetic
    • “claim_checklist_item” reworded the description of “item_name” cosmetic
    • “create_event_checklist” reworded the description of “host_name” cosmetic
    • “create_event_checklist” reworded the description of “items” cosmetic
    • “create_event_checklist” reworded the description of “template” cosmetic
    • “create_event_checklist” reworded the description of “title” cosmetic
    • “get_event_checklist” reworded the description of “event_id” cosmetic
    • “suggest_event_template” reworded the description of “event_type” cosmetic
    • Tool “add_checklist_items” changed its title: Add Checklist Items cosmetic
    • Tool “claim_checklist_item” changed its title: Claim Checklist Item cosmetic
    • Tool “create_event_checklist” changed its title: Create Event Checklist cosmetic
    • Tool “get_event_checklist” changed its title: Get Event Checklist cosmetic
    • Tool “suggest_event_template” changed its title: Suggest Event Template cosmetic
  • 31 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 30 Oct 26 +6
    • Authorization: unverified → partial ▲ security
    • Tool “add_checklist_items” rewrote its description, which is the text the model reads security
    • Tool “claim_checklist_item” rewrote its description, which is the text the model reads security
    • Tool “create_event_checklist” rewrote its description, which is the text the model reads security
    • Tool “get_event_checklist” rewrote its description, which is the text the model reads security
    • Tool “suggest_event_template” rewrote its description, which is the text the model reads security
    • Schema quality: pass → fail ▼ functional
    • Tool coverage: 93% → 100% ▲ functional
    • Stability: unverified → 0.03 ▲ functional
    • Schema quality: good → excellent functional
    • “add_checklist_items” reworded the description of “event_id” cosmetic
    • “add_checklist_items” reworded the description of “items” cosmetic
    • “claim_checklist_item” reworded the description of “claimed_by_name” cosmetic
    • “claim_checklist_item” reworded the description of “event_id” cosmetic
    • “claim_checklist_item” reworded the description of “item_id” cosmetic
    • “claim_checklist_item” reworded the description of “item_name” cosmetic
    • “create_event_checklist” reworded the description of “host_name” cosmetic
    • “create_event_checklist” reworded the description of “items” cosmetic
    • “create_event_checklist” reworded the description of “template” cosmetic
    • “create_event_checklist” reworded the description of “title” cosmetic
    • “get_event_checklist” reworded the description of “event_id” cosmetic
    • “suggest_event_template” reworded the description of “event_type” cosmetic
    • Tool “add_checklist_items” changed its title: Add Checklist Items cosmetic
    • Tool “claim_checklist_item” changed its title: Claim Checklist Item cosmetic
    • Tool “create_event_checklist” changed its title: Create Event Checklist cosmetic
    • Tool “get_event_checklist” changed its title: Get Event Checklist cosmetic
    • Tool “suggest_event_template” changed its title: Suggest Event Template cosmetic
  • 29 Oct 26 66

    First indexed and scored.

Diagnostics

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 5 Nov 2026 · Probed https://api.whoisbringing.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=whoisbringing.com CN=WE1,O=Google Trust Services,C=US 3 Nov 2026 1 Feb 2027 ECDSA 256 ECDSA-SHA256 aae456c10aac7e10136b2cade5fa276b
SANs: whoisbringing.com, api.whoisbringing.com, *.api.whoisbringing.com
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 api.whoisbringing.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
whoisbringing.com. 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
Header Value
strict-transport-security max-age=0; includeSubDomains; preload
x-content-type-options nosniff

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.whoisbringing.com/mcp Verified 200
http (plaintext) http://api.whoisbringing.com/mcp HTTPS enforced 301 https://api.whoisbringing.com/mcp
MCP tools · 5 exposed · ~404 tokens

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 →

Tool Tokens
add_checklist_items ~46

Append additional food, drinks, or supply items to an existing event checklist.

NameTypeReqDescription
event_idstringyesThe 8-character event ID
itemsarrayyes–

No output schema declared.

No examples provided.

claim_checklist_item ~82

Claim an item on the event checklist on behalf of a guest/attendee.

NameTypeReqDescription
claimed_by_namestringyesGuest nickname or name claiming the item
event_idstringyesThe 8-character event ID
item_idinteger–The checklist item ID
item_namestring–Item name if ID is unknown

No output schema declared.

No examples provided.

create_event_checklist ~183

Agentic tool to create a new collaborative event checklist (e.g. for BBQs, camping, picnics, potlucks, dinners) with categorized items, required quantities, date, location, and host name. Returns live shareable URL and WhatsApp copy.

NameTypeReqDescription
descriptionstring–Optional event notes or instructions
event_datestring–Optional date and time (e.g. "2026-09-05T15:00")
host_namestringyesHost or organizer display name
itemsarray–List of supply and food items needed
locationstring–Optional venue, address, or park landmark
templatestring–Preset template category
titlestringyesEvent title (e.g. "Grand Saturday Braai & Rugby" or "Family Lake Picnic")

No output schema declared.

No examples provided.

get_event_checklist ~49

Inspect the current status of an event checklist, including items claimed vs unclaimed, percentage completed, and attendee allocations.

NameTypeReqDescription
event_idstringyesThe 8-character event ID or slug

No output schema declared.

No examples provided.

suggest_event_template ~44

Returns curated category and item templates for specific event types (e.g. BBQ, Picnic, Camping, Potluck Dinner).

NameTypeReqDescription
event_typestring–Type of event

No output schema declared.

No examples provided.

Install

How do I install the WhoIsBringing — Group Event & Potluck Item Coordinator MCP server?

WhoIsBringing — Group Event & Potluck Item Coordinator is a hosted endpoint at https://api.whoisbringing.com/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 · api.whoisbringing.com

# add to Claude Code
claude mcp add --transport http com-whoisbringing-whoisbringing-mcp 'https://api.whoisbringing.com/mcp'
Common questions

What is the WhoIsBringing — Group Event & Potluck Item Coordinator MCP server?

WhoIsBringing — Group Event & Potluck Item Coordinator is an MCP server listed in the public MCP registry as com.whoisbringing/whoisbringing-mcp. Organize group events, braais, and potlucks with live item checklists and guest coordination. This page covers its hosted endpoint (https://api.whoisbringing.com/mcp).

Is the WhoIsBringing — Group Event & Potluck Item Coordinator MCP server safe to use?

WhoIsBringing — Group Event & Potluck Item Coordinator scores 69 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 WhoIsBringing — Group Event & Potluck Item Coordinator MCP server expose?

WhoIsBringing — Group Event & Potluck Item Coordinator exposes 5 tools: create_event_checklist, get_event_checklist, claim_checklist_item, add_checklist_items, suggest_event_template. Their descriptions and schemas cost roughly 404 tokens of context every time the server is loaded.

Does the WhoIsBringing — Group Event & Potluck Item Coordinator MCP server require authentication?

No. We connected to WhoIsBringing — Group Event & Potluck Item Coordinator without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the WhoIsBringing — Group Event & Potluck Item Coordinator MCP server still maintained?

WhoIsBringing — Group Event & Potluck Item Coordinator is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.