comfy.fun MCP
Related Servers
Alternatives to comfy.fun MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to read multi-chain memecoin launchpad data including coins, burns, staking, fee boards, and read-only perps markets, while calculating quotes and preparing buys, sells, stakes, unstakes, and launches for the user’s own wallet to sign.MIT
- AlicenseBqualityBmaintenanceEnables read-only access to public Star Atlas-inspired game data, profile key audits, DAO treasury/proposal/revenue/Ecosystem Fund information, and signed hub updates, listings, and claims through MCP tools, without signing or writing to any chain.22Apache 2.0

QoreChain MCPofficial
AlicenseNot gradedqualityBmaintenanceGives AI agents and developer tools read access to a blockchain network's blocks, transactions, accounts, validators, staking tiers, contract reads and fee estimates, plus post-quantum signature status checks and unsigned transfers for the user's own wallet to sign. It never signs, holds keys, or broadcasts.Apache 2.0- AlicenseAqualityCmaintenanceEnables MCP clients to access public spot market data—tickers, candlesticks, order books, trades, spreads, instruments, assets, and system status—via remote Streamable HTTP or local stdio. It is read-only and requires no API keys.10MIT
- AlicenseAqualityDmaintenanceProvides read-only access to Solana on-chain data, enabling natural language queries for wallet balances, token holdings, prices, transactions, and more via MCP-compatible clients.8MIT
- FlicenseNot gradedqualityBmaintenanceExposes 8 read-only Trust Vault tools over MCP (Streamable HTTP) for querying protocol overview, tokens, market rates, orders, platform stats, fees, and currencies. Enables on-chain reads and static config without wallet or signing.-
TDQS
Scored across 14 tools
Most tools have clearly distinct purposes, especially around tokens, swaps, launches, tasks, bazaar, and compute. A few pairs could be confused at first glance, such as comfy_tokens vs comfy_search_tokens and comfy_compute_funded vs comfy_agent_compute, but their descriptions provide enough separation.
All tools use a consistent comfy_ prefix and snake_case, making the set readable and predictable. The only minor inconsistency is that some names are verb-led actions (search, build) while most are resource nouns, but the convention remains coherent.
With 14 tools, the server is well within the appropriate range for a broad platform surface covering tokens, trading, launches, tasks, bazaar, jobs, and compute. Each tool appears to serve a distinct resource or operation rather than bloating the set.
The read and transaction-building surface is fairly strong for tokens, swaps, launches, fees, trades, and compute. However, task and job functionality is largely read-only with no create, accept, submit, or lifecycle operations, and the bazaar surface only exposes the floor rather than broader service management.