INEI MCP Server
Related Servers
Alternatives to INEI MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI agents to access economic statistics from the Central Reserve Bank of Peru, including exchange rates, interest rates, and GDP, without requiring an API key.7MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents and analysts to query UN CEPALSTAT indicators through MCP by resolving natural-language requests into statistically valid indicators and retrieving clean, decoded data with anti-hallucination safeguards.MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to discover and query official Census Bureau datasets, geography levels, aggregate statistics, FIPS codes, and population data through MCP tools and prompts.MIT
- AlicenseNot gradedqualityCmaintenanceMCP server for Peruvian public-data lookups including SUNAT RUC registrations, BCRP exchange rates, and SEACE tenders. Provides official open-data access through tools for Claude, Cursor, and other MCP clients.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to search statistical series, retrieve metadata and PDF links, and download time-series data in multiple formats through MCP tools.GPL 3.0
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to discover datasets, indicators, and geographies and retrieve INEGI Intercensal Survey estimates with statistical precision through read-only MCP tools.MIT
TDQS
Scored across 9 tools
The tool set has a major disambiguation problem due to inei_get_districts being misnamed: its description says it returns all 25 departments, not districts, making it redundant with inei_get_departments. Other tools like inei_browse_topics, inei_search_indicators, and inei_get_indicator_data have distinct roles, but the duplication causes confusion.
All tools use the 'inei_' prefix and snake_case, with a consistent verb_noun pattern (get_*, browse_*, search_*). However, inei_get_districts is misleading because it does not return districts but departments, breaking semantic consistency. inei_get_census_dashboard uses 'dashboard' instead of a data-object noun, which is a minor deviation.
With 9 tools, the set is well-scoped for a statistical API covering browsing, searching, geography listing, geography profiling, and data retrieval. Each tool has a clear purpose, and the count feels neither too sparse nor overwhelming.
The set covers the main workflows: explore topics, search indicators, retrieve data by geography, and get national summaries. It can handle department and province queries. However, the duplicate get_districts tool is unnecessary, and the API's limitation to department-level geography (no district data) is a domain constraint. Minor gaps exist (e.g., no hierarchical drill-down beyond two levels), but overall coverage is good for a read-only census API.