json-chamber-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VERIFIEDDR_API_KEY | No | API key to unlock the paid features. | |
| CHAMBER_MASTER_SECRET | Yes | High-entropy secret used to seal and open JSON chambers. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| chamber_statusB | License status: eval remaining hours, purchased, or dead. |
| chamber_infoC | Package info, cloak license ($9/mo · $99/yr), open is keys-only. |
| chamber_cloakC | Seal JSON/text with φ-split + AES-256-GCM. Requires live license. |
| chamber_openB | Open a sealed chamber blob. Keys only — no license, no clock. |
| chamber_hop_gateA | Evaluate Chamber hop-gate (exact-text code). Gate only — does not seal/open/SettleHop. Wire: CUNI ScanChunk + url/etag/hash/agent_id. Result: single code string. PCC ≠ payment. |
| chamber_hop_reject_logC | Live hop-gate reject.log as TSV ISO\tcode\tpreview (Rider SoT). Extra values never rehydrate. |
| benefit_checkC | Entropy + bias gate for $1900 tier. Always available. No TRU8. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
The tools have distinct roles: status/info for licensing, cloak/open for sealing/unsealing, and two separate gate checks (hop_gate vs benefit_check) plus a log. There's minor overlap between status and info (both about license state), but they serve different details. Overall, an agent can tell them apart with clarity.
Most tools follow a 'chamber_' prefix with a noun or verb (status, info, cloak, open, hop_gate, hop_reject_log), but 'benefit_check' breaks the pattern. The verbs are inconsistent (some are nouns like status, others are imperatives like cloak), though the naming is still readable and mostly predictable.
With 7 tools, the server is well-scoped for its purpose: managing sealed JSON chambers, checking license status, and evaluating gates. Each tool has a clear function, and the count is appropriate for the domain without being overwhelming or too sparse.
The core lifecycle is covered: sealing (chamber_cloak), opening (chamber_open), status (chamber_status), and license info (chamber_info). Gate evaluation and logging are also included. A minor gap is no tool to list or manage multiple chambers, but for the given purpose, the surface is largely complete.