Fruit Stand Fund Returns — MCP Server
MCP serverProductivityYour AI can look up the past performance of more than 32,000 US mutual funds and ETFs. Once fund-returns is added, it can pull trailing and calendar-year returns for any fund by its ticker, so you can check how an investment has done without leaving your conversation.
Available today. Use it from your connected AI after setup.
Needs your own account with this service. Credentials stay encrypted.
Add fund-returns to your AI, then try asking for the trailing or calendar-year returns of a fund you follow using its ticker symbol.
Then ask your AI: use the searchFunds tool from Fruit Stand Fund Returns — MCP Server
What your AI can do with it
- Look up returns for any of 32,000+ US mutual funds and ETFs by ticker
- Get trailing returns to see how a fund has performed recently
- Get calendar-year returns to see how a fund did in past years
- Compare returns across several funds you are weighing against each other
- Ask about fund performance in plain language mid-conversation
From the project's README
As published by fruitstanddev/fruitstand-mcp in README.md.
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
Quick start
1. Get an API key
Sign up at app.fruitstand.dev — the free tier needs no card.
2. Point your client at the endpoint
https://api.fruitstand.dev/mcp
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:
Authorization: Bearer YOUR_API_KEY
Claude Desktop config (claude_desktop_config.json) — bridge to the remote endpoint with mcp-remote:
{
"mcpServers": {
"fruit-stand": {
"command": "npx",
"args": [
"mcp-remote",
"https://api.fruitstand.dev/mcp",
"--header",
"Authorization: Bearer YOUR_API_KEY"
]
}
}
}
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:
{
"mcpServers": {
"fruit-stand": {
"command": "docker",
"args": ["run", "--rm", "-i", "-e", "FRUITSTAND_API_KEY", "ghcr.io/fruitstanddev/fruitstand-mcp"],
"env": { "FRUITSTAND_API_KEY": "YOUR_API_KEY" }
}
}
}
The container only bridges stdio to api.fruitstand.dev/mcp — all data comes from the hosted server.
3. Ask a question
"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.
Tools
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).
About the data
- Coverage: ~32,000 US mutual funds & ETFs.
- Trailing returns: standard windows through since-inception, total return (distributions reinvested).
- Calendar returns: full-year total return per calendar year.
- Freshness: refreshed daily from the same pipeline that builds the Fruit Stand datasets on Snowflake Marketplace.
- Methodology & field reference: app.fruitstand.dev/api/mcp and the docs.
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.
Links
- Get a key / pricing: https://app.fruitstand.dev/pricing
- MCP setup docs: https://app.fruitstand.dev/api/mcp
- REST API reference: https://app.fruitstand.dev/api
- Marketing site: https://fruitstand.dev
- Status of the data pipeline / datasets: https://fruitstand.dev/datasets
License
MIT — this repo holds the public docs and connector metadata for the hosted service; the service implementation lives in a separate repo.
Tools it offers (6)
What this server listed when ahel dialed its public endpoint in Sep 2026, with no key and no account of yours. The names are the server’s own.
searchFundsgetFundgetTrailingReturnsbatchTrailingReturnsgetCalendarReturnsbatchCalendarReturns
Signals
- Last commit
- Sep 2026
Advanced
- Delivery
- fund-returns MCP server → your ahel gateway (mcp.ahel.ai) → every connected AI client.
- Catalog kind
- mcp-server
- Gateway key
dev-fruitstand-fund-returns- Source
- github.com/fruitstanddev/fruitstand-mcp
- Hosted endpoint
https://api.fruitstand.dev/mcp