Bitquery vs xyz.cabalspy/wallet-tracker
Bitquery is an MCP server published by pipeworx-io. Marketplaces we read that list it: 1 (Official MCP Registry). xyz.cabalspy/wallet-tracker is an MCP server published by cabalspy.xyz. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-11. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Bitquery |  xyz.cabalspy/wallet-tracker |
|---|---|---|
| Official MCP Registry | Listed Version: 0.2.1 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 2.7.0 No figure published Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Bitquery | xyz.cabalspy/wallet-tracker |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release (differs) | 2026-10-30 (worse) | 2026-11-01 (better) |
| Where it runs (differs) | Remote server (gateway.pipeworx.io/bitquery/mcp) | Remote server (mcp.cabalspy.xyz/mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/pipeworx-io/mcp-bitquery | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Status out of date: last check 38 h ago returned HTTP 200 | Status out of date: last check 2 days ago returned HTTP 406 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Bitquery
Bitquery MCP — trade-level blockchain data (DEX trades, transfers, holders) across 40+ chains via…
xyz.cabalspy/wallet-tracker
KOL and smart money tracking on 5 chains, plus CabalSpy ID (SocialFi): verified traders, theses.
How to run each
Bitquery As a remote MCP server
claude mcp add --transport http bitquery https://gateway.pipeworx.io/bitquery/mcpRequires: PIPEWORX_API_KEY (secret)
xyz.cabalspy/wallet-tracker As a remote MCP server
claude mcp add --transport http wallet-tracker https://mcp.cabalspy.xyz/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Both endpoints responded at the last daily check. How we check endpoints
Tools each declares
Only Bitquery has
ai_visibility_checkarchive_comparearchive_evidenceask_pipeworxask_pipeworx_betaask_pipeworx_groundedbet_researchbitquery_dex_tradesbitquery_token_holdersbitquery_token_transfersclassify_rowcompany_facts
Show the remaining 35
company_register_searchcompare_entitiesdeep_researchdiscover_toolsentity_profileforgetgenerate_llms_txtkalshi_weather_edgelist_subscriptionspipeworx_feedbackpipeworx_trendingpolymarket_arbitragepolymarket_edge_trackerpolymarket_edgespolymarket_fill_riskpolymarket_kalshi_spreadprediction_calibrationrecallrecent_alertsrecent_changesrelease_calendar_marketsrememberresearch_rowresolution_auditresolution_diffresolve_entityscan_competitor_ai_presencescan_dependencysearch_withinsubscribesuggest_questionsunsubscribeupdown_divergence_rateupdown_venue_comparevalidate_claim
Only xyz.cabalspy/wallet-tracker has
compare_tokenscompare_walletscsid_kolscsid_latest_thesescsid_leaderboardcsid_profilecsid_thesiscsid_token_thesescsid_user_thesescsid_wallet_ownerdetect_bundlesget_activity_metrics
Show the remaining 17
get_analyticsget_api_statusget_leaderboardget_pnl_calendarget_recent_tradesget_signal_historyget_signalsget_startedget_token_holdersget_token_statsget_token_transactionsget_wallet_connectionsget_wallet_historyget_wallet_holdingsget_wallet_trackerlist_walletslookup_wallet
Both have
None
Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (Bitquery as of 2026-10-28; xyz.cabalspy/wallet-tracker as of 2026-10-16). More tools is not better in itself: compare what each needs for the job.
Settings each asks for
The marketplaces of xyz.cabalspy/wallet-tracker publish no settings it asks for, so we do not compare settings.
What it can do: Bitquery · What it can do: xyz.cabalspy/wallet-tracker · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.