fletch-mcp
OfficialRelated Servers
Alternatives to fletch-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables agents to query live Robinhood Chain data including tokens, wallets, Chainlink feeds, heat scores, and tracking error on tokenized equities, all read-only without API keys.44 npmMIT

STOX Research MCPofficial
AlicenseAqualityCmaintenanceEnables live market data lookup and search for tokenized stocks, ETFs, commodities, bonds, and real estate on Robinhood Chain, plus broader DEX token discovery, including price queries, market ranking, and movers.5MIT- AlicenseNot gradedqualityCmaintenanceEnables querying normalized real-world asset data through MCP tools, including listing assets, retrieving asset details, comparing yields against SOFR, and checking eligibility by jurisdiction.MIT

robinscan-mcpofficial
AlicenseNot gradedqualityBmaintenanceMCP server for querying Robinhood Chain blockchain data, including network stats, transactions, token transfers, and stock prices.MIT- FlicenseNot gradedqualityCmaintenanceRead-only MCP server for Robinhood chain launchpad discovery and token due diligence using GMGN data.-
- AlicenseBqualityBmaintenanceGives MCP clients tools to discover tokenized Stock Tokens, read prices, corporate actions, and portfolio balances, and create route quotes. It prepares policy-checked trade plans with an explainable verdict and unsigned transactions for the user's wallet to sign.8231 npmMIT
TDQS
Scored across 17 tools
Most tools target a distinct resource (assets, rounds, holders, pools, bridge, documents, events), and the descriptions are detailed enough to separate them. A few pairs—status vs chain_health, history vs activity—could be confused at a glance, but their purposes are clearly differentiated once read.
The set is mostly readable snake_case noun-resource names, with list_assets and get_asset as the only verb-prefixed tools. This mixed convention is not chaotic, but it is inconsistent: bare resources like holders, pools, and events sit alongside verb-prefixed asset endpoints.
Seventeen tools is at the heavy end for a single MCP server, and the calibration for this range is borderline. That said, each tool does correspond to a distinct data domain rather than redundant operations, so the count is justified even though it feels large.
The read-only surface covers the main data domains well: asset discovery and detail, feed rounds, history, holders, transfers, pools, venues, bridge flows, documents, lookalikes, chain health, events, corporate actions, and webhooks. Minor gaps exist—such as no document-body retrieval and no per-job drilldown beyond the aggregate status—but they are workable.