{"id":"hanlulong-openecon-data","name":"openecon-data","homepage":"https://openecon.ai","repo_url":"https://github.com/hanlulong/openecon-data","category":"ai-ml","subcategories":[],"tags":["ai","economic-data","economic-indicators","data-visualization","mcp-server","fastapi","react","fred","world-bank","imf","eurostat","bis","un-comtrade"],"what_it_does":"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).","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)"],"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.","alternatives":["fredapi / FRED directly for US-only FRED series","pandas-datareader for limited source integration","Existing MCP servers dedicated to a single provider (e.g., FRED-focused MCP servers)","Custom pipelines that call each provider API directly and map indicators via your own ontology"],"af_score":46.0,"security_score":44.5,"reliability_score":22.5,"package_type":"mcp_server","discovery_source":["github"],"priority":"high","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-03-30T15:41:38.802145+00:00","interface":{"has_rest_api":false,"has_graphql":false,"has_grpc":false,"has_mcp_server":true,"mcp_server_url":"https://data.openecon.ai/mcp","has_sdk":false,"sdk_languages":[],"openapi_spec_url":null,"webhooks":false},"auth":{"methods":["MCP access via SSE endpoint (as described for MCP clients)","Optional OpenRouter API key for LLM parsing","Optional Supabase credentials for persistent history/auth on the web app"],"oauth":false,"scopes":false,"notes":"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":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"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."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":46.0,"security_score":44.5,"reliability_score":22.5,"mcp_server_quality":70.0,"documentation_accuracy":60.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":45.0,"rate_limit_clarity":10.0,"tls_enforcement":80.0,"auth_strength":40.0,"scope_granularity":20.0,"dependency_hygiene":30.0,"secret_handling":50.0,"security_notes":"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.","uptime_documented":10.0,"version_stability":30.0,"breaking_changes_history":20.0,"error_recovery":30.0,"idempotency_support":"false","idempotency_notes":null,"pagination_style":"none","retry_guidance_documented":false,"known_agent_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."]}}