MCP SECOP II Colombia
Related Servers
Alternatives to MCP SECOP II Colombia
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.243 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to query Ecuador government procurement (SERCOP/Compras Públicas) data without API keys, via natural language or direct tools.273 npmMIT
- AlicenseAqualityBmaintenanceEnables an LLM to answer questions about Colombian public procurement from the SECOP II electronic contracts open dataset on datos.gov.co, with typed queries that are built into SoQL by the server. A column allowlist and local entity directory keep personal-data fields unreachable and resolve institution names to NITs, so users get aggregate contract figures without writing queries themselves.3MIT
- AlicenseAqualityAmaintenanceConnects AI assistants and agents with the Dominican Republic's public procurement transactional portal and open data API, enabling searches of tenders, contracts, bids, and suppliers, plus legal threshold calculations, proposal drafting, scoring simulations, collusion auditing, and institutional scorecards.17MIT
- AlicenseNot gradedqualityBmaintenanceEnables access to Chile's government procurement data (Mercado Público / ChileCompra) via MCP, allowing AI agents to query public procurement information.269 npmMIT
- AlicenseBqualityBmaintenanceEnables AI agents to query Paraguay's public procurement data via the official DNCP API v3 (OCDS), including tender processes, awards, contracts, suppliers, contracting entities, product catalog, and visualizations.17MIT
TDQS
Scored across 8 tools
Most tools have clearly distinct roles: search, crawl, inspect, RAG chunking, taxonomy, bridge diagnostics, feed management, and budget analysis. Some potential overlap exists between search, spider crawl, and opportunity inspection since all involve retrieving SECOP II data, but descriptions make the intended granularity reasonably clear.
All tools use the secop_ prefix and snake_case, which is highly predictable. Minor deviations appear in action-style consistency, especially secop_bridge_status and secop_spider_crawl, where the verb_noun pattern is less clean than in tools like secop_search_processes or secop_generate_rag_chunks.
Eight tools is well-scoped for an integration server covering SECOP II search, crawling, inspection, RAG preparation, taxonomy, bridge diagnostics, feed management, and budget analysis. Each tool appears to serve a distinct function rather than bloating the surface.
The surface covers the main procurement data workflows: discovery, detailed inspection, crawling, RAG chunk generation, taxonomy mapping, bridge health, feed management, and financial analysis. Minor lifecycle gaps exist, such as no update/delete for RAG feeds and no obvious dedicated contract-by-ID retrieval tool, but core workflows are represented.