In-depth architectural comparison of the Oathscore and TradeTi.me — Market Hours MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Oathscore
Finance & Fintech · Local stdio
Quality: 59/100 (Good) | Auth: No auth required
TradeTi.me — Market Hours
Finance & Fintech · Local stdio
Quality: 27/100 (Emerging) | Auth: No auth required
Verdict Summary: Choose Oathscore if you need specialized Finance & Fintech tools running via a local process. Choose TradeTi.me — Market Hours if your workspace requires Finance & Fintech integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Oathscore when:
You need dedicated capabilities in the Finance & Fintech domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Freemium).
The trust layer for AI trading agents. Real-time world state (exchange status, VIX/VVIX/SKEW, economic events) in one call, plus independent quality ratings (0-100) for financial data APIs. 8 MCP tools.
Read-only trading hours for 30 stock exchanges — open now, next open, holidays, sessions.
Oathscore is categorized under Finance & Fintech and uses a local stdio subprocess. In contrast, TradeTi.me — Market Hours belongs to Finance & Fintech using local stdio subprocess. Select Oathscore when you need capabilities focused on finance & fintech and TradeTi.me — Market Hours when you require tools for finance & fintech.