openecon-data
OpenEcon Data is an AI-assisted economic data aggregator that routes natural-language requests to multiple official data providers (e.g., FRED, World Bank, IMF, Eurostat, BIS, Comtrade, plus crypto/currency sources). It provides charts and exports, and exposes access to agents via an MCP server endpoint over SSE. It also includes a web UI (data.openecon.ai/chat).
Score Breakdown
⚙ Agent Friendliness
🔒 Security
TLS is implied by HTTPS for the MCP endpoint. Authentication strength and scope granularity are not clearly documented in the provided excerpt; OpenRouter API key and optional Supabase credentials are mentioned, but how secrets are handled/logged is not shown. Dependency and CVE hygiene cannot be assessed from the provided manifest/README excerpt; a security policy file is referenced, but details are not included.
⚡ Reliability
Best When
You want agent-friendly, source-attributed economic time-series retrieval via MCP, especially when natural-language querying and multi-provider coverage matter.
Avoid When
You cannot tolerate reliance on an LLM parsing step (for intent/country/indicator/date extraction) or you need strict, audited compliance assurances without reviewing the implementation.
Use Cases
- • Enable an MCP-compatible AI agent to fetch verified economic indicators by asking in natural language
- • Cross-country comparisons (e.g., G7/BRICS/EU style groupings) with time-series charts
- • Indicator discovery (search among ~330K indexed indicators) and retrieving source-attributed data
- • Exporting datasets as CSV/JSON and other formats for analysis and research workflows
- • Self-hosting an economic data backend with provider routing and normalization
Not For
- • Use as a fully generic economic database without understanding its concept-to-provider routing behavior
- • Highly regulated environments without validating security posture of LLM parsing, logs, and auth configuration
- • Applications that require a documented, stable public REST/OpenAPI contract (beyond the MCP/web UI described)
Interface
Authentication
Docs mention MCP clients adding the server (e.g., Claude/Codex). The install/self-host guide implies an OpenRouter API key is required and Supabase is optional; exact MCP auth mechanism/scopes are not specified in the provided README excerpt.
Pricing
The README describes an OpenRouter API key requirement for LLM parsing and optional provider API keys. It does not specify pricing tiers/credits for OpenEcon itself in the provided content.
Agent Metadata
Known Gotchas
- ⚠ MCP endpoint is described over SSE; agent clients must support SSE transport.
- ⚠ The system relies on an LLM parsing/router step (OpenRouter) for intent/country/indicator/date extraction; ambiguous queries may lead to incorrect routing even if provider data retrieval is correct.
- ⚠ Because the repo content provided is high-level, the exact MCP tool names, parameters, and error payload schema are not visible here—agents should validate tool contracts against actual MCP schema at runtime.
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for openecon-data.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-30.