Cloaked Agent
Give autonomous agents a Solana spending account with on-chain enforced limits so paid API calls do not drain your main wallet.
Overview
Cloaked is an MCP server for the Build phase that provisions Solana spending accounts for AI agents with on-chain enforced spending limits.
What is this MCP server?
- Trustless spending accounts for AI agents on Solana with on-chain limit enforcement
- stdio npm package @cloakedagent/sdk v0.2.0
- Requires CLOAKED_AGENT_KEY (Base58 private key); optional CLOAKED_BACKEND_URL relay
- Configurable SOLANA_RPC_URL (default https://api.devnet.solana.com)
- Pairs with paid MCP tools (e.g. micropayment APIs) for bounded agent commerce
- Server/package version 0.2.0; npm identifier @cloakedagent/sdk; transport stdio
- Required secret CLOAKED_AGENT_KEY; optional CLOAKED_BACKEND_URL (default api.cloakedagent.com)
- Default SOLANA_RPC_URL https://api.devnet.solana.com
Community signal: 1 GitHub stars.
What problem does it solve?
Letting agents spend from your primary wallet is risky because soft prompts cannot cap transfers when tools chain autonomously.
Who is it for?
Solo builders shipping agent prototypes that need bounded Solana spending for devnet trials or controlled production agent commerce.
Skip if: Traditional Stripe checkout for end users, non-crypto teams, or workflows with no on-chain payment requirement.
What do I get? / Deliverables
Your agent operates through Cloaked accounts with enforced on-chain limits and relay-backed flows suited to metered third-party APIs.
- Agent-accessible spending accounts with on-chain enforced limits
- Configurable backend relay and RPC for payment workflows
- Safer separation between personal wallets and agent-operated spend
Recommended MCP Servers
Journey fit
Cloaked belongs in Build agent-tooling because you wire spending guardrails while constructing agents that call paid services. Agent-tooling is where MCP servers extend what agents can do safely—here, delegated payments with protocol-enforced caps.
How it compares
On-chain agent spending MCP, not a generic payment-gateway or banking Open Banking connector.
Common Questions / FAQ
Who is Cloaked for?
Cloaked is for developers building AI agents that must pay external services on Solana while keeping spend caps enforced on-chain instead of honor-system prompts.
When should I use Cloaked?
Use it during Build when wiring agent-tooling MCP stacks that call paid APIs and you need segregated keys, relays, and limit policies before wider autonomy.
How do I add Cloaked to my agent?
Add the stdio npm server @cloakedagent/sdk to MCP config, set CLOAKED_AGENT_KEY, optionally CLOAKED_BACKEND_URL and SOLANA_RPC_URL, then expose Cloaked tools to your host.