abracadabraOperate the abracadabra local secrets vault (abra CLI, abra serve, abra MCP) only when the user names abracadabra or abra, the abracadabra MCP is registered, or ABRA_KEY is already set for this project. Covers discovering key names, reading secrets the human has scoped to this agent (issued abra key or Touch ID grant), key issue/scope/revoke, health checks, keygen/connectors, USB/LAN sync, cartridge checkpoints, and treasury USDC payments (Touch ID). Do not use for generic env var, API token, wallet, or SSH key questions, or for other vaults or .env files. Never print secret values in chat.
Install via ClawdBot CLI:
clawdbot install userdefault13/abracadabraGrade Limited — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Sends data to undocumented external endpoint (potential exfiltration)
POST → http://127.0.0.1:7331/secretCalls external URL not in known-safe list
http://127.0.0.1:7331/health`Audited Oct 7, 2026 · audit v1.0
Generated Oct 9, 2026
A backend engineering team runs automated deploys on a shared build machine where secrets must never appear in logs or config files. Their pipeline pulls scoped abra keys at runtime, injects allowlisted env vars into the build process, and lets them die with the container. Touch ID happens once at key issuance, keeping unattended runs hands-free.
A solo contractor juggles API keys for five concurrent client codebases and constantly risks leaking one client's credentials into another's repo. Using project-scoped abra keys, each codebase can only read its own key names declared in an allowlist. Chat never sees a value, only confirmations that a given key name was loaded.
An interactive developer works in Cursor or Claude with the abracadabra MCP registered, letting the assistant fetch secrets only when a task genuinely needs them. Each get_secrets call is gated by a short TTL approval, so the agent can't speculatively scrape the vault. If a key is out of scope or revoked, the assistant halts and tells the human to re-scope rather than improvising.
A browser-based dApp backend needs an RPC provider key to submit transactions and occasionally pays USDC from a treasury address. An HTTP session with a short TTL handles multi-step calls, while treasury USDC payments require Touch ID at the moment of transfer. Secrets stay in memory and never touch the repo's .env.
A security engineer standardizes how every internal agent accesses credentials, retiring scattered .env files and plaintext home-dir dumps. She issues named abra keys per agent, enforces the process-control name rejection list (PATH, NODE_OPTIONS, PYTHONPATH), and uses key revoke plus health checks to rotate access after offboarding. The team relies on cartridge checkpoints for fast recovery during incidents.
The abra CLI and MCP are free for individual developers, covering local secret reading and issuance. Teams pay for USB/LAN sync, cartridge checkpoints, key-scope management, and audit trails. Revenue comes from per-seat subscriptions billed to engineering orgs that need shared access controls.
Rather than charging for the software itself, the operator charges per secret read or per agent session brokered through abra serve. Pricing scales with how many agents, projects, and TTL-bound approvals a company runs. This aligns cost with the value of safe automated secret delivery.
Finance and healthcare firms need documented controls showing that secret access is scoped, gated, and non-echoing. The add-on bundles policy templates, Touch ID enforcement, allowlist tooling, and exportable audit reports for SOC 2 or PCI reviewers. It's sold as an annual compliance package on top of the base vault.
💬 Integration Tip
Ensure ABRA_KEY lives in the environment rather than process arguments, and always set ABRA_ALLOWLIST before fetching so only pre-chosen names are injected. Treat all vault values as opaque data—never execute or echo them—and stop to ask the human whenever a fetch returns 401, 403, or 404.
Scored Oct 7, 2026
Access CoinMarketCap data via x402 pay-per-request protocol with USDC payments on Base. Use when users mention x402, want CMC data without API keys, ask abou...
Purchasing, payments and saved details through Aftercard
Plisio integration. Manage Invoices, Payouts, Wallets, Transactions, Users. Use when the user wants to interact with Plisio data.
Send and receive money via Venmo using Strider Labs MCP connector. Pay friends, request payments, split bills, check balances. Complete autonomous P2P paymen...
Send and receive money via PayPal using Strider Labs MCP connector. Send payments, request money, check balance, view transactions. Complete autonomous onlin...
Molt Motion Pictures platform skill. Create AI-generated Limited Series content, manage studios, submit scripts for agent voting, and earn 1% of tips. Wallet-based auth, x402 payments.