mcp-Uruguay
Related Servers
Alternatives to mcp-Uruguay
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP server for querying real-time Argentine economic data, including dollar exchange rates, inflation, country risk, foreign currencies, and more.MIT
- AlicenseAqualityDmaintenanceMCP server for accessing Chilean Central Bank economic data (UF, UTM, IPC, exchange rates, IMACEC, GDP) via official APIs, including series lookup and metadata tools.3MIT
- AlicenseNot gradedqualityCmaintenanceMCP server exposing Montevideo public transportation data (STM) as tools for AI assistants, enabling natural language queries about routes, stops, arrivals, and trip planning.8 npm1MIT
- AlicenseAqualityDmaintenanceMCP server for accessing Uruguay's IMPO open data API with SQLite caching. Provides tools to retrieve legal norms, search regulations, and access schema documentation from Uruguay's official legal database.4MIT
- AlicenseNot gradedqualityNot gradedmaintenanceAn MCP server deployed on Cloudflare Workers that provides access to Uruguayan legislation from the official IMPO database. It enables users to search for legal norms, retrieve full texts, and query specific articles from laws, decrees, and the constitution.-
- 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
TDQS
Scored across 29 tools
Most tools target a clearly distinct dataset or action (procurement vs exchange rate vs river level vs elections), and descriptions actively disambiguate adjacent pairs (cotizacion vs cotizacion_mensual, combustible_ancap vs ventas_combustible vs paridad_combustibles, nivel_rio vs nivel_rio_comparado). The weakest seams are the weather pair (observaciones_inumet vs clima — different networks, easy to mix up) and the economic tools (pesos_constantes vs variacion_real vs ipc_argentina/ipca_brasil) which an agent must read carefully to choose between.
All names are lowercase snake_case Spanish with no accents, which is a consistent surface style. However the grammatical pattern is mixed: most are bare nouns (cotizacion, leyes, semana) while a few are verb-first (buscar_indicador_social, geocodificar_direccion, validar_documento, ubicar_punto), so the agent cannot infer a predictable verb_noun convention.
29 tools is on the heavy side of the scale and the surface is a grab bag of unrelated domains stitched together (meteorology, fuel, parliament, geocoding, ISO week numbers). Almost every tool maps to a real distinct dataset so few are truly redundant, but trivia like semana and diagnostico sit oddly next to substantive datasets and push the set past a comfortably scannable size.
Coverage within each domain is decent (read-only series, comparisons, geocoding, validation), but there are notable dead ends: recursos_catalogo requires a dataset identifier with no companion tool to search or list catalogodatos.gub.uy datasets, and there is no weather forecast or any write/lifecycle operation. Election and indicator tools also depend on discovery tools that only partially bridge the gap (buscar_indicador_social exists, but no equivalent search for datasets or elections).