Skip to main content
Glama
jrierapeiro

Finance MCP Server

by jrierapeiro
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
JavaScript
Remote

Finance MCP Server

A Model Context Protocol (MCP) server that provides access to financial market data using the yfinance API.

Features

  • Fetches real-time financial market data for stock tickers

  • Supports common stocks like AAPL, GOOGL, MSFT, AMZN, TSLA

  • Provides current price, day change percentage, 52-week high/low, P/E ratio, market cap, and dividend yield

  • Includes news headlines related to the requested ticker

Running with Docker Compose

To start the MCP server using Docker Compose:

docker-compose up -d

The server will be accessible on port 3000.

Development

To run in development mode with auto-restart:

docker-compose up

Usage

The server implements the MCP protocol and can be used with MCP-compatible clients that support the fetchMarketData tool.

Example Query

Example of how to query the server for Apple (AAPL) stock data using an MCP client:

{
  "method": "tools/call",
  "params": {
    "name": "fetchMarketData",
    "arguments": {
      "ticker": "AAPL"
    }
  }
}

Example Response

This query would return market data in the following format:

{
  "success": true,
  "data": {
    "current_price": 172.35,
    "day_change_pct": 0.84,
    "52w_high": 198.23,
    "52w_low": 124.17,
    "pe_ratio": 28.5,
    "market_cap": 2700000000000,
    "dividend_yield_pct": 0.55,
    "currency": "USD",
    "news_headlines": [
      "Apple Report Shows Strong Growth in Services Segment",
      "AAPL Earnings Beat Estimates as iPhone Sales Surpass Expectations"
    ],
    "news": [
      {
        "title": "Apple Report Shows Strong Growth in Services Segment",
        "publisher": "Financial Times",
        "link": "https://example.com/news1",
        "time": "2023-06-15T10:30:00Z"
      }
    ]
  }
}

Testing

This project now includes comprehensive test coverage using vitest:

Running Tests

  • npm test - Run all tests once

  • npm run test:watch - Run tests in watch mode for development

Test Structure

  • Unit tests for yfinance module in test/yfinance.test.js

  • Integration tests for MCP server functionality in test/integration.test.js

Usage Examples

1. Fetch Single Stock Market Data

{
  "method": "tools/call",
  "params": {
    "name": "fetchMarketData",
    "arguments": {
      "ticker": "AAPL"
    }
  }
}

Response:

{
  "success": true,
  "data": {
    "current_price": 172.35,
    "day_change_pct": 0.84,
    "52w_high": 198.23,
    "52w_low": 124.17,
    "pe_ratio": 28.5,
    "market_cap": 2700000000000,
    "dividend_yield_pct": 0.55,
    "currency": "USD",
    "news_headlines": [
      "Apple Report Shows Strong Growth in Services Segment",
      "AAPL Earnings Beat Estimates as iPhone Sales Surpass Expectations"
    ],
    "news": [
      {
        "title": "Apple Report Shows Strong Growth in Services Segment",
        "publisher": "Financial Times",
        "link": "https://example.com/news1",
        "time": "2023-06-15T10:30:00Z"
      }
    ]
  }
}

2. Fetch Multiple Stocks Market Data

{
  "method": "tools/call",
  "params": {
    "name": "fetchMultipleMarketData",
    "arguments": {
      "tickers": ["AAPL", "MSFT", "GOOGL"]
    }
  }
}

Response:

{
  "success": true,
  "data": [
    {
      "ticker": "AAPL",
      "data": { /* similar to fetchMarketData response */ },
      "error": null
    },
    {
      "ticker": "MSFT",
      "data": { /* similar to fetchMarketData response */ },
      "error": null
    },
    {
      "ticker": "GOOGL", 
      "data": { /* similar to fetchMarketData response */ },
      "error": null
    }
  ]
}

3. Search Stocks by Query

{
  "method": "tools/call",
  "params": {
    "name": "searchStocks",
    "arguments": {
      "query": "Apple"
    }
  }
}

Response:

{
  "success": true,
  "data": [
    {
      "ticker": "AAPL",
      "name": "Apple Inc.",
      "exchange": "NMS",
      "type": "EQUITY",
      "market_cap": 2700000000000,
      "price": 172.35
    }
  ]
}

4. Get Market Overview for Indices

{
  "method": "tools/call",
  "params": {
    "name": "getMarketOverview",
    "arguments": {}
  }
}

Response:

{
  "success": true,
  "data": [
    {
      "index": "SP500",
      "current_value": 4500.12,
      "change_amount": 50.34,
      "change_percentage": 1.13
    },
    {
      "index": "DJI",
      "current_value": 34000.56,
      "change_amount": -120.78,
      "change_percentage": -0.35
    },
    {
      "index": "IXIC",
      "current_value": 14000.33,
      "change_amount": 85.45,
      "change_percentage": 0.62
    }
  ]
}

Running the Server

To run the MCP server locally and test tools:

  1. Install dependencies:

    npm install

  2. Start the server in development mode:

    npm run dev

  3. The server will be accessible through MCP client implementations.

Testing Tools Locally

This server uses stdio transport (JSON-RPC over stdin/stdout), not HTTP. Below are ways to test the tools directly.

Using MCP Inspector (Web UI)

The official MCP Inspector provides a web interface to test all tools:

npx @modelcontextprotocol/inspector node server/src/index.js

Then open the provided URL (usually http://localhost:5173) in your browser.

Using JSON-RPC over stdin/stdout

Pipe JSON-RPC messages directly to the server process:

List available tools:

echo '{"jsonrpc":"2.0","id":1,"method":"tools/list"}' | node server/src/index.js

Call fetchMarketData:

echo '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"fetchMarketData","arguments":{"ticker":"AAPL"}}}' | node server/src/index.js

Call fetchMultipleMarketData:

echo '{"jsonrpc":"2.0","id":3,"method":"tools/call","params":{"name":"fetchMultipleMarketData","arguments":{"tickers":["AAPL","MSFT","GOOGL"]}}}' | node server/src/index.js

Call searchStocks:

echo '{"jsonrpc":"2.0","id":4,"method":"tools/call","params":{"name":"searchStocks","arguments":{"query":"Apple"}}}' | node server/src/index.js

Call getMarketOverview:

echo '{"jsonrpc":"2.0","id":5,"method":"tools/call","params":{"name":"getMarketOverview","arguments":{}}}' | node server/src/index.js

Note: The server outputs a JSON-RPC response per request. The first response will include initialization data (protocol version, server capabilities), and subsequent responses will contain the tool results. Use jq to pretty-print: echo '...' | node server/src/index.js | jq .

Integrating with Odysseus

This server can be added to Odysseus as a custom MCP server (admin access required).

Via Settings UI

Go to Settings → MCP management and add a new server:

Field

Value

Name

Finance MCP

Transport

stdio

Command

node

Args

["/full/path/to/finance-mcp/server/src/index.js"]

Via API

curl -X POST http://your-odysseus-host/api/mcp/servers \
  -d 'name=Finance+MCP' \
  -d 'transport=stdio' \
  -d 'command=node' \
  -d 'args=["/full/path/to/finance-mcp/server/src/index.js"]'

Changelog

Improvements made by AI code review (big-pickle):

  • getMarketOverview now accepts custom indices — The MCP tool's optional indices parameter is now wired through to the underlying function. Supports short names (SP500, DJI, IXIC) and direct Yahoo symbols (^GSPC, ^DJI, ^IXIC).

  • Added getCompanyInfo tool — New Phase 4 tool returning company profile, officers, financial metrics, and valuation data via quoteSummary.

  • Fixed searchStocks options — Changed invalid { count: 20 } to valid { quotesCount: 20 } matching the library's SearchOptions interface.

  • Removed dead code — Deleted orphaned prototypes (simple-server.js, yfinance-mcp-server.js, index.js), artifact server/node_modules/ and server/package-lock.json, unused express dependency, and no-op server/config.js.

  • Rewrote tests with mocking — 29 unit tests now mock yahoo-finance2 so they're fast and reliable (no network calls). Covers all four data functions plus getCompanyInfo.

  • Switched test environment — Changed from happy-dom to node in vitest config (server project, not a browser/DOM project).

  • Committed package-lock.json — Removed from .gitignore so installs are reproducible.

  • Updated task tracking — All 12 task files now reflect actual completion status. Development plan annotated with checkmarks.

  • Improved MCP response format for LLM agents — Switched from flat JSON.stringify(result) to pretty-printed JSON.stringify(result, null, 2) and added isError: true on error responses, making tool outputs easier for agent frameworks like Odysseus to parse.