mcp-contrataciones-py
Related Servers
Alternatives to mcp-contrataciones-py
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to query Colombian government procurement data via MCP tools or natural language questions.5 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables access to Chile's government procurement data (Mercado Público / ChileCompra) via MCP, allowing AI agents to query public procurement information.5 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to query Ecuador government procurement (SERCOP/Compras Públicas) data without API keys, via natural language or direct tools.4 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables access to Paraguay's government procurement and public contracts data, keyless.5 npmMIT
- AlicenseAqualityDmaintenanceAllows AI assistants to query public procurement opportunities, purchase orders, and government entities from Chile's Mercado Público (ChileCompra) API in real time.126 npm1MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI assistants to query and analyze Costa Rica's public procurement (SICOP) data, including supplier profiles, market trends, product price histories, and bid comparisons, through a suite of MCP tools.-
TDQS
Scored across 17 tools
Most tools have a clear target entity and identifier, but the licitación/proceso family overlaps: buscar_procesos, resumen_licitaciones, and contar_licitaciones all accept similar filters and differ mainly in output detail. An agent could easily pick the wrong one when trying to list or summarize tenders.
The vast majority follow a consistent 'verb_noun' snake_case pattern (obtener_*, buscar_*). The exceptions 'resumen_licitaciones' and 'contar_licitaciones' deviate slightly, but the overall convention is recognizable and predictable.
With 17 tools the server is slightly above the ideal 3-15 range, but the breadth of the public procurement domain justifies the larger surface. Each tool adds a distinct resource or aggregation, and none feel redundant enough to be removed.
The set covers the main OCDS entities: records, tenders, awards, contracts, suppliers, buyers, protests, catalog products, intentions, and reference data. For a read-only public contracting API, it offers comprehensive query coverage with no obvious dead ends.