abm9111/chamber

Catches your AI agent quoting a number or a name that isn't in the note it
cites. When Claude Code (or any MCP host) answers from your notes, it is told
to run each claim through chambercheck first. Real output, trimmed:
2 claim(s): 1 supported · 1 terms absent · 0 nothing to check · 0 not judged
[TERMSABSENT] Q3 revenue was $420k, up 18% on Q2.
the cited text does not contain: 420k
checked: q3-review.md#p0
[SUPPORTED] Enterprise renewals moved to Dana Ortiz in August.
every term Chamber recognises occurs in the cited text
checked: q3-review.md#p0
The note says $240k. The agent wrote $420k. Edit the note afterwards and
the same check judges the new text, and the result adds index is behind this
file, because the index still holds the old copy.
bash
claude mcp add -s user chamber -- npx -y @bu7umaid/chamber mcp --notes ~/Notes
json
"mcpServers": {
"chamber": {
"command": "npx",
"args": ["-y", "@bu7umaid/chamber", "mcp", "--notes", "/absolute/path/to/Notes"]
No model, no account, no network: the check is deterministic string matching
over node:sqlite and files on your disk. It checks numbers, capitalised
names, domains, file names and counts. It does not check meaning, so a negated
or reversed sentence built from the note's own words still passes. See
what a verified citation does and does not prove.
Beyond the check: answers that cite their sources, and a daily job that tells
you when a source changed underneath a conclusion you already trusted.
## Run the check
The npx line above is all most people need. --exclude repeats
after --notes. Config ingest roots and their excludes count too. Two other
ways in:
From a checkout (Node 23.6+). TypeScript runs straight from the repo, with
no build step. try builds a throwaway workspace, runs the real code paths
and deletes it. The published package runs on Node 22 (measured 22.23.1, which
prints Node's experimental-SQLite warning). Node 20.20.2 exits with
ERRUNKNOWNBUILTINMODULE because node:sqlite is absent. Node 23.6
remains the floor for a checkout.
bash
git clone https://github.com/abm9111/chamber.git && cd chamber && npm ci && node --experimental-strip-types src/cli.ts try
If /mcp does not list chambercheck, the host started the server with a
minimal PATH. Take the interpreter from command -v node in your own shell
and point it at the published bin or at a checkout's src/mcpserver.ts. Those
are different files:
bash
# published bin: bin/chamber.js loads dist/. This is not src/mcpserver.ts.
claude mcp add -s user chamber -- "$(command -v node)" /path/to/nodemodules/@bu7umaid/chamber/bin/chamber.js mcp
# checkout only. src/mcpserver.ts is not in the npm install.
claude mcp add -s user chamber -- "$(command -v node)" --experimental-strip-types /path/to/chamber/src/mcpserver.ts
Ingest and chamberask need config. The check also reads config ingest roots
when they are set. See
config: ingest, chamberask, and the check.
## What people actually do
There is no public trail of Chamber users yet. These are the adjacent failures
on X, which are the reason the check exists.
Pointing Claude Code at an Obsidian folder reads files. It does not check the
sentence. Richard Kovacs, 28 Sep 2026: