# Open Contracting (npm · @pipeworx/mcp-open-contracting)

Open Contracting MCP — international public procurement: government tenders and contract awards…

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

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-open-contracting`
- 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-open-contracting).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 1 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 986 tokens (~246/item across 4 items; 4 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 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 Open Contracting MCP server?

Open Contracting runs locally as an npm package, launched with npx -y @pipeworx/mcp-open-contracting. 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-open-contracting -- npx -y @pipeworx/mcp-open-contracting
```

### Cursor

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

### VS Code

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

### Codex

```bash
codex mcp add pipeworx-io-open-contracting -- npx -y @pipeworx/mcp-open-contracting
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add pipeworx-io-open-contracting --command npx --arg -y --arg @pipeworx/mcp-open-contracting
```

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

## 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, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-11-03 (score 66, −13)

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

### 2026-10-30 (score 79, 0)

- [functional regression] Security disclosure: unverified → fail

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

First indexed and scored.

## MCP tools (4)

### `oc_tender_search` (~504 tokens)

Search international public procurement — government tenders, contract notices, and contract awards published under the OCDS Open Contracting Data Standard. Covers 18 national and subnational publishers across developing countries and Europe: Africa (Kenya, Nigeria, Ghana, Zambia, Liberia, Rwanda, Tanzania), Latin America (Uruguay, Honduras, Guatemala, Peru, Dominican Republic, Mexico/Oaxaca), the Balkans (Albania, Kosovo, Croatia), Thailand (Bangkok), and Italy (ANAC anti-corruption authority). Free-text query matches tender title, buyer (procuring government entity), and description, and works in English even though most publishers file their text in Spanish, Albanian, Croatian, Italian or Thai: the query is searched alongside its equivalents in the language of the country you filter to, so "Ministry of Health" also finds "MINISTERIO DE SALUD". The response echoes every spelling it searched in query_match. Filter by country, status (e.g. tender, award, complete), category (works | goods | services), min_value (tender value floor), and days (recently released). Returns one row per contracting process (latest release) with buyer, value, procurement method, deadlines, and award details when present. Data is refreshed weekly from official OCDS publications (OCP Data Registry). Use oc_coverage first to see which countries have data and how fresh it is.

Input parameters:

- `category` (string): Main procurement category. One of: works | goods | services.
- `country` (string): Country name, forgiving match (e.g. "Thailand", "mexico", "kosovo"). One of: Albania | Argentina | Croatia | Dominican Republic | Ghana | Guatemala | Honduras | Italy | Kenya | Kosovo | Liberia | Mex…
- `days` (number|string): Only releases published within this many days.
- `limit` (number|string): Max results (1-100, default 20).
- `min_value` (number|string): Only processes whose tender value is at or above this (in the publisher's currency).
- `query` (string): Free-text matched (case-insensitive) against tender title, buyer, and description, e.g. "road construction", "medical supplies", "ministry of health".
- `status` (string): Contracting process status, e.g. "tender", "award", "complete".

### `oc_recent` (~200 tokens)

Most recently published government procurement releases — new tenders and fresh contract awards across all covered OCDS publishers (Kenya, Nigeria, Ghana, Zambia, Liberia, Rwanda, Tanzania, Uruguay, Honduras, Guatemala, Peru, Dominican Republic, Mexico/Oaxaca, Albania, Kosovo, Croatia, Thailand/Bangkok, Italy), newest first. Optionally filter to one country and adjust the lookback window. The "what public tenders just came out" view over the weekly-refreshed OCP Data Registry feed.

Input parameters:

- `country` (string): Country name, forgiving match. One of: Albania | Argentina | Croatia | Dominican Republic | Ghana | Guatemala | Honduras | Italy | Kenya | Kosovo | Liberia | Mexico | Nigeria | Peru | Rwanda | Tanzan…
- `days` (number|string): Lookback window in days (default 14).
- `limit` (number|string): Max results (1-100, default 20).

### `oc_process_history` (~119 tokens)

Full release history for a single contracting process, looked up by its OCID (Open Contracting ID, as returned by oc_tender_search / oc_recent). Returns every OCDS release in chronological order, showing the tender → award → contract progression: planning and tender notices, deadline changes, and the eventual award with supplier and amount. Use it to trace how a specific government tender played out.

Input parameters:

- `ocid` (string, required): The Open Contracting ID of the process, e.g. "ocds-abc123-000-00001".

### `oc_coverage` (~109 tokens)

Which open-contracting procurement data is currently available: per-country publisher name, release and contracting-process counts, and latest-release freshness. Call this first to learn which of the 18 covered countries (Albania, Croatia, Dominican Republic, Ghana, Guatemala, Honduras, Italy, Kenya, Kosovo, Liberia, Mexico/Oaxaca, Nigeria, Peru, Rwanda, Tanzania, Thailand/Bangkok, Uruguay, Zambia) have data, how much, and how current the data is before relying on it.

## Diagnostics

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

## Score history

- 2026-11-05: 82
- 2026-11-04: 82
- 2026-11-03: 66
- 2026-11-02: 79
- 2026-11-01: 79
- 2026-10-31: 79
- 2026-10-30: 79
- 2026-10-29: 79

## Common questions

### What is the Open Contracting MCP server?

Open Contracting is an MCP server listed in the public MCP registry as io.github.pipeworx-io/open-contracting. Open Contracting MCP, international public procurement: government tenders and contract awards… This page covers its npm package (@pipeworx/mcp-open-contracting).

### Is the Open Contracting MCP server safe to use?

Open Contracting 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 Open Contracting MCP server expose?

Open Contracting exposes 4 tools: oc_tender_search, oc_recent, oc_process_history, oc_coverage. Their descriptions and schemas cost roughly 932 tokens of context every time the server is loaded.

### Is the Open Contracting MCP server still maintained?

Open Contracting 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 Open Contracting MCP server under?

Open Contracting 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 Open Contracting MCP server?

VerifyMCP ran 16 checks on Open Contracting, 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-open-contracting
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-open-contracting
- Repository: https://github.com/pipeworx-io/mcp-open-contracting
- Website: https://pipeworx.io/packs/open-contracting
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-open-contracting/pipeworx-mcp-open-contracting.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-open-contracting/pipeworx-mcp-open-contracting/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-open-contracting/pipeworx-mcp-open-contracting.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-open-contracting/pipeworx-mcp-open-contracting