Polygon.io MCP Server

What is Massive.com MCP Server?

The Massive.com MCP Server gives LLMs access to the full Massive.com financial data API through three composable tools: search, call, and query. Data can be stored in an in-memory SQLite database and enriched with built-in financial functions. It is for developers who want to integrate market data into AI assistants.

How to use Massive.com MCP Server?

Install with uv tool install "mcp_massive @ git+https://github.com/massive-com/[email protected]" and set the MASSIVE_API_KEY environment variable. Then register the server with Claude Code (claude mcp add massive...) or add it to your Claude Desktop configuration. The LLM uses three tools: search_endpoints to discover endpoints and functions, call_api to fetch data, and query_data to run SQL against stored results.

Key features of Massive.com MCP Server

• Three tools cover the entire Massive.com API surface.
• Built-in financial functions for Greeks, returns, and technicals.
• Dynamic endpoint indexing via llms.txt stays current automatically.
• In-memory SQLite database for storing and querying results.
• Multiple transport options: stdio, SSE, and streamable-http.

Use cases of Massive.com MCP Server

• Fetch real-time stock, option, forex, crypto, and futures aggregates.
• Compute Black-Scholes option Greeks and moving averages.
• Analyze historical trades, quotes, and market snapshots.
• Retrieve financial fundamentals, dividends, splits, and analyst ratings.

FAQ from Massive.com MCP Server

What data does the server cover?

Stock, options, forex, crypto, and futures aggregates; real-time and historical trades and quotes; market snapshots, gainers/losers; ticker details; dividends, splits, IPOs; financial fundamentals; analyst ratings and news; treasury yields, inflation data; market status and holidays.

What are the prerequisites?

Python 3.12+, a Massive.com API key, and Astral UV v0.4.0+.

What environment variables are required?

MASSIVE_API_KEY is required. Optional: MCP_TRANSPORT (default stdio), MASSIVE_API_BASE_URL, MASSIVE_LLMS_TXT_URL, MASSIVE_MAX_TABLES (default 50), MASSIVE_MAX_ROWS (default 50000).

How does the server handle my API key?

The API key is used only for authenticating requests to Massive.com. No personal data is stored or cached; all requests are proxied directly.

What transport protocols are supported?

STDIO by default. SSE and streamable-http are also supported via the --transport CLI argument or MCP_TRANSPORT environment variable.