openfolio-ro-mcp
Related Servers
Alternatives to openfolio-ro-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceEnables MCP clients to securely access read-only Psagot Trade account and market information through authenticated HTTP endpoints. It exposes only read-only tools, with no trade-submission capabilities.-
- FlicenseAqualityCmaintenanceEnables read-only, bounded quantitative-research workflows with schema compatibility checking and server capability discovery, without exposing market data or live trading.1-

FxSocket MCPofficial
AlicenseNot gradedqualityBmaintenanceEnables MCP clients to read MetaTrader 4 and 5 account data, including balances, open positions, closed trades, quotes, symbol specifications, and price history, without placing, modifying, or closing orders.MIT- AlicenseNot gradedqualityBmaintenanceEnables authenticated, read-only access to stored account, options, and monitoring data for bounded research. It also permits pausing/resuming monitoring, with no brokerage write or proxy capabilities.MIT
- FlicenseNot gradedqualityCmaintenanceEnables read-only access to Addepar portfolio and ownership data for financial reporting, with transparent provenance caveats and compliance-oriented audit logging.-
- AlicenseBqualityCmaintenanceEnables read-only access to Questrade accounts, portfolios, market data, transactions, technical analysis, and order history through MCP.11MIT
TDQS
Scored across 4 tools
Each tool targets a distinct resource: catalog for discovery, holdings for positions, grid for grid performance, logs for system logs. There is zero overlap in purpose, so an agent can reliably select the right tool.
All tools follow the consistent pattern 'ro_<noun>' (ro_catalog, ro_holdings, ro_grid, ro_logs), making the naming predictable and easy to infer.
With just 4 tools, the set is tightly scoped to the read-only portfolio data domain. Each tool serves a clear, non-redundant purpose, and the count is well within the typical ideal range.
The tools cover the core read-only needs: discovery (catalog), holdings, grid positions, and logs. The catalog provides awareness of additional HTTP-only endpoints, so agents can at least know about them. Minor gap: some read-only data (e.g., individual grid trades) is not directly accessible via MCP, but the presence of the catalog mitigates this.