QuantGist-mcp
https://api.quantgist.com/mcp ↗
Description
**QuantGist MCP** gives Claude and any MCP-compatible agent live macro-economic, earnings, and market data from natural language. Connect over HTTP and pass your QuantGist API key in the `X-API-Key` header (free tier: 100 calls/day — [get one free](https://quantgist.com)). ### Tools (10) - **Macro & events** — `get_upcoming_events`, `get_events_range`, `get_economic_calendar`, `get_event_detail` - **Earnings** — `get_earnings_upcoming`, `get_earnings_for_ticker`, `get_earnings_summary`, `get_earnings_surprises`, `get_earnings_season_summary` - **Markets** — `get_markets_overview` Ask things like *"What high-impact events are in the next 4 hours?"*, *"Show me AAPL's earnings beat rate"*, or *"Give me a quick market overview."* QuantGist provides trading-intelligence context — not order execution or buy/sell advice. **Docs:** https://quantgist.com/docs/mcp · **API keys:** https://quantgist.com · **PyPI:** `pip install quantgist-mcp`
What our measurements say
QuantGist-mcp is a remote MCP server published at api.quantgist.com. It has been probed 6 times since 9/10/2026. It answered in 6 of them (100.0%), a near-uninterrupted record. Median response time is 558 ms, a delay an agent will notice. It exposes a broad tool surface of 22 tools. On the protocol side it still runs 2025-11-25 and has not moved to the newer spec.
Agent readability score
Can an LLM agent pick the right tool here — names, descriptions and parameter clarity are assessed.
Agent readability score
Strengths
- Tool names are descriptive and indicate their primary purpose (e.g., 'get_upcoming_events' clearly signals event retrieval).
- Descriptions often explain use cases (e.g., 'get_earnings_summary' clarifies its purpose in analyzing beat/miss rates).
Weaknesses
- Some parameter definitions are ambiguous (e.g., 'get_events_range' lacks explicit schema for 'impact level' filtering).
- Redundancy between tools like 'get_upcoming_events' and 'get_events_range' may confuse agents about when to use each.
get_events_range— Parameter 'impact level' filtering lacks explicit schema definition.get_upcoming_events— No explicit mention of rate limits or error handling in description.get_earnings_for_ticker— Input schema for 'ticker' parameter is not clearly defined (e.g., format, required fields).
Verdict
Event narrative
Risk: medium
- 2026-09-10T21:16:35.016Z — era changed from 'auth-gated' to 'legacy' · indicates compliance framework transition
- 2026-09-11T07:35:54.413Z — complianceScore set to 100 (previously null) · confirms full regulatory compliance achieved
Advice
Schema compliance
tools/list structure, inputSchema validity, and a functional smoke test — the components of the 0-100 score.
- tools/list schema valid
- inputSchema is valid JSON Schema
- Smoke test not run this round
- Cold-start: cold 178ms → warm 176ms (penalty 2ms)
Availability history
Event log
Derived by comparing consecutive probes — changes in era, protocol version, build and reachability.
- Server build: — → 1.28.1
- Supported versions: — → 2025-11-25
- Era changed: Auth-gated → Legacy
- Added to watch — era: Auth-gated
Get your badge
Add this badge to your README — it updates automatically as measurements change.
[](https://mcpmetrics.io/servers/quantgist-quantgist-mcp)<a href="https://mcpmetrics.io/servers/quantgist-quantgist-mcp"><img src="https://mcpmetrics.io/badge/quantgist/quantgist-mcp/era.svg" alt="mcpmetrics"></a>You are seeing the last 7 days. Sign up for the full history. Which check failed and why is in the dashboard.
Sign up free to see