Zero‑Exposure Slack Sender (MGC Secure Edition)
Description
A local execution vault for AI Agents: providing encrypted key authorization, encrypted task‑chain execution, and controlled external execution permissions. It preserves the high‑efficiency execution capability of AI while protecting user data and cognitive assets — putting a…
About
A local execution vault for AI Agents: providing encrypted key authorization, encrypted task‑chain execution, and controlled external execution permissions. It preserves the high‑efficiency execution capability of AI while protecting user data and cognitive assets — putting a real harness on AI (AI Harness).
Details
- Author
- zkeviny
- Downloads
- 389
- Categories
- Communication, Developer Tools, AI, Security, Automation, Other
Jump to
- Sealed script execution (encrypted, decrypted at runtime)
- Protected subprocess execution in a controlled sandbox
- Encrypted local storage with device-level encryption
- Capability sandbox hides underlying logic from AI
- Three interaction interfaces: WebUI, API, MCP
- Serves as a trusted execution boundary for agents
Install via pip with the command pip install mgc-blackbox. For detailed installation and usage instructions, refer to the full documentation at the provided GitHub repository.
MirginCipher Blackbox (MGC)— Encrypted AI Agent Execution Layer
A secure local execution layer for AI agents — encrypted storage, sealed scripts, zero plaintext leakage.
Protect API keys, credentials, and scripts from AI agents with AES‑256 + RSA hybrid encryption and a Cython‑compiled secure core.
📌Roadmap:MGC Blackbox — 2026 Development Plan
MirginCipher Blackbox (MGC) is aLocal Encrypted Execution Layerdesigned to protect sensitive human intent and enablesecure, deterministic AI execution.
It provides a trusted device‑level encrypted boundary for agents —MGC is not an agent itself.
- Sensitive data never leaves the device
- AI agents cannot access plaintext
- Scripts execute inside a sealed, encrypted environment
- Cross‑node execution is possible without exposing code
-
🔐End‑to‑End Encrypted Storage
AES‑256 encrypted vault for API keys, credentials, configs — never exposed to AI agents or external systems.
🧱Local‑First Security Boundary
All execution and decryption happen on‑device. No cloud dependency, no plaintext leakage, no telemetry.
🧩Sealed Script Execution (Unique)
Convert scripts into unreadable execution capsules.
Only trusted nodes can decrypt & run them — even the sender cannot read sealed scripts.
⚡Deterministic Local Execution
Stable, reproducible behavior across macOS / Linux / Windows with a Cython‑compiled secure core.
🛠️Native MCP / Skill Integration
Exposes mgc_save / mgc_get / mgc_list / mgc_seal / mgc_open_webui as standard MCP tools.
Works out‑of‑the‑box with Copilot, Claude, Trae, IDE Agents.
🔄Zero Integration Cost
Any MCP‑compatible agent can immediately use MGC as its secure execution backend — no SDK, no custom code.
🛡️Designed for AI Agent Security
Protects human intent, prevents agent overreach, and enforces strict execution boundaries.
1. Protect API Keys & Credentials from AI Agents
Store secrets encrypted. Agents can use them, but never see plaintext.
Run Python / Shell / Node scripts locally without exposing sensitive data to AI logs or cloud systems.
Share scripts with collaborators or deviceswithout exposing source code— they can execute but cannot read.
Send sealed scripts to trusted remote nodes:
- Sender cannot read the sealed content
- Recipient cannot read the sealed content
- Only the target node can decrypt and execute
5. Local‑First AI Agent Security Boundary
Provides a local security layer for Copilot / Claude / Trae / IDE Agents.
Enables financial automation, personal data processing, and enterprise internal workflows with privacy protection.
MGC Blackbox provides atrusted, encrypted execution boundaryfor different roles and environments.
Detailed scenario documents:
-
🔐Sensitive Credentials Authorization
docs/Sensitive_Credentials_Authorization.md
🧠Encrypted Cognitive Script Execution
docs/Encrypted_Cognitive_Script_Execution.md
🌐Cross‑Node Execution Grant (Encrypted Capability Sharing)
[](https://github.com/zkeviny/MGC-Blackbox/blob/HEAD/docs/Cross%E2%80%91Node_Execution_Grant%20(Encrypted_Capability_Sharing).md)<<<docs/Cross‑Node_Execution_Grant%20(Encrypted_Capability_Sharing).md
MGC uses ahybrid cryptographic design:
- AES‑256‑GCM— bulk data encryption
- RSA‑2048/4096— key encapsulation & node authorization
- Improve AES & RSA performance
- Reduce Python overhead
- Provide a sealed, tamper‑resistant execution boundary
- Maintain deterministic behavior across nodes
- Local encrypted storage
- Encrypted execution
- Store‑once authorization
- Environment migration
- Cross‑agent availability
- Cross‑platform support
- No delete function (manual DB deletion only)
- Script sealing for cross‑node execution
from mgc import save save("openai_key", "sk-xxxx")
Scripts run inside MGC's encrypted boundary.
from mgc import save, get save("openai_key", "sk-xxxx") print(get("openai_key"))
MGC exposes a local MCP tools interface:
- mgc_save
- mgc_get
- mgc_list
- mgc_seal
- mgc_open_webui
Compatible with Copilot, Claude, Trae, IDE Agents.
Agents can store secrets, retrieve encrypted items, execute scripts, and seal scripts.
External scripts can fetch encrypted items at runtime.
- All data remains local
- No cloud upload
- No plaintext logging
- Deterministic execution
- User‑controlled authorization
Integration into any third‑party products or AI agents is free,
but requires official authorization to ensure ecosystem integrity.
Contact:mirgincipher@outlook.comzkeviny@icloud.com
© 2026 MirginCipher Team. All rights reserved.
This is a web browser that enables your coding agent, such as Claude Code, to visit websites on your behalf and assist you in identifying bugs or creating UI test cases.
Remote MCP server (Streamable HTTP) at https://mcp.agenticrail.nz/ — deterministic step-order enforcement for AI agents. evaluate_step returns ALLOW or DENY before a step runs; verify_receipt proves a sequence's Ed25519-signed, hash-chained receipt chain is intact. No auth required: omit the bearer token and calls run on the public demo key. That first clause matters — the form has no "remote/hosted" field, and putting the endpoint in the description is the convention on that list ("Fully REMOTE! Just use…"). The rest mirrors your own server card verbatim, so the listing and the card can't drift.
AMS – Deterministic Agent Pipeline with A2A‑style Orchestration and Cryptographic Audit
What Shopify did for ecommerce, Chipp does for AI agents. Build, deploy, and monetize AI agents for your business — no engineering team required.
CodeVF MCP lets AI hand off problems to real engineers instantly, so your workflows don’t stall when models hit their limits.
Require a named human's offline-verifiable approval before an AI agent takes an irreversible action — payment release, record change, deploy. Two-person rule, Ed25519 Trust Receipts, IETF-drafted, Apache-2.0.
Client implementation for Mastra, providing seamless integration with MCP-compatible AI models and tools.
Agent-native developer Q&A API with MCP + A2A endpoints for citations, job pickup, and answer submission.
On-demand access to 150+ specialist AI agent templates — search, browse, and spawn agents. 150x reduction in context usage vs loading agents locally.
AgentChatBus is a persistent AI communication bus that lets multiple independent AI Agents chat, collaborate, and delegate tasks — across terminals, across IDEs, and across frameworks.
An AI Agent with optional Human-in-the-Loop Safety and Model Context Protocol (MCP) integration.
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.





