Open Contracting
NPM · @PIPEWORX/MCP-OPEN-CONTRACTING · 2 COMPONENTS
Open Contracting MCP — international public procurement: government tenders and contract awards…
Available components
Last scanned (5 hours ago)
Scores higher than 72% of npm servers
Category Finance and Payments
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. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-open-contracting). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability63
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 3 Nov 26 −13
- Malware scan: pass → unverified ▼ security
- Stability: unverified → 0.17 ▲ functional
- Package version: 0.2.0 → 0.2.1 functional
- 30 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 79
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/@pipeworx/mcp-open-contracting@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-open-contracting |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-open-contracting/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3679752573 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:b6accea585ec1cccff526d8a77ef34de8e9699efe1bb25de68ee2eca3cfefb6696af5ff5c0a63d8ad85ef10a01574640ddc8e04e1ecf08835d0474c02 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
oc_coverage ~109
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
oc_process_history ~119
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ocid | string | yes | The Open Contracting ID of the process, e.g. "ocds-abc123-000-00001". |
No output schema declared.
No examples provided.
oc_recent ~200
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
oc_tender_search ~504
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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". |
No output schema declared.
No examples provided.
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.
npm · @pipeworx/mcp-open-contracting
claude mcp add pipeworx-io-open-contracting -- npx -y @pipeworx/mcp-open-contracting
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.