Fund and ETF data MCP server: seven read-only tools for assistants and agents

What the server is

A remote MCP server (Model Context Protocol, the open standard AI apps use to call tools) at https://fundfactsapi.com/api/mcp: nothing to install or host. It reads the same 24-hour store as the REST API, with figures from each fund house's factsheet, KID, holdings and NAV files and dataAsOf, the date of the figures.

• Authentication: Claude, ChatGPT and Claude Code sign in with the FundFacts account (OAuth 2.1, PKCE, dynamic client registration); other clients send an API key as Authorization: Bearer ffk_…. OAuth tokens only work on the MCP server.
• Cards: in ChatGPT and in Claude on the web and desktop, results render as interactive cards (MCP Apps); elsewhere, the same figures come as text.

The seven tools

All seven only read data. A fund nobody asked for in the last 24 hours is read from its documents on demand, typically in 15–90 seconds.

A tour prompt explains the service on the example fund IE00B4L5Y983 (iShares Core MSCI World UCITS ETF), preloaded and not counted. search_funds also matches the tickers of the listed ETFs it knows, such as IWDA or VWCE.

Connect it in five steps

1. Create a FundFacts account. Sign up at /signup with an e-mail address or Google. The Free plan needs no card and gives 15 lookups a month.
2. Choose how the client signs in. Claude, ChatGPT and Claude Code (through /mcp) sign in with the account. For Cursor, VS Code, Windsurf, Codex or a script, create an API key in the dashboard, one per tool so each can be revoked alone.
3. Add the server. Give the client https://fundfactsapi.com/api/mcp with the configuration below. Where a client asks for an OAuth client ID and secret, leave them empty: it registers itself.
4. Check the tools. The client lists seven tools. In Claude Code, /mcp shows the server and its status; Cursor, VS Code and Windsurf show it in their MCP settings.
5. Ask about a fund. Start with the example fund IE00B4L5Y983, which is not counted, or ask for a tour of FundFacts.

Configuration by client

Claude Code

bash
claude mcp add --transport http fundfacts https://fundfactsapi.com/api/mcp

Then /mcp in a session to sign in. With an API key instead:

bash
claude mcp add --transport http fundfacts https://fundfactsapi.com/api/mcp --header "Authorization: Bearer ffk_your_api_key"

Cursor

In .cursor/mcp.json (or ~/.cursor/mcp.json for every project):

json
{
  "mcpServers": {
    "fundfacts": {
      "url": "https://fundfactsapi.com/api/mcp",
      "headers": {
        "Authorization": "Bearer ffk_your_api_key"
      }
    }
  }
}

VS Code (GitHub Copilot agent mode)

In .vscode/mcp.json; VS Code asks for the key once and keeps it out of the file:

json
{
  "inputs": [
    {
      "id": "fundfacts-key",
      "type": "promptString",
      "description": "FundFacts API key",
      "password": true
    }
  ],
  "servers": {
    "fundfacts": {
      "type": "http",
      "url": "https://fundfactsapi.com/api/mcp",
      "headers": {
        "Authorization": "Bearer ${input:fundfacts-key}"
      }
    }
  }
}

Windsurf

In ~/.codeium/windsurf/mcp_config.json, where the URL key is serverUrl:

json
{
  "mcpServers": {
    "fundfacts": {
      "serverUrl": "https://fundfactsapi.com/api/mcp",
      "headers": {
        "Authorization": "Bearer ffk_your_api_key"
      }
    }
  }
}

Codex

In ~/.codex/config.toml, with FUNDFACTS_API_KEY=ffk_… exported in the shell that starts Codex:

toml
[mcp_servers.fundfacts]
url = "https://fundfactsapi.com/api/mcp"
bearer_token_env_var = "FUNDFACTS_API_KEY"

Claude and ChatGPT

Both sign in with the account: FundFacts in Claude, FundFacts in ChatGPT.

Any other client

Remote clients take the URL and the header, as for Cursor. Clients that only speak stdio, including claude_desktop_config.json, go through mcp-remote:

json
{
  "mcpServers": {
    "fundfacts": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://fundfactsapi.com/api/mcp",
        "--header",
        "Authorization: Bearer ffk_your_api_key"
      ]
    }
  }
}

What it costs

Each fund found counts as one request, like the REST API. Searches, the example fund and ISINs still loading are not counted, nor are misses, up to as many a month as the plan's allowance. Monthly prices, VAT included:

Prompts that work as they are

• "Look up IWDA with FundFacts: its ongoing charge, its ten largest holdings and the date of the figures." (search_funds, then get_fund)
• "Compare IE00B4L5Y983 and IE00B3RBWM25 on fees, 5-year returns and worst drawdown." (compare_funds from Starter; on Free, one get_fund per fund)
• "How much do IE00B4L5Y983 and IE00B3RBWM25 overlap, and which holdings do they share?" (fund_overlap, Pro and above)
• "What has the SCPI Épargne Pierre distributed over the last few years, and how full are its buildings?" (search_scpi, then get_scpi)

What it does not do

• No prices or quotes. Factsheet data re-read at most every 24 hours and a monthly performance series; prices come from a market-data API or a broker.
• Funds only. UCITS funds, ETFs, money-market funds and French SCPIs. Stocks, bonds and indices come back as not found.
• No advice. Published figures with their date; the server tells the assistant not to recommend buying or selling.
• Read-only. No tool touches your account, keys or billing.

Informational data, not investment advice. The MCP server docs cover every input, privacy and troubleshooting.