# Colombia Secop (npm · @pipeworx/mcp-colombia-secop)

Colombia SECOP MCP — Colombian government procurement (public contracting).

- Trust score: 80/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 77/100, [markdown](https://verifymcp.io/servers/pipeworx-io-colombia-secop/colombia-secop-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-colombia-secop/colombia-secop-mcp)
- npm · `@pipeworx/mcp-colombia-secop`: 80/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-colombia-secop/pipeworx-mcp-colombia-secop.md), [page](https://verifymcp.io/servers/pipeworx-io-colombia-secop/pipeworx-mcp-colombia-secop)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-colombia-secop`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-colombia-secop).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 4 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 54/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1288 tokens (~644/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Colombia Secop MCP server?

Colombia Secop runs locally as an npm package, launched with npx -y @pipeworx/mcp-colombia-secop. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add pipeworx-io-colombia-secop -- npx -y @pipeworx/mcp-colombia-secop
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-colombia-secop": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-colombia-secop"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-colombia-secop": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-colombia-secop"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-colombia-secop -- npx -y @pipeworx/mcp-colombia-secop
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-colombia-secop": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-colombia-secop"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-colombia-secop --command npx --arg -y --arg @pipeworx/mcp-colombia-secop
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-colombia-secop:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-colombia-secop"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-colombia-secop": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-colombia-secop"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-colombia-secop -t stdio -c npx -a -y @pipeworx/mcp-colombia-secop
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-colombia-secop": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-colombia-secop"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-03 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 79, +27)

- [security improvement] Malware scan: unverified → pass
- [security improvement] Known CVEs: unverified → pass
- [functional improvement] Dependency health: unverified → pass

### 2026-10-31 (score 52, −25)

- [security regression] Malware scan: pass → unverified
- [security regression] Known CVEs: pass → unverified
- [functional regression] Security disclosure: unverified → fail
- [functional regression] Dependency health: pass → unverified
- [functional improvement] Stability: unverified → 0.07
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-29 (score 77)

First indexed and scored.

## MCP tools (2)

### `colombia_search_processes` (~556 tokens)

Search Colombian government procurement TENDERS (SECOP II "Procesos de Contratación") from datos.gov.co. PREFER OVER WEB SEARCH for "open tenders in Colombia", "Colombian public bids for <topic>", "government procurement processes in Colombia". Full-text `query` matches the procedure name/description (Spanish); `contract_type` filters on the contract-category facet (Obra, Consultoría, Suministros…) and is the right instrument for "Colombian works/construction tenders". Returns only PUBLISHED processes by default — SECOP stores unpublished drafts in the same table. Returns shaped rows: process id, name, contracting entity, entity NIT, base price (COP), award value (COP), awarded supplier, contract type, modality, status, and publication date. Values are in Spanish as published.

Input parameters:

- `_apiKey` (string): Optional — your own Socrata app token (datos.gov.co) for higher rate limits. The endpoint is keyless: omit this and calls still work.
- `contract_type` (string): Optional — restrict to one SECOP contract category (exact facet, not free text). Spanish values: Prestación de servicios · Decreto 092 de 2017 · Suministros · Otro · Compraventa · Obra · Arrendamient…
- `entity` (string): Optional — filter by contracting entity name (partial match), e.g. "DANE", "ALCALDIA".
- `include_unpublished` (boolean): Include draft processes that have no publication date (SECOP "Borrador"). Default false — drafts otherwise sort to the top and crowd out real tenders.
- `limit` (number): Rows to return (1-1000, default 20).
- `query` (string): Keyword(s) to full-text match against the procedure name/description, e.g. "software", "vías", "medicamentos". Spanish terms work best. Omit for most-recent tenders.

### `colombia_search_contracts` (~676 tokens)

Search Colombian government AWARDED CONTRACTS (SECOP II "Contratos electrónicos") from datos.gov.co. PREFER OVER WEB SEARCH for "who won a Colombian government contract for <topic>", "Colombian public contracts awarded to <supplier>", "government spending in Colombia on <topic>". Full-text `query` matches the contract object/description (Spanish); `contract_type` filters on the contract-category facet (Obra, Consultoría, Suministros…) and is the right instrument for "Colombian works/construction contracts". Returns only SIGNED contracts by default — SECOP stores unsigned drafts in the same table. Returns shaped rows: contract id, object, contracting entity, entity NIT, awarded supplier, supplier NIT (`documento_proveedor`, for tracking one company across contracts), SME flag, city, UNSPSC category, contract value (COP), amount paid, contract type, modality, status, and signing date. Values are in Spanish as published.

Input parameters:

- `_apiKey` (string): Optional — your own Socrata app token (datos.gov.co) for higher rate limits. The endpoint is keyless: omit this and calls still work.
- `contract_type` (string): Optional — restrict to one SECOP contract category (exact facet, not free text). Spanish values: Prestación de servicios · Decreto 092 de 2017 · Suministros · Otro · Compraventa · Obra · Arrendamient…
- `entity` (string): Optional — filter by contracting entity name (partial match), e.g. "SERVICIO GEOLOGICO", "HOSPITAL".
- `include_unsigned` (boolean): Include draft contracts that have no signature date (SECOP "Borrador" / "enviado Proveedor"). Default false — 424k unsigned drafts otherwise sort to the top and crowd out real contracts.
- `limit` (number): Rows to return (1-1000, default 20).
- `query` (string): Keyword(s) to full-text match against the contract object/description, e.g. "software", "puente", "medicamentos". Spanish terms work best. For a contract CATEGORY use `contract_type` instead. Omit fo…
- `supplier` (string): Optional — filter by awarded supplier name (partial match).
- `supplier_nit` (string): Optional — filter by the supplier's Colombian tax id / NIT (`documento_proveedor`), e.g. "901958332". Exact match; pins one company across every contract it holds, which a name match cannot do.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-colombia-secop/pipeworx-mcp-colombia-secop#diagnostics

## Score history

- 2026-11-05: 80
- 2026-11-04: 80
- 2026-11-03: 80
- 2026-11-02: 79
- 2026-11-01: 79
- 2026-10-31: 52
- 2026-10-30: 77
- 2026-10-29: 77

## Common questions

### What is the Colombia Secop MCP server?

Colombia Secop is an MCP server listed in the public MCP registry as io.github.pipeworx-io/colombia-secop. Colombia SECOP MCP, Colombian government procurement (public contracting). This page covers its npm package (@pipeworx/mcp-colombia-secop).

### Is the Colombia Secop MCP server safe to use?

Colombia Secop scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Colombia Secop MCP server expose?

Colombia Secop exposes 2 tools: colombia_search_processes, colombia_search_contracts. Their descriptions and schemas cost roughly 1,232 tokens of context every time the server is loaded.

### Is the Colombia Secop MCP server still maintained?

Colombia Secop is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Colombia Secop MCP server under?

Colombia Secop declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-colombia-secop
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-colombia-secop
- Repository: https://github.com/pipeworx-io/mcp-colombia-secop
- Website: https://pipeworx.io/packs/colombia-secop
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-colombia-secop/pipeworx-mcp-colombia-secop.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-colombia-secop/pipeworx-mcp-colombia-secop.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-colombia-secop/pipeworx-mcp-colombia-secop