{
  "markdown": "# @pipeworx/colombia-secop\n\nColombia SECOP MCP — Colombian government procurement (tenders and awarded contracts) from the keyless Socrata API at datos.gov.co.\n\nPart of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 1476+ live data sources.\n\n## Tools\n\n- `colombia_search_contracts(query, entity, supplier, supplier_nit, contract_type, include_unsigned, limit)` — awarded contracts (SECOP II \"Contratos electrónicos\", dataset `jbjy-vk9h`). Returns contract id, object, entity + entity NIT, supplier + supplier NIT, SME flag, city, UNSPSC category, value and amount paid (COP), type, modality, status, signing date.\n- `colombia_search_processes(query, entity, contract_type, include_unpublished, limit)` — tenders (SECOP II \"Procesos de Contratación\", dataset `p6dx-8zbt`). Returns process id, name, entity + entity NIT, base price, award value, awarded supplier, type, modality, status, publication date.\n\n## Auth\n\nKeyless. `_apiKey` is optional — pass your own [Socrata app token](https://www.datos.gov.co/profile/edit/developer_settings) only if you want higher rate limits. There is no platform key and none is needed; a call with no token works.\n\n## Gotchas\n\n**Drafts share the table with real contracts, and they sort first.** 424,153 contract rows have a NULL `fecha_de_firma`, and Socrata orders NULLs *first* on `ORDER BY ... DESC`. An unguarded \"most recent\" search therefore returns nothing but unsigned `Borrador` / `enviado Proveedor` rows. Both tools require the sort column to be non-NULL by default; `include_unsigned` / `include_unpublished` opt back in.\n\n**Use `contract_type`, not `query`, for a contract category.** `tipo_de_contrato` is a clean 24-value facet (`Obra` ≈ 52k contracts against ≈ 5.1M `Prestación de servicios`). Passing `\"obra\"` as free text LIKE-matches service contracts that merely mention the word. The argument accepts the Spanish facet values and maps common English ones (`works`/`construction` → `Obra`, `consulting` → `Consultoría`, `supplies` → `Suministros`); an unrecognised value returns `unknown_contract_type` listing the valid set rather than a silent zero.\n\n**Text is published in Spanish.** An English `query` matches nothing even when the data is present, so a zero-result response carries a hint saying so.\n\n**Socrata reports a throttle as `403 \"Invalid app_token specified\"`.** With no token sent that is the rate limit, not a credential problem — space the calls out and retry. If the caller *did* pass `_apiKey`, the pack instead reports `invalid_api_key` and tells them to drop the token, since the endpoint is keyless and retrying a bad token never succeeds.\n\n**`documento_proveedor` (supplier NIT) is the durable supplier key.** Names vary across filings; the NIT pins one company across every contract it holds. It reads `\"No Definido\"` on rows where SECOP has no value.\n\n## Data sources\n\n- Contratos electrónicos: `https://www.datos.gov.co/resource/jbjy-vk9h.json`\n- Procesos de Contratación: `https://www.datos.gov.co/resource/p6dx-8zbt.json`\n- Portal: https://www.colombiacompra.gov.co/secop/secop-ii\n\n## Quick Start\n\nAdd to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):\n\n```json\n{\n  \"mcpServers\": {\n    \"colombia-secop\": {\n      \"url\": \"https://gateway.pipeworx.io/colombia-secop/mcp\"\n    }\n  }\n}\n```\n\n### What this endpoint actually serves\n\n`tools/list` at `https://gateway.pipeworx.io/colombia-secop/mcp` returns the tools in the table\nabove **plus the shared Pipeworx meta-tools** — `ask_pipeworx`,\n`discover_tools`, `search_within`, `remember`/`recall` and the rest of the\ngateway-wide set. So the tool count you see is larger than this table: a\nsingle-pack endpoint currently lists roughly 30 shared tools alongside the\npack's own. The connection's `initialize` response states its exact scope, and\nis the authoritative answer for a given day.\n\nThis is deliberate, not multiplexing by accident. The meta-tools are what let a\nscoped connection answer a question this pack does not cover — via\n`ask_pipeworx`, which routes across the whole catalog — without you adding a\nsecond MCP server. There is currently no way to mount a pack endpoint without\nthem; if the extra schemas cost you more context than the routing is worth,\nconnect to the full gateway once rather than to several pack endpoints.\n\nOr connect to the full Pipeworx gateway to get every pack's tools listed\ndirectly, instead of just this one's:\n\n```json\n{\n  \"mcpServers\": {\n    \"pipeworx\": {\n      \"url\": \"https://gateway.pipeworx.io/mcp\"\n    }\n  }\n}\n```\n\nBoth URLs reach the same gateway and the same 1476+ data sources. The\nonly difference is which pack's tools are listed **directly**; `ask_pipeworx`\nreaches all of them from either one.\n\n## Using with ask_pipeworx\n\nInstead of calling tools directly, you can ask questions in plain English —\nthis works on the pack endpoint above as well as on the full gateway:\n\n```\nask_pipeworx({ question: \"your question about Colombia Secop data\" })\n```\n\nThe gateway picks the right tool and fills the arguments automatically.\n\n## More\n\n- [Docs and guides](https://pipeworx.io/docs)\n- [pipeworx.io](https://pipeworx.io)\n\n## License\n\nMIT\n",
  "bytes": 5148,
  "sha": "7319a0b785b5ee2bd39168574fdce49beb75c65c2f2ff123ff3af6a1ae5f38d5",
  "repo_slug": "pipeworx-io/mcp-colombia-secop",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_pipeworx_io_colombia_secop_ddef8c1b/readme"
}