Is Gloam safe to connect to an AI agent?
Can trade unattended. Safety 48%
What an AI agent can do
- Live vs paper: live on mainnet (beta) on Tempo and Robinhood Chain since Oct 21, 2026 and on Base and Ethereum since Oct 26; Gloam says it is live on Elysium; the MCP server defaults to testnet, so a setup never moves to mainnet by itself source
- Order approval: the agent pays x402 and MPP resources and other Gloam addresses from a private balance without approving each payment, within spending limits it cannot lift: off-chain limits the local MCP server checks, and on Tempo an access key whose cap the protocol enforces; amounts and payees are hidden, money going in and out of the vault stays public; the hosted MCP server (gloam.trade/mcp) only reads and plans and never signs or holds keys; the local server that signs keeps the key on your machine; the MCP server can't cash out to a public wallet (the app and SDK can, for 0.5%); Gloam says it never holds your keys and there is no admin withdraw source
- Markets: stablecoins (USDC.e, pathUSD, USDT0, USDG and others by network), x402 and MPP payments, private balances on Tempo, Robinhood Chain, Base, Ethereum and Elysium
- Pricing: deposits and private payments free; cashing out to a public wallet costs 0.5%
Safeguards that exist
- Guardrails outside the agent: Spending limits the agent can't lift, but they're off-chain limits checked by the local server itself; only on Tempo does the protocol enforce an access key's cap (official docs) source
- Test before real money: Paper, demo or testnet mode available source
- Who holds the keys: Self-custody: the local MCP server that signs keeps the key on your machine, and the hosted server only reads and plans and never signs or holds a key; Gloam says it never holds your keys and has no admin withdraw (official docs) source
- Open source or audited: Open source (MIT); Kann Audits reviewed the vault contracts (report, Nov 1, 2026) and found no Critical, High or Medium issues (official docs) source
- Incident record (last 12 months): No incident naming this tool in our incident tracker in the last 12 months source
Safeguards that are missing
- Human approval: No approval per payment: the agent pays x402 and MPP resources and other Gloam addresses on its own, within its limits (official docs) source
- Sending funds out: The agent can pay any x402 or MPP resource and any Gloam address within its limits; the MCP server can't cash out to a public wallet (the app and SDK can, for 0.5%) (official docs) source
Safety score
| Input | From official docs or our listing | Points |
|---|---|---|
| Human approval | No approval per payment: the agent pays x402 and MPP resources and other Gloam addresses on its own, within its limits (official docs) source | 0 / 25 |
| Guardrails outside the agent | Spending limits the agent can't lift, but they're off-chain limits checked by the local server itself; only on Tempo does the protocol enforce an access key's cap (official docs) source | 8 / 15 |
| Test before real money | Paper, demo or testnet mode available | 15 / 15 |
| Sending funds out | The agent can pay any x402 or MPP resource and any Gloam address within its limits; the MCP server can't cash out to a public wallet (the app and SDK can, for 0.5%) (official docs) source | 0 / 15 |
| Who holds the keys | Self-custody: the local MCP server that signs keeps the key on your machine, and the hosted server only reads and plans and never signs or holds a key; Gloam says it never holds your keys and has no admin withdraw (official docs) source | 5 / 10 |
| Open source or audited | Open source (MIT); Kann Audits reviewed the vault contracts (report, Nov 1, 2026) and found no Critical, High or Medium issues (official docs) source | 10 / 10 |
| Incident record (last 12 months) | No incident naming this tool in our incident tracker in the last 12 months (incident tracker) | 10 / 10 |
| Total | 48% of the points we could check | 48 / 100 |
Sources
Full listing: Gloam · How the score works: Safety score method