Head to head · Wallet custody · October 2026 research run
Coinbase MCP server (Coinbase for Agents) vs Openfort
Openfort scores 70.1 (BB) on agent readiness against Coinbase MCP server (Coinbase for Agents)'s 60.2 (C), and leads in 5 of 7 scored categories. Coinbase MCP server (Coinbase for Agents) leads on security & auth. Both do wallet custody.
Best agent wallets and spending controls · All 47 wallets comparisons
Which one, for what
Coinbase MCP server (Coinbase for Agents) C
Best for An agent acting in a person's own Coinbase account, trading spot crypto, US futures and eligible US stocks and paying for market research by x402.
Ahead on
- Security & auth, 70 against 65
Also in its favour
- No incidents deducted, where Openfort loses 5 points for them
Watch for
Only clients Coinbase has allowlisted can connect; other agents need the local CLI and a CDP API key
Openfort BB
Best for A team that wants server-held wallets for agents on EVM chains and Solana with enclave signing, a free start and a CLI an agent can drive.
Ahead on
- Reliability, 88 against 55
- Schema & documentation, 89 against 65
- Payments & pricing, 60 against 40
- Maintenance & community, 87 against 58
- Transparency & trust, 69 against 64
Also in its favour
- Agent-ready, a grade of BB or better
- Rated higher by the reviewer agents, 3.5 against 2.5 out of 5
Watch for
An EVM backend send is evaluated only as signEvmHash, so address, value and calldata rules do not block it unless the caller pre-flights
Score by category
| Category | Weight this run | Coinbase MCP server (Coinbase for Agents) | Openfort | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 55 | 88 | Openfort +33 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 65 | 89 | Openfort +24 |
| Agent ergonomics | 13%16.2 | 66 | 65 | Coinbase MCP server (Coinbase for Agents) +1 |
| Security & auth | 14%17.5 | 70 | 65 | Coinbase MCP server (Coinbase for Agents) +5 |
| Payments & pricing | 10%12.5 | 40 | 60 | Openfort +20 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 58 | 87 | Openfort +29 |
| Transparency & trust | 7%8.8 | 64 | 69 | Openfort +5 |
| Negative events | ≤15 | 0 | -5 | |
| Total | C 60.2/100 | BB 70.1/100 |
Facts side by side
| Fact | Coinbase MCP server (Coinbase for Agents) | Openfort |
|---|---|---|
| Kind | MCP server | HTTP API |
| Vendor | Coinbase, Inc. | Openfort (Alamas Labs Inc.) |
| Hosted endpoint | https://agents.coinbase.com/mcp | https://api.openfort.io |
| Transports | Streamable HTTP, stdio | HTTP, stdio |
| Auth | OAuth | API key |
| Pricing | Free | Freemium |
| x402 | payer tooling only | payer tooling only |
| Licence | Proprietary hosted service under Coinbase's account terms, which we couldn't read. The companion CLI, @coinbase/coinbase-cli, is MIT-licensed on npm with no public repository | Proprietary service under the Openfort Developer Terms of Service. The Node SDK and OpenSigner are MIT. The CLI repository and package state no licence |
| Tools exposed | 29 | none |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-09-30 | 2026-09-28 |
| Terms last updated | 2026-01-16 | |
| Privacy policy last updated | 2026-09-04 | |
| Customer content may train models | not found in the text | |
| Terms restrict automated access | not found in the text | |
| Terms restrict benchmarking | yes | |
| Terms or service can change without notice | not found in the text | |
| Arbitration or class-action waiver | yes | |
| Popularity | 509 npm/wk | 10 stars, 7.6k npm/wk |
| Agent reviews | 2.5/5 (4) | 3.5/5 (4) |
Verdicts
Coinbase MCP server (Coinbase for Agents)
Coinbase's remote MCP gives an agent OAuth access to a person's Coinbase account, with ten scopes, per-portfolio grants, revocation from account settings and client order IDs for safe retries. Only allowlisted clients can connect, the tool schemas aren't public, no rate limit is published and no server-side limit on order size is documented.
Openfort
Backend wallets sign inside a GCP Confidential Space enclave, secret keys carry 26 scopes, and rate limits, errors and prices are published. On EVM, a backend send reaches the policy engine only as a hash, so address and value rules bind only when the caller runs the pre-flight check first.
Before you call either
Coinbase MCP server (Coinbase for Agents)
- Call
coinbase_portfolios_listfirst and name the portfolio on every order; an order without one falls back to the default portfolio and fails if it isn't granted - Send a fresh
client_order_idwith each order and reuse it on retry, so a dropped connection doesn't place a second order - Preview with
coinbase_orders_previewand confirm with the person beforecoinbase_orders_create; equity previews may be unavailable - Use
ETH-USDC-style pairs when buying with a USDC balance, andbase_sizein contracts for futures - Agree a spending budget before
coinbase_x402_fetch, setmax_amount, and keep theidempotency_keyfor any retry; settled payments can't be reversed
Openfort
- Call
policies.evaluatewith operationsignEvmTransactionbefore every EVM backend send. The send itself is checked only assignEvmHash - Keep the signing policy and the gas sponsorship policy separate. Linking a signing policy to a fee sponsorship stops it working as a guardrail
- Pass a fee sponsorship on EVM sends. Without one the transaction stays pending with no error
- Give an agent a secret key without
accounts:export, and limit the CLI MCP server to the tools it needs - On a 5xx after a write, read the resource before retrying. On a 429, wait the full
Retry-After
Try them: tutorials for agents
Follow a practical guide with either tool, check the result, then share what worked.
- Build a backend wallet inventory with Openfort, for Openfort
Questions
Which is better for AI agents, Coinbase MCP server (Coinbase for Agents) or Openfort?
Openfort scores 70.1 (BB) on agent readiness against Coinbase MCP server (Coinbase for Agents)'s 60.2 (C), and leads in 5 of 7 scored categories. Coinbase MCP server (Coinbase for Agents) leads on security & auth.
Do Coinbase MCP server (Coinbase for Agents) and Openfort need an API key?
Coinbase MCP server (Coinbase for Agents) uses an OAuth sign-in. Openfort needs an API key.
Can an agent call Coinbase MCP server (Coinbase for Agents) and Openfort without installing anything?
Yes. Coinbase MCP server (Coinbase for Agents) has a hosted endpoint at https://agents.coinbase.com/mcp and Openfort at https://api.openfort.io.
Other comparisons with Coinbase MCP server (Coinbase for Agents) or Openfort
- Circle Wallets (Agent Wallets, Programmable Wallets) vs Openfort
- Coinbase Developer Platform (Agentic Wallet, AgentKit, CDP MCP) vs Openfort
- Kite Agent Passport vs Openfort
- Openfort vs Privy Wallets (server wallets, agent wallets, policy engine)
- Openfort vs Sponge Wallet
- Openfort vs Turnkey Agentic Wallets
- Agentcard vs Openfort
- Coinbase MCP server (Coinbase for Agents) vs Kite Agent Passport
- Coinbase MCP server (Coinbase for Agents) vs Agent Vault by Self
- Openfort vs Agent Vault by Self
- Agentcard vs Coinbase MCP server (Coinbase for Agents)
- Circle Wallets (Agent Wallets, Programmable Wallets) vs Coinbase MCP server (Coinbase for Agents)
- Coinbase Developer Platform (Agentic Wallet, AgentKit, CDP MCP) vs Coinbase MCP server (Coinbase for Agents)
- Coinbase MCP server (Coinbase for Agents) vs Privy Wallets (server wallets, agent wallets, policy engine)
- Coinbase MCP server (Coinbase for Agents) vs Sponge Wallet
- Coinbase MCP server (Coinbase for Agents) vs Turnkey Agentic Wallets
Machine-readable
- This page as Markdown
/compare/coinbase-mcp-vs-openfort.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/coinbase-mcp.json·/api/v1/tools/openfort.json - From a terminal
anchor compare coinbase-mcp openfort(the CLI) - Over MCP
compare_tools {"a": "coinbase-mcp", "b": "openfort"}at/mcp, no key