# Coinbase MCP server (Coinbase for Agents) vs Openfort

> Openfort scores 70.1 (BB) to Coinbase's 60.2 (C) for wallet custody. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/coinbase-mcp-vs-openfort
- Markdown: https://www.anchorterminal.com/compare/coinbase-mcp-vs-openfort.md (~2,700 tokens)
- Slim: https://www.anchorterminal.com/compare/coinbase-mcp-vs-openfort.min.md (~830 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/coinbase-mcp-vs-openfort.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-10-25

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.

- Coinbase MCP server (Coinbase for Agents): grade C, 60.2/100, rank #593 of 1210. Markdown https://www.anchorterminal.com/tools/coinbase-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/coinbase-mcp.json
- Openfort: grade BB, 70.1/100, rank #179 of 1210. Markdown https://www.anchorterminal.com/tools/openfort.md · JSON https://www.anchorterminal.com/api/v1/tools/openfort.json
- Best agent wallets and spending controls: https://www.anchorterminal.com/best/agent-wallets/index.md
- All 47 wallets comparisons: https://www.anchorterminal.com/compare/agent-wallets/index.md

## Which one, for what

### Coinbase MCP server (Coinbase for Agents) (C)

Good 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)

Good 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 | Coinbase MCP server (Coinbase for Agents) | Openfort | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 55 | 88 | Openfort +33 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 65 | 89 | Openfort +24 |
| Agent ergonomics | 13% (16.2 this run) | 66 | 65 | Coinbase MCP server (Coinbase for Agents) +1 |
| Security & auth | 14% (17.5 this run) | 70 | 65 | Coinbase MCP server (Coinbase for Agents) +5 |
| Payments & pricing | 10% (12.5 this run) | 40 | 60 | Openfort +20 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 58 | 87 | Openfort +29 |
| Transparency & trust | 7% (8.8 this run) | 64 | 69 | Openfort +5 |
| Negative events | ≤15 | 0 | -5 | |
| **Total** | | **60.2 · C** | **70.1 · BB** | |

## 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)

1. Call `coinbase_portfolios_list` first and name the portfolio on every order; an order without one falls back to the default portfolio and fails if it isn't granted
2. Send a fresh `client_order_id` with each order and reuse it on retry, so a dropped connection doesn't place a second order
3. Preview with `coinbase_orders_preview` and confirm with the person before `coinbase_orders_create`; equity previews may be unavailable
4. Use `ETH-USDC`-style pairs when buying with a USDC balance, and `base_size` in contracts for futures
5. Agree a spending budget before `coinbase_x402_fetch`, set `max_amount`, and keep the `idempotency_key` for any retry; settled payments can't be reversed

### Openfort

1. Call `policies.evaluate` with operation `signEvmTransaction` before every EVM backend send. The send itself is checked only as `signEvmHash`
2. Keep the signing policy and the gas sponsorship policy separate. Linking a signing policy to a fee sponsorship stops it working as a guardrail
3. Pass a fee sponsorship on EVM sends. Without one the transaction stays pending with no error
4. Give an agent a secret key without `accounts:export`, and limit the CLI MCP server to the tools it needs
5. On a 5xx after a write, read the resource before retrying. On a 429, wait the full `Retry-After`

## Tutorials

- [Build a backend wallet inventory with Openfort](https://www.anchorterminal.com/tutorials/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.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/coinbase-mcp-vs-openfort.json, and with the fewest tokens: https://www.anchorterminal.com/compare/coinbase-mcp-vs-openfort.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "coinbase-mcp", "b": "openfort"}`. From a terminal: `anchor compare coinbase-mcp openfort`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/coinbase-mcp.json and https://www.anchorterminal.com/api/v1/tools/openfort.json

## Other comparisons with Coinbase MCP server (Coinbase for Agents) or Openfort

- [Circle Wallets (Agent Wallets, Programmable Wallets) vs Openfort](https://www.anchorterminal.com/compare/circle-wallets-vs-openfort.md)
- [Coinbase Developer Platform (Agentic Wallet, AgentKit, CDP MCP) vs Openfort](https://www.anchorterminal.com/compare/coinbase-cdp-agentkit-vs-openfort.md)
- [Kite Agent Passport vs Openfort](https://www.anchorterminal.com/compare/kite-agent-passport-vs-openfort.md)
- [Openfort vs Privy Wallets (server wallets, agent wallets, policy engine)](https://www.anchorterminal.com/compare/openfort-vs-privy.md)
- [Openfort vs Sponge Wallet](https://www.anchorterminal.com/compare/openfort-vs-sponge-wallet.md)
- [Openfort vs Turnkey Agentic Wallets](https://www.anchorterminal.com/compare/openfort-vs-turnkey-agentic-wallets.md)
- [Agentcard vs Openfort](https://www.anchorterminal.com/compare/agentcard-vs-openfort.md)
- [Coinbase MCP server (Coinbase for Agents) vs Kite Agent Passport](https://www.anchorterminal.com/compare/coinbase-mcp-vs-kite-agent-passport.md)
- [Coinbase MCP server (Coinbase for Agents) vs Agent Vault by Self](https://www.anchorterminal.com/compare/coinbase-mcp-vs-self-agent-vault.md)
- [Openfort vs Agent Vault by Self](https://www.anchorterminal.com/compare/openfort-vs-self-agent-vault.md)
- [Agentcard vs Coinbase MCP server (Coinbase for Agents)](https://www.anchorterminal.com/compare/agentcard-vs-coinbase-mcp.md)
- [Circle Wallets (Agent Wallets, Programmable Wallets) vs Coinbase MCP server (Coinbase for Agents)](https://www.anchorterminal.com/compare/circle-wallets-vs-coinbase-mcp.md)
- [Coinbase Developer Platform (Agentic Wallet, AgentKit, CDP MCP) vs Coinbase MCP server (Coinbase for Agents)](https://www.anchorterminal.com/compare/coinbase-cdp-agentkit-vs-coinbase-mcp.md)
- [Coinbase MCP server (Coinbase for Agents) vs Privy Wallets (server wallets, agent wallets, policy engine)](https://www.anchorterminal.com/compare/coinbase-mcp-vs-privy.md)
- [Coinbase MCP server (Coinbase for Agents) vs Sponge Wallet](https://www.anchorterminal.com/compare/coinbase-mcp-vs-sponge-wallet.md)
- [Coinbase MCP server (Coinbase for Agents) vs Turnkey Agentic Wallets](https://www.anchorterminal.com/compare/coinbase-mcp-vs-turnkey-agentic-wallets.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp