F
Warning
22/100
6 days ago

chamber

Cited Q&A and drift detection over your own markdown notes: answers cite exact passages, cited passages are hashed at citation time, and a scheduled verify flags when a source changed under a conclusion already drawn from it. Local-first, zero runtime dependencies (node:sqlite); tools: chamber_ask, chamber_verify, chamber_corpus.

Warning. Serious findings were identified. Review the full report before connecting. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

abm9111

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

Install from

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
🚨
Secret credentials may flow to a network call
1 flow detected: CHAMBER_API_BASE. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 11 credentials: CHAMBER_API_KEY, CHAMBER_API_TOKEN, CHAMBER_MCP_ACCESS_TOKEN, CHAMBER_MCP_CLIENT_SECRET, CHAMBER_TOKEN_KEY, DISCORD_BOT_TOKEN, HF_ACCESS_TOKEN, HF_TOKEN, SLACK_APP_TOKEN, SLACK_BOT_TOKEN, TELEGRAM_BOT_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configCHAMBER_ACTOR
configCHAMBER_ALLOW_HIGH_RISK_TOOLS
configCHAMBER_ALLOW_PLAINTEXT_SECRETS
configCHAMBER_API_BASE
🔐 secretCHAMBER_API_KEYno API key; anything else reads from the environment, never
configCHAMBER_API_MODEL
🔐 secretCHAMBER_API_TOKEN
configCHAMBER_AUTO_PAY_DEBT
configCHAMBER_BIND
configCHAMBER_CHECKPOINT_PUBKEY
configCHAMBER_CORS_ORIGIN
configCHAMBER_DB
configCHAMBER_DISCORD_ALLOWED_USERS
configCHAMBER_DISCORD_APPROVERS
configCHAMBER_DISCORD_FREE_CHANNELS
configCHAMBER_DISCORD_OPS_CHANNEL
configCHAMBER_DISCORD_REACTION_APPROVE
configCHAMBER_EMBEDDER
configCHAMBER_FACULTY_MODE
configCHAMBER_GATEWAY
configCHAMBER_HARNESS
🔐 secretCHAMBER_MCP_ACCESS_TOKEN
configCHAMBER_MCP_ALLOW_CALL
configCHAMBER_MCP_CLIENT_ID
🔐 secretCHAMBER_MCP_CLIENT_SECRET
configCHAMBER_MCP_REDIRECT_URI
configCHAMBER_MCP_SCOPE
configCHAMBER_MCP_SKIP_PIN
configCHAMBER_MODEL
configCHAMBER_OAUTH_ALLOW_HTTP
configCHAMBER_OAUTH_CODE
configCHAMBER_OAUTH_ISS
configCHAMBER_OAUTH_NO_BROWSER
configCHAMBER_OAUTH_REFRESH_MOCK
configCHAMBER_OAUTH_REFRESH_MOCK_SEQUENCE
configCHAMBER_OAUTH_RETRY_DELAY_MS
configCHAMBER_OAUTH_VERIFIER
configCHAMBER_OLLAMA_EMBED_MODEL
configCHAMBER_OLLAMA_URL
configCHAMBER_PILOT
configCHAMBER_PILOT_LOG
configCHAMBER_PORT
configCHAMBER_POSTURE
configCHAMBER_PYTHONe =/path/to/python-with-onnxruntime \
configCHAMBER_SANDBOX_BACKEND
configCHAMBER_SANDBOX_KEEP
configCHAMBER_SANDBOX_REQUIRED
configCHAMBER_SCOPE
configCHAMBER_SESSION
configCHAMBER_SLACK_APPROVERS
configCHAMBER_SLACK_DEBUG
configCHAMBER_SLACK_OPS_CHANNEL
configCHAMBER_SPEND_CAP_USD
configCHAMBER_STRICT_CONTRACT
configCHAMBER_SURFACE_RATE_CAPACITY
configCHAMBER_SURFACE_RATE_REFILL_MS
🔐 secretCHAMBER_TOKEN_KEY
configDISCORD_ALLOWED_USERS
🔐 secretDISCORD_BOT_TOKEN
configDISCORD_CLIENT_ID
configDISCORD_GUILD_ID
🔐 secretHF_ACCESS_TOKEN
🔐 secretHF_TOKEN
configLISTEN_FDS
configLISTEN_PID
🔐 secretSLACK_APP_TOKEN
🔐 secretSLACK_BOT_TOKEN
🔐 secretTELEGRAM_BOT_TOKEN
configTESTING_REMOTELY
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

3/3 tools missing one or more hints — chamber_ask (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); chamber_verify (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); chamber_corpus (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint). OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool test coverage

Only 0/3 tools referenced in tests (0%)

Write tests that reference each tool by name so every tool has at least one test.

Shell command execution

19 child_process/subprocess calls in production code — runs shell commands (src/mcp_client.ts:53, src/mcp_oauth.ts:71, src/mcp_oauth.ts:92)

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

Secrets stay with their owner

1 secret/sensitive value flow into network calls (CHAMBER_API_BASE → dynamic)

Audit where credentials are sent. A NOTION_TOKEN should only reach api.notion.com — never a third-party host.

Secrets never reach shell commands

2 secret values passed to shell commands — possible command injection

Never pass secrets through shell commands. Use library APIs that accept credentials as arguments.

Secrets not logged

4 secret values sent to console.log

Redact or omit secret values from log output.

Domain consistency

npm scope @bu7umaid doesn't match GitHub owner abm9111

Use the same org name across GitHub, npm, and your homepage so users can verify the publisher.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 8 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/abm9111-chamber-1b5z1e?variant=verified)](https://m8ven.ai/mcp/abm9111-chamber-1b5z1e)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: e307fe328c874ee5a5f55ceee9990282baed35a9
code hash: 5d436830d85126f9a615c87617475933839a17729dcdfc47d435baa22e9fe14f
verified: 8/13/2026, 7:52:25 AM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client