Model Context Protocol moderate risk

Polygon

The Massive.com MCP server provides access to real-time and historical financial market data via an LLM-friendly interface, using an API key for authentication.

Connections & Capabilities

Connects To

GitHub

Capabilities

read

Quickstart

Install

npm install -g @anthropic-ai/claude-code

Config

{
    "mcpServers": {
        "massive": {
            "command": "<path_to_your_uvx_install>/uvx",
            "args": [
                "--from",
                "git+https://github.com/massive-com/mcp_massive@v0.6.0",
                "mcp_massive"
            ],
            "env": {
                "MASSIVE_API_KEY": "<your_api_key_here>",
                "HOME": "<your_home_directory>"
            }
        }
    }
}

Exposed MCP Tools (7)

safe

get_aggs

Retrieves stock aggregates (OHLC) data for a specific ticker.

Read-only operation, retrieves historical data.

safe

list_trades

Lists historical trade data for a given ticker.

Read-only operation, retrieves historical data.

safe

get_last_trade

Gets the latest trade for a specified symbol.

Read-only operation, retrieves real-time data.

safe

list_ticker_news

Retrieves recent news articles related to specific tickers.

Read-only operation, retrieves news data.

safe

get_snapshot_ticker

Provides the current market snapshot for a ticker.

Read-only operation, retrieves real-time data.

safe

get_market_status

Retrieves the current market status and trading hours.

Read-only operation, retrieves market status information.

safe

list_stock_financials

Lists fundamental financial data for a specific stock.

Read-only operation, retrieves financial data.

Safety Assessment

This MCP server is relatively safe for read-only access to financial data. The primary risk is the exposure of the Massive.com API key. Ensure the API key is securely stored and managed to prevent unauthorized access. Avoid using the API in untrusted environments.

Read-only access to financial data via API
No direct write or delete operations on the server itself
API key authentication
Data requests are proxied directly to Massive.com's API

Requires a Massive.com API key, which needs to be securely managed
Potential for information disclosure if the API key is compromised
Reliance on the security of the Massive.com API and infrastructure
Exposure to external data sources introduces a risk of data integrity issues