This MCP server implements a “two-key” JSON seal/open workflow. It supports sealing and opening operations based on provided keys. According to the description, it also depends on a live license for “Cloak,” while the “Open” path is described as keys-only.
🛠️ Key Features
Two-key JSON seal/open mechanism
“Cloak” requires a live license
“Open” is keys-only
🚀 Use Cases
Sealing JSON data using two keys
Opening/unsealing JSON using keys only
Scenarios where the cloak step must be licensed
⚡ Developer Benefits
Clear separation between “Cloak” (license-dependent) and “Open” (keys-only)
Key-based operation model for JSON sealing/unsealing
⚠️ Limitations
“Cloak needs a live license”
“Open is keys-only,” implying limited behavior beyond key-based opening
Live reject.log is TSV ISO\tcode\tpreview (mirrors agent-rider-c/reject.log); preview truncates ~120 and flattens newlines. Extra-key values never rehydrate as next machine input.
PCC ≠ payment — PCC is the compression/storefront face; hop-gate codes are admission control, not billing.