Crypto Feeds
Server Details
Crypto Feeds MCP.
The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Uptime
- 0.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- pipeworx-io/mcp-crypto-feeds
- GitHub Stars
- 1
- Server Listing
- mcp-crypto-feeds
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 47 tools
Several clusters overlap heavily: ask_pipeworx / ask_pipeworx_beta / ask_pipeworx_grounded / deep_research / discover_tools / suggest_questions all answer 'find me an answer from the catalog', and six Polymarket tools (arbitrage, edges, edge_tracker, fill_risk, kalshi_spread, bet_research) sit on adjacent ground, as do entity_profile / company_facts / compare_entities / recent_changes / resolve_entity. The descriptions work unusually hard to draw the boundaries (explicit 'prefer X over Y', 'use this before sizing', mode lists), which saves the set, but an agent must read long prose to route correctly. archive_compare vs archive_evidence and research_row vs classify_row are separable only after careful reading.
Everything is snake_case, but conventions are mixed: verb-first (list_feeds, read_feed, fetch_feed, compare_entities, resolve_entity) coexists with noun-first (entity_profile, company_facts, company_register_search, archive_compare, recent_changes, recent_alerts). Suffix variants (_beta, _grounded, _tracker, _edge, _edges, _pp) plus near-duplicate stems (polymarket_edges vs polymarket_edge_tracker vs polymarket_arbitrage) make the names readable individually but not predictable as a family.
47 tools is far beyond what the stated 'Crypto Feeds' purpose needs — the feeds surface itself is only three tools (list_feeds, read_feed, fetch_feed) with the remaining 44 belonging to a broad multi-domain data gateway (SEC, FRED, FDA, patents, prediction markets, agent memory, feedback, subscriptions). At this size an agent needs meta-routers just to find tools, which is a symptom of an over-wide set rather than a well-scoped one.
For the feed-reading core the lifecycle is covered: discover curated sources (list_feeds with category/keyword filter), read with item filtering (read_feed), and arbitrary RSS/Atom/RDF ingestion with a proxy fallback (fetch_feed), plus push monitoring via subscribe/recent_alerts. Gaps are minor — no write/manage operations on feeds, no explicit paging or date-window args on read_feed, and no feed-health/dedupe tool — but agents can work around all of these.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
CoinDesk Data (formerly CryptoCompare / CCData) MCP.
Real-time crypto market data: candles, tickers, orderbooks across 13+ exchanges via MCP.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceEnables fetching cryptocurrency prices, historical OHLC data, and news via CryptoCompare API through an MCP gateway.94 npmMIT

Desk3 MCP Serverofficial
AlicenseBqualityDmaintenanceCryptocurrency MCP Server! Free! This powerful tool is designed for blockchain enthusiasts, providing comprehensive, real-time cryptocurrency information at your fingertips. Whether you're an experienced trader or just starting your journey into the crypto world.163MIT- AlicenseAqualityDmaintenanceAn MCP server that aggregates real-time cryptocurrency news from multiple RSS feeds.217MIT
- -licenseNot gradedqualityNot gradedmaintenanceReal-time financial market data MCP server. Stocks, crypto, technicals, sentiment, FDA calendar. No API keys required.-
Glama MCP Gateway
Add one secure layer between your agents and this server.