The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Fruit Stand Fund Returns listing page.
Live trailing & calendar-year total returns for 32,000+ US mutual funds and ETFs, as an MCP server. Ask an AI assistant to compare fund performance by ticker — no Morningstar or Bloomberg contract, free tier, same API key as the REST API.
Hosted, remote MCP over Streamable HTTP · works with Claude, Cursor, and any MCP client · get a free API key

Sign up at app.fruitstand.dev — the free tier needs no card.
Remote MCP over Streamable HTTP, authenticated with your API key as a bearer token.
Native remote-MCP clients (Claude web/desktop "Add custom connector", Cursor, etc.) — use the URL above and add the header:
Claude Desktop config (claude_desktop_config.json) — bridge to the remote endpoint with mcp-remote:
Restart the client and the Fruit Stand tools appear.
Docker — the same bridge as a container (this repo's Dockerfile), for clients that take a docker command:
The container only bridges stdio to api.fruitstand.dev/mcp — all data comes from the hosted server.
"Compare the 1-year, 5-year, and since-inception returns of SPY, QQQ, and VTI, and tell me which had the best 2022 calendar year."
The assistant calls batchTrailingReturns and batchCalendarReturns and summarizes.
Six tools, mirroring the REST API. Returns come back as decimal fractions (0.1234 = 12.34%).
| Tool | Does | Key inputs |
|---|---|---|
searchFunds | Search / list the fund universe (keyset paginated) | q, type, country, exchange, cursor, limit |
getFund | Fund metadata by ticker | code |
getTrailingReturns | Trailing returns for one fund (latest or as-of a date) | code, as_of? |
batchTrailingReturns | Trailing returns for up to 100 funds in one call | codes[], as_of? |
getCalendarReturns | Calendar-year return for one fund (latest or a given year) | code, year? |
batchCalendarReturns | Calendar-year returns for up to 100 funds in one call | codes[], year? |
Tickers use the SYMBOL.US form (e.g. SPY.US, VTSAX.US).
MCP tool calls are metered exactly like REST calls and count against your monthly quota. A key with no active plan gets a 403 on tool calls.
MIT — this repo holds the public docs and connector metadata for the hosted service; the service implementation lives in a separate repo.