Oathscore vs Mrmarket.ai — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Oathscore vs Mrmarket.ai
In-depth architectural comparison of the Oathscore and Mrmarket.ai 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
Mrmarket.ai
Finance & Fintech · Remote HTTP/SSE
Quality: 51/100 (Good) | Auth: No auth required
Verdict Summary: Choose Oathscore if you need specialized Finance & Fintech tools running via a local process. Choose Mrmarket.ai if your workspace requires Finance & Fintech integration with remote web transport. 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.
Analytical engine for US-listed equities: screens, rankings, and event studies in plain English.
Oathscore is categorized under Finance & Fintech and uses a local stdio subprocess. In contrast, Mrmarket.ai belongs to Finance & Fintech using remote streaming HTTP/SSE transport. Select Oathscore when you need capabilities focused on finance & fintech and Mrmarket.ai when you require tools for finance & fintech.
The workhorse. A natural-language financial question in; structured rows and columns out. Screens, rankings, comparisons, time-series, cohort studies, and event studies are all single calls.
fetch_page
The continuation. When a `query_data` result is too large for one response, page 1 comes back with a `pagination.next_cursor`; pass that cursor to `fetch_page` to retrieve the rest. It runs no new query, so it never costs credits — the original `query_data` is charged once.
describe_data
The data catalog. Browse categories and fields, or search for a specific metric, before composing a question.
get_symbols
Fast ticker, sector, and industry resolution. Name to ticker, sector membership, or the full universe in under 50ms.
getting_started
A structured orientation tour with verified example prompts, grouped by use case.
recent_queries
Your recent queries, for context and re-runs.
get_account_status
Connected account, plan tier, credit balance, and rate limits. A useful first call in any new session.
report_issue
Flag a result that looks wrong or a feature that is missing. Pass the `query_id` from the response so the trace can be investigated.