# Chile Procurement (npm · @pipeworx/mcp-chile-procurement)

Chile Government Procurement MCP — Mercado Público / ChileCompra (keyless-ish).

- Trust score: 82/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-chile-procurement/chile-procurement-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-chile-procurement/chile-procurement-mcp)
- npm · `@pipeworx/mcp-chile-procurement`: 82/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-chile-procurement/pipeworx-mcp-chile-procurement.md), [page](https://verifymcp.io/servers/pipeworx-io-chile-procurement/pipeworx-mcp-chile-procurement)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-chile-procurement`
- 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-chile-procurement).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 5 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 63/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 542 tokens (~271/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 Chile Procurement MCP server?

Chile Procurement runs locally as an npm package, launched with npx -y @pipeworx/mcp-chile-procurement. 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-chile-procurement -- npx -y @pipeworx/mcp-chile-procurement
```

### Cursor

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

### VS Code

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

### Codex

```bash
codex mcp add pipeworx-io-chile-procurement -- npx -y @pipeworx/mcp-chile-procurement
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add pipeworx-io-chile-procurement --command npx --arg -y --arg @pipeworx/mcp-chile-procurement
```

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

## 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-04 (score 82, +1)

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

### 2026-11-02 (score 81, +1)

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

### 2026-11-01 (score 80, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-31 (score 65, −14)

- [security regression] Malware scan: pass → unverified
- [functional] Package version: 0.2.0 → 0.2.1

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

First indexed and scored.

## MCP tools (2)

### `chile_search_tenders` (~356 tokens)

Search Chile government procurement tenders (licitaciones) from Mercado Público / ChileCompra, the official Chilean public-procurement platform. By default returns tenders published TODAY. Pass estado="activas" for all currently OPEN tenders, or fecha="ddmmyyyy" (e.g. "01072026") for tenders published on a specific day. Returns each tender's código (CodigoExterno), name, status, and closing date. Use chile_get_tender with a código for full detail (buyer, amount, line items).

Input parameters:

- `estado` (string): Optional tender-status filter. Use "activas" for all currently open tenders. Other accepted values include "publicada", "cerrada", "desierta", "adjudicada", "revocada", "suspendida". Omit for today's…
- `fecha` (string): Optional publication date in ddmmyyyy format (e.g. "01072026" for 1 July 2026). Omit for today. Mutually exclusive with estado — if both given, fecha wins.
- `keyword` (string): Optional keyword filter matched against the tender NAME. Tender names are in SPANISH — pass Spanish terms, translating if the user asked in another language (trucks → "camion", ambulance → "ambulanci…
- `limit` (number|string): Max tenders to return (default 25, max 200). The result count column reflects the full API total.

### `chile_get_tender` (~129 tokens)

Get the full detail of a single Chile government tender (licitación) from Mercado Público / ChileCompra by its código (CodigoExterno, e.g. "1002772-63-LP26"). Returns the tender name, description, status, buyer organisation/unit/region, estimated amount and currency, key dates (closing, publication, award), and the list of line items (product, category, quantity, unit). Get códigos from chile_search_tenders.

Input parameters:

- `codigo` (string, required): Tender código / CodigoExterno, e.g. "1002772-63-LP26".

## Diagnostics

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

## Score history

- 2026-11-05: 82
- 2026-11-04: 82
- 2026-11-03: 81
- 2026-11-02: 81
- 2026-11-01: 80
- 2026-10-31: 65
- 2026-10-30: 79
- 2026-10-29: 79

## Common questions

### What is the Chile Procurement MCP server?

Chile Procurement is an MCP server listed in the public MCP registry as io.github.pipeworx-io/chile-procurement. Chile Government Procurement MCP, Mercado Público / ChileCompra (keyless-ish). This page covers its npm package (@pipeworx/mcp-chile-procurement).

### Is the Chile Procurement MCP server safe to use?

Chile Procurement scores 82 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 Chile Procurement MCP server expose?

Chile Procurement exposes 2 tools: chile_search_tenders, chile_get_tender. Their descriptions and schemas cost roughly 485 tokens of context every time the server is loaded.

### Is the Chile Procurement MCP server still maintained?

Chile Procurement 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 Chile Procurement MCP server under?

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

### What did VerifyMCP test on the Chile Procurement MCP server?

VerifyMCP ran 16 checks on Chile Procurement, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

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