# Fruit Stand Fund Returns (remote · api.fruitstand.dev)

Trailing & calendar-year returns for 32,000+ US mutual funds & ETFs — fund performance by ticker.

- Trust score: 79/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-24

## Components

- remote · `api.fruitstand.dev`: 79/100 (this document), [markdown](https://verifymcp.io/servers/dev-fruitstand-fund-returns/api.md), [page](https://verifymcp.io/servers/dev-fruitstand-fund-returns/api)

## Channel facts

- Endpoint: `https://api.fruitstand.dev/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-24.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 604 tokens (~100/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 57/100
  - Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Fruit Stand Fund Returns MCP server?

Fruit Stand Fund Returns is a hosted endpoint at https://api.fruitstand.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http dev-fruitstand-fund-returns 'https://api.fruitstand.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-fruitstand-fund-returns": {
      "url": "https://api.fruitstand.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-fruitstand-fund-returns": {
      "type": "http",
      "url": "https://api.fruitstand.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-fruitstand-fund-returns]
url = "https://api.fruitstand.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-fruitstand-fund-returns": {
      "type": "remote",
      "url": "https://api.fruitstand.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-fruitstand-fund-returns --url 'https://api.fruitstand.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-fruitstand-fund-returns:
    url: "https://api.fruitstand.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-fruitstand-fund-returns": {
      "Transport": "http",
      "Url": "https://api.fruitstand.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-fruitstand-fund-returns -t streamable-http -u 'https://api.fruitstand.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dev-fruitstand-fund-returns": {
      "type": "http",
      "url": "https://api.fruitstand.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-24 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-21 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-19 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-13 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-11 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-09 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (6)

### `searchFunds` (~96 tokens)

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), exchange, currency, ISIN, and the date range with return data — plus `next_cursor` for keyset paging. No performance figures here; use getTrailingReturns / getCalendarReturns for those.

Input parameters:

- `queryParams` (object, required)

### `getFund` (~92 tokens)

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 data exists. Returns 404 if the ticker is unknown. Use searchFunds to resolve a name to a code; use the returns tools for performance.

Input parameters:

- `pathParams` (object, required)
- `queryParams` (object, required)

### `getTrailingReturns` (~130 tokens)

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). Values are decimal fractions of total return, distributions reinvested (0.1234 = +12.34%); 2y and longer are annualized (CAGR). Use batchTrailingReturns for many funds.

Input parameters:

- `pathParams` (object, required)
- `queryParams` (object, required)

### `batchTrailingReturns` (~91 tokens)

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 data are omitted and order is not guaranteed, so match on `code`. Values are decimal fractions, total return, distributions reinvested. Use this to compare or screen funds.

Input parameters:

- `body` (object, required)

### `getCalendarReturns` (~104 tokens)

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, distributions reinvested (0.263 = +26.3%); `base_date`/`end_date` give the actual span (partial in launch/delist years). Use getTrailingReturns for rolling windows.

Input parameters:

- `pathParams` (object, required)
- `queryParams` (object, required)

### `batchCalendarReturns` (~91 tokens)

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 data are omitted and order is not guaranteed, so match on `code`. Values are decimal fractions, total return, distributions reinvested. Use this to compare funds across a year.

Input parameters:

- `body` (object, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-fruitstand-fund-returns/api#diagnostics

## Score history

- 2026-09-24: 79
- 2026-09-23: 78
- 2026-09-22: 78
- 2026-09-21: 78
- 2026-09-20: 77
- 2026-09-19: 77
- 2026-09-18: 76
- 2026-09-17: 76
- 2026-09-16: 75
- 2026-09-15: 75
- 2026-09-14: 74
- 2026-09-13: 74
- 2026-09-12: 73
- 2026-09-11: 73
- 2026-09-10: 72
- 2026-09-09: 72
- 2026-09-08: 71
- 2026-09-07: 71
- 2026-09-06: 33
- 2026-09-05: 33
- 2026-09-04: 33
- 2026-09-03: 33
- 2026-09-02: 33

## Common questions

### What is the Fruit Stand Fund Returns MCP server?

Fruit Stand Fund Returns is an MCP server listed in the public MCP registry as dev.fruitstand/fund-returns. Trailing & calendar-year returns for 32,000+ US mutual funds & ETFs, fund performance by ticker. This page covers its hosted endpoint (https://api.fruitstand.dev/mcp).

### Is the Fruit Stand Fund Returns MCP server safe to use?

Fruit Stand Fund Returns scores 79 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Fruit Stand Fund Returns MCP server expose?

Fruit Stand Fund Returns exposes 6 tools: searchFunds, getFund, getTrailingReturns, batchTrailingReturns, getCalendarReturns, batchCalendarReturns. Their descriptions and schemas cost roughly 604 tokens of context every time the server is loaded.

### Does the Fruit Stand Fund Returns MCP server require authentication?

Yes. Fruit Stand Fund Returns asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the Fruit Stand Fund Returns MCP server still maintained?

Fruit Stand Fund Returns is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://api.fruitstand.dev/mcp
- Authorisation metadata: https://api.fruitstand.dev/.well-known/oauth-protected-resource/mcp
- Repository: https://github.com/fruitstanddev/fruitstand-mcp
- Website: https://fruitstand.dev/
- Changelog RSS feed: https://verifymcp.io/servers/dev-fruitstand-fund-returns/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-fruitstand-fund-returns/api.json
- HTML version of this page: https://verifymcp.io/servers/dev-fruitstand-fund-returns/api