Polygon-io MCP Server
OfficialRelated Servers
Alternatives to Polygon-io MCP Server
No user-submitted related servers found.
Related Servers
- -licenseNot gradedqualityNot gradedmaintenanceReal-time financial market data MCP server. Stocks, crypto, technicals, sentiment, FDA calendar. No API keys required.-
- AlicenseAqualityCmaintenanceMCP Server for publicly available real-time Indian Mutual Funds data127MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server providing A-share market data tools (daily OHLCV, real-time quotes, financials, northbound capital flow, sector lists) with zero dependencies, also serving as a template for building custom MCP servers.1MIT
- AlicenseBqualityDmaintenanceHigh-performance CCXT MCP server for cryptocurrency exchange integration24124 npm145MIT
- AlicenseCqualityAmaintenanceLocal paper-trading and market simulation MCP server for multi-account portfolios, advanced orders, options/futures, backtesting, alerts, and automation.60MIT
- AlicenseAqualityCmaintenanceExtensible trading-intelligence MCP server with diagnostic tools, structured logging, and tool registration; currently provides server info tool with plans for market data adapters.14 npm-
TDQS
Scored across 53 tools
Most tools have distinct purposes targeting specific asset classes (e.g., stocks, crypto, futures) or data types (e.g., aggregates, snapshots, lists), with clear boundaries. However, some overlap exists between similar 'list' and 'get' functions (e.g., list_aggs vs get_aggs) that could cause minor confusion, though descriptions help differentiate them.
Tool names follow a highly consistent verb_noun pattern throughout, using 'get_' for single-item retrieval and 'list_' for collections, with clear and descriptive nouns (e.g., get_ticker_details, list_futures_contracts). There are no deviations in naming conventions, making the set predictable and readable.
With 53 tools, the count is excessive for a single server, making it overwhelming and difficult for agents to navigate efficiently. While the domain (financial data) is broad, this many tools suggests poor scoping and could lead to usability issues, as typical well-scoped servers have 3-15 tools.
The tool surface provides comprehensive coverage for financial data retrieval, including stocks, crypto, forex, futures, and market metadata, with full CRUD-like operations (mostly read/list functions) and no apparent gaps. It supports diverse workflows from real-time quotes to historical analysis and auxiliary data like news or holidays.