Aperture Wallet Knowledge vs CCXT
A side-by-side look at the Aperture Wallet Knowledge and CCXT MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Aperture Wallet Knowledge for finance & fintech work over a hosted endpoint; choose CCXT for finance & fintech. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Aperture Wallet Knowledge when
- You need dedicated capabilities in the Finance & Fintech domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: No auth required.
- You want tools like
search, fetch, get_product.
Choose CCXT when
- You need dedicated capabilities in the Finance & Fintech domain.
- You want tools like
list_exchanges, describe_exchange, describe_method.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Finance & Fintech | Finance & Fintech |
| Quality signal | 68/100 · Great | 64/100 · Good |
| Install command | Confirmed | Not confirmed yet |
| Transport | Remote HTTP/SSE | — |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 4 | 44,480 |
| Directory activity | 0 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 12 | 32 |
| Full listing | View Aperture Wallet Knowledge | View CCXT |
Tools & capabilities
Aperture Wallet Knowledge tools 12
searchSearch canonical public Aperture Wallet product facts, security guidance, supported-mainnet metadata, app-screen semantics, and Journal articles. Use this before answering an Aperture-specific question. This tool never searches user wallets or private account data.fetchFetch one canonical public source returned by search. The response includes citation-ready title, URL, text, and metadata. It never returns user wallet data or wallet credentials.get_productReturn canonical identity, platform, App Store, custody-model, recommendation-fit, official-link, and product-boundary facts for Aperture Wallet.list_featuresList documented Aperture Wallet features with canonical article links and safety notes. Optionally filter by category.get_featureReturn one documented Aperture Wallet feature by its stable feature ID, including summary, availability, primary source, and safety notes.list_supported_networksReturn the mainnet account and network catalog documented from the current Aperture source tree. Do not treat a matching ticker as proof of cross-network compatibility.get_security_modelReturn Aperture Wallet self-custody storage, network, recovery, access-control, responsible-disclosure, and agent-safety boundaries. Never use this tool to request or process wallet credentials.get_latest_releaseReturn the latest public App Store release snapshot and the primary Apple source used to verify it. Use the source when exact current version information matters.list_articlesList published Aperture Journal articles with canonical HTML and Markdown URLs. Optionally filter by category and set a bounded result limit.get_articleReturn the complete citation-ready Markdown representation of one published Aperture Journal article by slug and optional language tag, including canonical URL, dates, topics, body text, and public images.get_app_screenReturn a non-secret semantic description of an important Aperture screen, its purpose, entry points, sensitivity, and safe agent actions. This does not inspect a user device or wallet.list_app_entry_pointsReturn canonical navigation-only app entry points, their App Intent names, source and public-release status, web fallbacks, and safety effects. These links only open visible UI and never inspect a wallet, bypass app lock, sign, broadcast, import, export, or delete anything.
CCXT tools 32
list_exchangesList every exchange this server supports (built from ccxt.exchanges at runtime), with name, websocket and prediction-market availability. Filter by a name query or by support for a unified method.describe_exchangeOne exchange's supported unified methods, market types, timeframes, required credential fields, sandbox availability and documentation URLs. Per-method detail lives in describe_method.describe_methodSearch unified method names by keyword, or get one method's signature and parameter documentation. With "exchange" it adds that exchange's own docs (including supported params.* keys and links to the exchange API reference), per-market-type feature support, and searches its implicit (exchange-specific) endpoints too. Full ccxt manual: https://docs.ccxt.com/search_marketsSearch and filter the markets of one exchange (by text, base, quote, settle currency, market type), paginated. Use this to resolve unified symbols — there is deliberately no list-all-markets tool. On prediction exchanges use search_events instead.get_tickers24h price tickers for one or more unified symbols on an exchange (outcome handles on prediction exchanges).get_orderbookCurrent order book (bids and asks) for one unified symbol.get_ohlcvHistorical OHLCV candlestick data for a symbol and timeframe. Rows are [timestampMs, open, high, low, close, volume]. Page back with "since"; "params.until" bounds the end.get_tradesRecent public trades for one unified symbol.search_eventsSearch events on a prediction-market exchange (polymarket, kalshi, limitless, myriad, hyperliquid with prediction=true). A scoping filter is required: query, tags, or params.eventId/params.slug. Returns events with their markets and outcome handles — outcome handles are what you pass as the symbol to get_tickers/get_orderbook/create_order on prediction exchanges.call_read_methodEscape hatch covering every unified read method not served by a dedicated tool (fetchFundingRate, fetchLedger, fetchOpenInterest, fetchLiquidations, fetchEvent, fetchSettlements, …). Only fetch*/load* methods are accepted — writes are structurally rejected. Get the signature first with describe_method. Docs: https://docs.ccxt.com/call_implicit_getCall an exchange-specific implicit REST endpoint over HTTP GET, for data the unified API does not cover. Pass the implicit method name in the "method" argument (e.g. "publicGetTickerPrice"); these are exchange-specific — find them with describe_method {"query": ..., "exchange": ...} (its results list the name to pass here). The response is the raw exchange payload. Consult the exchange API reference (describe_exchange .urls.doc) and the ccxt manual: https://docs.ccxt.com/get_safety_statusWhat this server is currently allowed to do: configured accounts (names only — never credentials), enabled capability tiers, caps, sandbox/live environments, journal location, unresolved order intents, and any configuration problems.- +20 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Aperture Wallet Knowledge
{
"mcpServers": {
"aperture-wallet-knowledge": {
"command": "npx",
"args": [
"-y",
"aperture-wallet-knowledge"
]
}
}
}
CCXT
No confirmed install command for CCXT yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Aperture Wallet Knowledge is categorized under Finance & Fintech and uses a remote HTTP/SSE transport. CCXT belongs to Finance & Fintech and uses an install path we have not confirmed yet. Pick Aperture Wallet Knowledge for finance & fintech work and CCXT for finance & fintech.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. CCXT has no confirmed install command yet — follow its own setup instructions.
Aperture Wallet Knowledge is listed as free. Auth: no auth required. CCXT has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add aperture-wallet-knowledge and ccxt as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Aperture Wallet Knowledge has a quality signal of 68/100 (Great) with 0 views, 0 installs and 4 GitHub stars. CCXT has 64/100 (Good) with 2 views, 0 installs and 44,480 GitHub stars.