FinData MCP

What is FinData MCP?

FinData MCP is a Model Context Protocol server that provides real-time and fundamental financial data through five tools covering stocks, company fundamentals, economic indicators, SEC filings, and cryptocurrencies. It is designed for AI agents and developers who need programmatic access to financial market data without managing API keys or signing up for services.

How to use FinData MCP?

Install the package using pip install findata-mcp or uvx findata-mcp. The thin client runs locally and connects to the hosted backend; when your agent calls a tool, it automatically handles a $0.01 USDC payment on Base mainnet and returns the data. No signup, API keys, or self-hosting is required.

Key features of FinData MCP

• Real-time stock quotes for NYSE/NASDAQ tickers
• Company fundamentals: revenue, P/E, market cap, sector, beta, dividend yield
• 800,000+ FRED economic indicator series (GDP, CPI, fed funds rate)
• Full text of SEC EDGAR filings (10-K, 10-Q, 8-K)
• Cryptocurrency prices, market cap, volume, and 7-day sparkline

Use cases of FinData MCP

• Building an AI assistant that retrieves live stock prices and company fundamentals
• Automating economic research by querying FRED series like GDP or CPI
• Extracting text from SEC filings for compliance or investment analysis
• Monitoring cryptocurrency market data alongside traditional financial indicators

FAQ from FinData MCP

What data sources does FinData MCP use?

It pulls real-time stock data from exchanges, economic indicators from the FRED database, and SEC filings from EDGAR. Cryptocurrency data comes from market aggregators.

Do I need an API key or sign up to use it?

No. FinData MCP requires no API keys, signup, or self-hosting. Payments are handled automatically per tool call via x402.

What are the runtime dependencies?

Python 3.8+ is required. The package can be installed via pip or run with uvx. It communicates with a hosted backend over the internet.

How much does each tool call cost?

Each tool invocation costs $0.01 USDC on Base mainnet, handled automatically by the x402 payment system.

What transports and authentication are supported?

The server uses HTTP to connect to the hosted backend. Authentication is handled through the x402 payment protocol—no manual credential management needed.