# WhoIsBringing — Group Event & Potluck Item Coordinator (remote · api.whoisbringing.com)

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

- Trust score: 69/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `api.whoisbringing.com`: 69/100 (this document), [markdown](https://verifymcp.io/servers/com-whoisbringing-whoisbringing-mcp/api.md), [page](https://verifymcp.io/servers/com-whoisbringing-whoisbringing-mcp/api)

## Channel facts

- Endpoint: `https://api.whoisbringing.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `2.0.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 404 tokens (~80/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 98/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 93% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

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

### Claude

```bash
claude mcp add --transport http com-whoisbringing-whoisbringing-mcp 'https://api.whoisbringing.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-whoisbringing-whoisbringing-mcp": {
      "url": "https://api.whoisbringing.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-whoisbringing-whoisbringing-mcp": {
      "type": "http",
      "url": "https://api.whoisbringing.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-whoisbringing-whoisbringing-mcp]
url = "https://api.whoisbringing.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-whoisbringing-whoisbringing-mcp": {
      "type": "remote",
      "url": "https://api.whoisbringing.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-whoisbringing-whoisbringing-mcp --url 'https://api.whoisbringing.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-whoisbringing-whoisbringing-mcp:
    url: "https://api.whoisbringing.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-whoisbringing-whoisbringing-mcp": {
      "Transport": "http",
      "Url": "https://api.whoisbringing.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-whoisbringing-whoisbringing-mcp -t streamable-http -u 'https://api.whoisbringing.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-whoisbringing-whoisbringing-mcp": {
      "type": "http",
      "url": "https://api.whoisbringing.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 69, +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.

### 2026-11-03 (score 68, +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.

### 2026-11-01 (score 67, −6)

- [security regression] 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
- [functional regression] Tool coverage: 100% → 93%
- [functional improvement] Schema quality: fail → pass
- [functional] Schema quality: excellent → good
- [cosmetic] “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

### 2026-10-31 (score 73, +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.

### 2026-10-30 (score 72, +6)

- [security improvement] 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
- [functional regression] Schema quality: pass → fail
- [functional improvement] Tool coverage: 93% → 100%
- [functional improvement] Stability: unverified → 0.03
- [functional] Schema quality: good → excellent
- [cosmetic] “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

### 2026-10-29 (score 66)

First indexed and scored.

## MCP tools (5)

### `create_event_checklist` (~183 tokens)

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.

Input parameters:

- `description` (string): Optional event notes or instructions
- `event_date` (string): Optional date and time (e.g. "2026-09-05T15:00")
- `host_name` (string, required): Host or organizer display name
- `items` (array): List of supply and food items needed
- `location` (string): Optional venue, address, or park landmark
- `template` (string): Preset template category
- `title` (string, required): Event title (e.g. "Grand Saturday Braai & Rugby" or "Family Lake Picnic")

### `get_event_checklist` (~49 tokens)

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

Input parameters:

- `event_id` (string, required): The 8-character event ID or slug

### `claim_checklist_item` (~82 tokens)

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

Input parameters:

- `claimed_by_name` (string, required): Guest nickname or name claiming the item
- `event_id` (string, required): The 8-character event ID
- `item_id` (integer): The checklist item ID
- `item_name` (string): Item name if ID is unknown

### `add_checklist_items` (~46 tokens)

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

Input parameters:

- `event_id` (string, required): The 8-character event ID
- `items` (array, required)

### `suggest_event_template` (~44 tokens)

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

Input parameters:

- `event_type` (string): Type of event

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-whoisbringing-whoisbringing-mcp/api#diagnostics

## Score history

- 2026-11-05: 69
- 2026-11-04: 68
- 2026-11-03: 68
- 2026-11-02: 67
- 2026-11-01: 67
- 2026-10-31: 73
- 2026-10-30: 72
- 2026-10-29: 66

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

## Links

- Remote endpoint: https://api.whoisbringing.com/mcp
- Website: https://whoisbringing.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-whoisbringing-whoisbringing-mcp/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-whoisbringing-whoisbringing-mcp/api.json
- HTML version of this page: https://verifymcp.io/servers/com-whoisbringing-whoisbringing-mcp/api
