An “official MCP” can be a public data server, an OAuth-protected trading gateway, a local package with hundreds of tools or a wallet application that cannot be inspected without interactive activation. WagerX examined four first-party products from major crypto companies and found four materially different access models.
“Official” describes provenance: the provider owns or publishes the product. It does not mean WagerX verified every tool, that the endpoint is publicly accessible, or that using it is safe, legal or appropriate for a particular user.
The result at a glance
| Product | Delivery | Access | WagerX observation |
|---|---|---|---|
| Crypto.com Market Data MCP | Hosted HTTP | Public, no account or key | Handshake, nine tools and two read-only calls succeeded |
| Binance Agentic MCP | Hosted HTTP | OAuth and Agentic sub-account | Endpoint and OAuth metadata observed; tools blocked before authorization |
| Bybit Trading MCP | Local stdio package | Public data without a key; scoped credentials for private actions | Local handshake and 382-tool inventory observed; no tool executed |
| Coinbase Agentic Wallet MCP | Local app and stdio package | Interactive email/OTP wallet activation | Official installer and package observed; protocol inspection blocked by activation |
1. Crypto.com: public retrieval with the lowest barrier
Crypto.com operates a hosted streamable-HTTP MCP at https://mcp.crypto.com/market-data/mcp. It required no account, OAuth grant or API key during our September 1 test. Initialization succeeded, the server advertised nine tools, and representative ticker and order-book calls returned structured public market data.
This is the simplest model for a newcomer to understand: connect, inspect tools and retrieve public information. Its deliberately narrow scope is also a strength. The observed tools read market data; they do not expose an account or place trades.
2. Binance: a live door with authorization in front of it
Binance publishes a hosted Agentic MCP at https://agent.binance.com/mcp/agentic. WagerX's unauthenticated initialization reached the service but received HTTP 401 and official OAuth protected-resource metadata. That proves the endpoint is present and protected; it does not prove the post-login tool inventory.
Binance describes capabilities spanning public market data, balances, positions and trading. It also states that withdrawals are unavailable and trades or transfers require confirmation. Those are provider declarations until WagerX completes an authorized inspection.
3. Bybit: local execution and a very large registry
Bybit takes a different route. Its official MCP is a local stdio package rather than a public URL. WagerX launched version 2.1.18 without credentials, completed initialization and counted 382 registered tools. The registry covers public data and provider-described authenticated account, asset, trading, loan, earn and streaming operations.
A large inventory demonstrates coverage, not quality. An agent still needs permission controls, sensible tool selection and a clear distinction between public reads and account-changing actions. WagerX did not execute a Bybit tool or connect an account.
4. Coinbase: an MCP inside a wallet experience
Coinbase's product is better understood as an Agentic Wallet MCP than an exchange market-data server. The official @coinbase/payments-mcp package uses a local Electron companion application and interactive email/OTP activation to create an embedded wallet. Provider documentation describes balances, addresses, onramp and x402/USDC payment capabilities.
WagerX confirmed the official distribution path and release archive, but stopped before creating a wallet. As a result, the protocol handshake and tools remain unobserved. This is why Coinbase belongs in the Index's Payments & Wallets category rather than the featured exchange-MCP row.
What newcomers should remember
- Hosted means a client connects to a remote URL; stdio normally means software runs locally and communicates through standard input/output.
- No authentication can be appropriate for public data, but private balances and actions should require scoped authorization.
- A handshake confirms protocol communication. It does not prove every tool works.
- A tool list describes available interfaces. It does not prove WagerX executed them.
- Official provenance is independent from technical verification and from financial, legal or safety assessment.
What professionals should compare
Beyond tool count, evaluate transport, credential custody, OAuth scopes, local supply-chain risk, read/write annotations, confirmation requirements, audit logs, rate limits and the blast radius of a compromised agent. The right architecture depends on whether the goal is public research, portfolio visibility, payments or trading.
Method and limits
This comparison uses provider-owned documentation and WagerX protocol observations completed by September 1, 2026. We made no trade, transfer, payment, deposit or withdrawal; connected no exchange account; and supplied no financial credentials. Product behavior can change after the observation date.
Open the underlying evidence records for Crypto.com, Binance, Bybit and Coinbase.