# io.github.nika110/openhuddle (npm · openhuddle)

Multiplayer mode for AI coding agents: team huddles, master prompt, task board, file claims.

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

## Components

- npm · `openhuddle`: 88/100 (this document), [markdown](https://verifymcp.io/servers/nika110-openhuddle/openhuddle.md), [page](https://verifymcp.io/servers/nika110-openhuddle/openhuddle)

## Channel facts

- Registry: `npm`
- Package: `openhuddle`
- Version: `0.4.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to nika110/openhuddle).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 17 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 64/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2066 tokens (~206/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 60/100
  - Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% 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 10 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 11 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 io.github.nika110/openhuddle MCP server?

io.github.nika110/openhuddle runs locally as an npm package, launched with npx -y openhuddle. 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 nika110-openhuddle -- npx -y openhuddle
```

### Cursor

```json
{
  "mcpServers": {
    "nika110-openhuddle": {
      "command": "npx",
      "args": [
        "-y",
        "openhuddle"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "nika110-openhuddle": {
      "command": "npx",
      "args": [
        "-y",
        "openhuddle"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add nika110-openhuddle -- npx -y openhuddle
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "nika110-openhuddle": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "openhuddle"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add nika110-openhuddle --command npx --arg -y --arg openhuddle
```

### Hermes

```yaml
mcp_servers:
  nika110-openhuddle:
    command: "npx"
    args: ["-y", "openhuddle"]
```

### Netclaw

```json
{
  "McpServers": {
    "nika110-openhuddle": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "openhuddle"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add nika110-openhuddle -t stdio -c npx -a -y openhuddle
```

### Other

```json
{
  "mcpServers": {
    "nika110-openhuddle": {
      "command": "npx",
      "args": [
        "-y",
        "openhuddle"
      ]
    }
  }
}
```

## 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-04 (score 88, +1)

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

### 2026-11-02 (score 87, +1)

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

### 2026-10-31 (score 86, +1)

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

### 2026-10-29 (score 85, +1)

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

### 2026-10-27 (score 84, +1)

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

### 2026-10-25 (score 83, +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-10-23 (score 82, +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-10-20 (score 81, +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.

## MCP tools (10)

### `team_sync` (~61 tokens)

See what your team is doing right now: who is online and on which task, the master prompt's state, your tasks, questions waiting for you, and what changed since you last looked. Call it at the start of a session and before starting new work.

### `team_post` (~86 tokens)

Tell your team something in one or two sentences: a progress update (what you finished, what changed for others) or a decision and why. Never include secrets.

Input parameters:

- `kind` (string, required): "update" for progress, "decision" for a choice the team should know about.
- `text` (string, required): The message.
- `why` (string): For decisions: the reason.

### `team_ask` (~88 tokens)

Ask a teammate's agent a question: what they are doing, whether you may change a file they hold, why they chose something. You get their live status at once; if their agent is active its answer comes back within about 20 seconds, otherwise it arrives later in your team news.

Input parameters:

- `question` (string, required): Your question.
- `to` (string, required): The teammate's name.

### `team_reply` (~67 tokens)

Answer a question a teammate's agent asked you (ids like Q3). Answer truthfully from what you actually did and know; say so when you don't know.

Input parameters:

- `answer` (string, required): Your answer.
- `ask_id` (string, required): The question id, e.g. Q3.

### `huddle` (~374 tokens)

Think together like a real dev team. start: open a huddle, either brainstorm (an open question), design (your proposed approach, for pushback), review (ask teammates to look at a branch, commit or task) or standup (everyone posts done, next, blockers); optionally only with some people. list: open and recently closed huddles. get: read the whole discussion. idea: add an idea. comment: discuss, optionally on one idea. react: back (up) or push back on (down) a teammate's idea, with a reason. close: record what the team decided (whoever started it, or the team owner).

Input parameters:

- `action` (string, required): What to do.
- `context` (string): start: background the team needs: constraints, what you tried, the branch or commit to review.
- `decision` (string): close: what the team settled on.
- `id` (string): Huddle id, e.g. H2 (all actions except start and list).
- `idea` (number): react: the idea number; comment: optional idea number the comment is about.
- `kind` (string): start: what kind of huddle.
- `note` (string): react: your reason.
- `people` (array): start: teammates to huddle with. Leave out for the whole team.
- `proposal` (string): start: your proposed approach (required for design; becomes idea #1).
- `text` (string): idea/comment: what you want to say.
- `topic` (string): start: the question or subject, in one line.
- `vote` (string): react: up to back the idea, down to push back.
- `why` (string): close: the reason, in a sentence or two.

### `master_prompt` (~177 tokens)

The team's shared master prompt: one description of what you are building, co-written by everyone. get: read it. edit: replace or append one section (Idea, Who it is for, Must-haves, Not doing, Tech stack, Look and feel, Done means, Conventions; a new title adds a section). submit: start the team vote. vote: approve or reject the version being voted on. Only edit or vote when your user asks.

Input parameters:

- `action` (string, required): What to do.
- `approve` (boolean): true to approve, false to reject (vote).
- `comment` (string): Optional note with your vote.
- `mode` (string): replace (default) or append (edit).
- `section` (string): Section title (edit).
- `text` (string): New section text (edit).

### `plan` (~135 tokens)

Turn the locked master prompt into tasks (usually the lead's job) or add tasks later. Contracts first: the first task is always the skeleton (repo setup, shared types and API contracts, database schema, lint/format config) and the other tasks depend on it. Give every task its own folder area and explicit dependencies. create: save a plan (replace=true drops tasks nobody started). add: append tasks. list: show the board.

Input parameters:

- `action` (string, required): What to do.
- `replace` (boolean): create only: remove tasks that nobody has started.
- `tasks` (array): Tasks to create or add.

### `task` (~156 tokens)

Work the task board. list: all tasks. take: claim an open task. accept/decline: answer a task proposed to you. start: begin (only when its dependencies are done). update: post a progress note. done: finish, with a one-line note on what changed for others. release: give it back. assign: give a task to a teammate.

Input parameters:

- `action` (string, required): What to do.
- `assignee` (string): Teammate's name (assign).
- `branch` (string): Git branch (start/done). Defaults to your current branch.
- `key` (string): Task key, e.g. T3.
- `note` (string): Progress note (update/done).

### `claim` (~104 tokens)

Reserve files you are about to change so teammates' agents don't edit them at the same time (files you edit are claimed automatically for 30 minutes). check: see whether files are held by someone or sit in a teammate's task area. release: free files you are done with.

Input parameters:

- `action` (string, required): What to do.
- `paths` (array, required): File paths (relative to the repo or absolute).
- `task_key` (string): Optional task the claim belongs to.

### `team_settings` (~308 tokens)

Read or change how the team works, when your user asks. Team-wide rules can only be changed by the team owner: assign_mode (self: people pick tasks, agent: the lead assigns, hybrid: the lead proposes and each person accepts), master_prompt_approval (all, majority or owner), claim_mode (ask: pause and ask the user before editing a file a teammate holds, block: refuse, warn: only tell) and claim_ttl_min (how long claims last). Anyone can set lead (who the lead, the main agent, is) and my_strengths (what you are good at, used for assignments). auto_respond is personal: whether your agent answers waiting questions and huddles before it finishes a turn.

Input parameters:

- `action` (string, required): What to do.
- `assign_mode` (string): How tasks get assigned.
- `auto_respond` (boolean): Yours only (Claude Code): before finishing a turn, answer teammates' questions and huddles waiting for you. On by default.
- `claim_mode` (string): What happens when you try to edit a file a teammate holds.
- `claim_ttl_min` (number): Minutes a claim lasts without activity.
- `lead` (string): Teammate's name to make lead (main agent).
- `master_prompt_approval` (string): Who must approve the master prompt.
- `my_strengths` (string): What you are good at, e.g. "frontend, design".

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/nika110-openhuddle/openhuddle#diagnostics

## Score history

- 2026-11-05: 88
- 2026-11-04: 88
- 2026-11-03: 87
- 2026-11-02: 87
- 2026-11-01: 86
- 2026-10-31: 86
- 2026-10-30: 85
- 2026-10-29: 85
- 2026-10-28: 84
- 2026-10-27: 84
- 2026-10-26: 83
- 2026-10-25: 83
- 2026-10-24: 82
- 2026-10-23: 82
- 2026-10-22: 81
- 2026-10-21: 81
- 2026-10-20: 81
- 2026-10-19: 80
- 2026-10-18: 68

## Common questions

### What is the io.github.nika110/openhuddle MCP server?

io.github.nika110/openhuddle is an MCP server listed in the public MCP registry as io.github.nika110/openhuddle. Multiplayer mode for AI coding agents: team huddles, master prompt, task board, file claims. This page covers its npm package (openhuddle).

### Is the io.github.nika110/openhuddle MCP server safe to use?

io.github.nika110/openhuddle scores 88 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 io.github.nika110/openhuddle MCP server expose?

io.github.nika110/openhuddle exposes 10 tools: team_sync, team_post, team_ask, team_reply, huddle, and 5 more. Their descriptions and schemas cost roughly 1,556 tokens of context every time the server is loaded.

### Is the io.github.nika110/openhuddle MCP server still maintained?

io.github.nika110/openhuddle 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.

### What licence is the io.github.nika110/openhuddle MCP server under?

io.github.nika110/openhuddle declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/openhuddle
- Socket report: https://socket.dev/npm/package/openhuddle
- Repository: https://github.com/nika110/openhuddle
- Changelog RSS feed: https://verifymcp.io/servers/nika110-openhuddle/openhuddle.xml
- Changelog JSON feed: https://verifymcp.io/servers/nika110-openhuddle/openhuddle.json
- HTML version of this page: https://verifymcp.io/servers/nika110-openhuddle/openhuddle