Back to MCP servers

Fund Trailing & Calendar Year Returns

https://server.smithery.ai/fruitstand/fund-returns/mcp
● down

Trailing and calendar-year total returns for 32,000+ US mutual funds and ETFs — compare fund performance by ticker. Six read-only tools: search the fund universe, fetch metadata, and pull single or batched (up to 100) trailing/calendar returns, latest or as-of a date. Free tier; same data and API key as the Fruit Stand REST API.

What we measured

Over the last 30 days we probed this MCP server 28 times on 28 days; it answered 0 (0%).

When we called tools/list it returned 6 tools, including searchFunds, getFund, getTrailingReturns, over MCP protocol revision 2025-11-25.

Among the 53,642 reachable MCP servers in our snapshot of 2026-11-13 01:12 UTC, it is faster than 42% and higher on readiness than 2%.

From agent-tools.cloud's own probes, last checked 2026-11-13. How we measure

Tools (6)

As returned by the server's own tools/list when we called it.

searchFunds
Search the ~32,000 US mutual funds and ETFs by name or ticker to get the `code` the other tools need. Returns fund metadata only — name, type (ETF or FUND), exc…
getFund
Fetch one fund's metadata by ticker (`code`): name, type (ETF or FUND), exchange, currency, ISIN, active/inactive status, and the date range for which return da…
getTrailingReturns
Trailing total returns for one fund: 1d, 1w, 1m, 3m, 6m, YTD, 1y-20y, and since inception. Latest by default, or pass `as_of` (snaps to the prior trading day).…
batchTrailingReturns
Trailing total returns for up to 100 funds in one call - same data as getTrailingReturns. Pass `codes` and optional `as_of`. One row per fund; funds with no dat…
getCalendarReturns
Full calendar-year (Jan-Dec) total return for one fund. Pass `year`, or omit for the latest completed year. `calendar_year_return` is a decimal fraction, distri…
batchCalendarReturns
Calendar-year total returns for up to 100 funds in one call - same data as getCalendarReturns. Pass `codes` and optional `year`. One row per fund; funds with no…
Transport
streamable-http
Auth
smithery_api_key
Cost
—
Protocol revision
2025-11-25
negotiated, not declared

MCP readiness

F · 32/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. For x402 and A2A listings it contributes up to 15 of the 100 quality points; for MCP listings it is shown for reference only. Search order and leaderboards use the separate quality grade (here E, 12.0/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ

Valid MCP handshake 0/10 No MCP handshake completed.
Live MCP endpoint 0/25 Endpoint did not answer.
Protocol revision 8/10 Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28.
Signed descriptor n/a No MCP standard defines a signed server descriptor.
Uptime (30 days) 0/15 0/28 probes succeeded over 30 days (0%).
Tool declaration 10/10 Lists 6 tool(s) with descriptions.
Verified identity 5/10 Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Freshness + modern flags 4/5 seen in a source within 7 days.
Auth declaration 2/5 Declares credential scheme: smithery_api_key.
Applicable criteria total 90 points, scaled to 100.
Measured 2026-11-13.
Nine criteria, the same as the A2A readiness score, read from our daily MCP probe (initialize + tools/list) and 30-day probe history. No MCP standard defines a signed server descriptor, so that criterion is n/a and the other 90 points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.

Compared with peers

Against 53,642 reachable MCP servers in our daily snapshot (2026-11-13 01:12 UTC). Display only; it does not change search order.

Readiness
Higher than 2% of peers
This listing 32 · peer median 81
Latency
Faster than 42% of peers
This listing 427 ms · peer median 349 ms

Where it loses the most points, and how to win them back

  • Live MCP endpoint −25 — Answer initialize and tools/list at the declared endpoint.
    Now: Endpoint did not answer.
  • Uptime (30 days) −15 — Stay reachable in our daily probes.
    Now: 0/28 probes succeeded over 30 days (0%).
  • Valid MCP handshake −10 — Complete the MCP handshake without errors.
    Now: No MCP handshake completed.

How many agent tools actually work · All statistics

Listed in

Directories this entry was found in.

How to connect

MCP endpoint (streamable-http)
https://server.smithery.ai/fruitstand/fund-returns/mcp
JSON-RPC initialize probe
curl -X POST https://server.smithery.ai/fruitstand/fund-returns/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'
Homepage
https://fruitstand.dev/
Listed at (smithery)
https://fruitstand.dev/