Fruit Stand Fund Returns
REMOTE · API.FRUITSTAND.DEV · SCANNED SEP 24
Trailing & calendar-year returns for 32,000+ US mutual funds & ETFs — fund performance by ticker.
Available components
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. How we score → Why this is hard to score →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 604 tokens (~100/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management57
- Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
remote · api.fruitstand.dev
claude mcp add --transport http dev-fruitstand-fund-returns 'https://api.fruitstand.dev/mcp'
{
"mcpServers": {
"dev-fruitstand-fund-returns": {
"url": "https://api.fruitstand.dev/mcp"
}
}
} {
"servers": {
"dev-fruitstand-fund-returns": {
"type": "http",
"url": "https://api.fruitstand.dev/mcp"
}
}
} [mcp_servers.dev-fruitstand-fund-returns] url = "https://api.fruitstand.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-fruitstand-fund-returns": {
"type": "remote",
"url": "https://api.fruitstand.dev/mcp",
"enabled": true
}
}
} openclaw mcp add dev-fruitstand-fund-returns --url 'https://api.fruitstand.dev/mcp' --transport streamable-http
mcp_servers:
dev-fruitstand-fund-returns:
url: "https://api.fruitstand.dev/mcp" {
"McpServers": {
"dev-fruitstand-fund-returns": {
"Transport": "http",
"Url": "https://api.fruitstand.dev/mcp"
}
}
} assistant mcp add dev-fruitstand-fund-returns -t streamable-http -u 'https://api.fruitstand.dev/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 24 Sept 26 +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.
- 21 Sept 26 +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.
- 19 Sept 26 +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.
- 17 Sept 26 +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.
- 15 Sept 26 +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.
- 13 Sept 26 +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.
- 11 Sept 26 +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.
- 9 Sept 26 +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.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 24 Sept 2026 · Probed https://api.fruitstand.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.fruitstand.dev | CN=WE1,O=Google Trust Services,C=US | 24 Aug 2026 | 22 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 87f3ba0c9bd3a600efade610b9f4606 |
| SANs: api.fruitstand.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.fruitstand.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| fruitstand.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.fruitstand.dev/mcp | Verified | 200 | |
| http (plaintext) | http://api.fruitstand.dev/mcp | HTTPS enforced | 301 | https://api.fruitstand.dev/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
batchCalendarReturns ~91
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.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | yes | – |
No output schema declared.
No examples provided.
batchTrailingReturns ~91
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.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | yes | – |
No output schema declared.
No examples provided.
getCalendarReturns ~104
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.
| Name | Type | Req | Description |
|---|---|---|---|
| pathParams | object | yes | – |
| queryParams | object | yes | – |
No output schema declared.
No examples provided.
getFund ~92
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.
| Name | Type | Req | Description |
|---|---|---|---|
| pathParams | object | yes | – |
| queryParams | object | yes | – |
No output schema declared.
No examples provided.
getTrailingReturns ~130
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.
| Name | Type | Req | Description |
|---|---|---|---|
| pathParams | object | yes | – |
| queryParams | object | yes | – |
No output schema declared.
No examples provided.
searchFunds ~96
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.
| Name | Type | Req | Description |
|---|---|---|---|
| queryParams | object | yes | – |
No output schema declared.
No examples provided.
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.