CHAP Coordinator
io.github.BrightbeamAI/chap
About CHAP Coordinator
CHAP Coordinator is an MCP server published by the GitHub account BrightbeamAI. Auditable records of human decisions over AI agent work. Approvals, edits, overrides, escalations.
It runs on your own machine: your AI client starts it from the npm package @brightbeamai/chap-coordinator-mcp at version 0.3.3.
It asks for no keys or passwords.
Version 0.3.3 was published on 20 October 2026, and the source code is public, so you can read it before installing.
Written from the registry entry. 9 automated checks on the registry entry and the package code: 7 pass, 0 warn, 0 fail, 2 info. How we check.
What it asks for
| Variable | Required | Secret | Description |
|---|---|---|---|
CHAP_DB_PATH | No | No | Path to a SQLite file. Without it the coordinator runs in memory and workspaces are lost when the client restarts. |
CHAP_PROFILES | No | No | Comma-separated CHAP profiles enabled on new workspaces. Defaults to Core plus review, whisper, deliberation, handoff, control, routing, modes and audit-scitt. |
Checks
| Check | Result | Detail |
|---|---|---|
| Source repository linked | Pass | https://github.com/BrightbeamAI/chap |
| Version pinned | Pass | Every package has an explicit version |
| Secrets requested | Info | Asks for no secrets |
| Known package registry | Pass | All packages come from npm, PyPI, OCI, NuGet or MCPB |
| Namespace ownership | Info | Name verified via GitHub account BrightbeamAI |
| Registry text aimed at the AI | Pass | Description and settings contain no hidden characters or instructions to the AI |
| Install scripts | Pass | @brightbeamai/chap-coordinator-mcp@0.3.3 runs nothing at install |
| Code red flags | Pass | Read 18 files in @brightbeamai/chap-coordinator-mcp@0.3.3: no obfuscation, encoded execution, credential reads or data-collection endpoints found |
| Text aimed at the AI | Pass | No hidden characters or instructions to the AI in 18 files, including comments and the README |
Popularity & health: 79 / 100
Worked out from public numbers and our own checks, not from user reviews or ratings. It says how used and how looked-after a server is, not whether it is safe.
14 forks, 125 merged pull requests. Sources: GitHub, npm, PyPI (pypistats.org) and Hacker News (Algolia), fetched 2026-10-31.
What people say
3 Hacker News threads linking to the source code. We link to them and copy nothing.
- Collaborative Human Agent Protocol (CHAP) 26 points, 12 comments, 2026-08-19
- How do you audit what your autonomous agents did? 2 points, 0 comments, 2026-07-15
- Ask HN: How should human overrides of AI agent outputs be recorded? 1 points, 0 comments, 2026-06-24
Look further: search Reddit, search Hacker News, read its GitHub issues. These are not reviews we checked.
Facts
| Registry name | io.github.BrightbeamAI/chap |
|---|---|
| Publisher | GitHub account BrightbeamAI |
| How the name is verified | Name verified via GitHub account BrightbeamAI. The registry ties the name prefix to that account or domain; it does not check the code. |
| Type | Local: runs on your machine from a package |
| Packages | npm @brightbeamai/chap-coordinator-mcp 0.3.3 (stdio) |
| Version | 0.3.3 |
| Published | |
| Last updated | |
| Source repository | https://github.com/BrightbeamAI/chap |
| Website | https://github.com/BrightbeamAI/chap |
| Category | Agent safety & governance (assigned by keyword rule, not by hand) |
Related servers in Agent safety & governance
- Guardrail MCP4/4Deterministic preflight checks for credentials, fund transfers,…
- DarkMatter7/7Tamper-evident records of AI agent decisions. Verify offline, or…
- Agent Handoff MCP7/7Bounded, auditable handoffs between AI agents through a local MCP…
- Code Relay7/7Branch-scoped runbooks, remote checkpoints, and auditable…
- quantity-takeoff4/4Auditable construction takeoffs with locked waste and conservative…
- Kumbuka3/3Governed, auditable knowledge your team curates for its AI…