oc_process_history
Pack: open-contracting · Connect: https://pipeworx.io/mcp (see Connect below for a single-pack URL)
No MCP client? Call it directly: GET https://gateway.pipeworx.io/v1/tools/oc_process_history for the schema, then POST the same URL with its arguments for the data.
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.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
ocid | string | yes | The Open Contracting ID of the process, e.g. “ocds-abc123-000-00001”. |
Example call
Arguments
{
"ocid": "ocds-xqjsxa-30947049"
}
curl
curl -X POST https://gateway.pipeworx.io/open-contracting/mcp \
-H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"oc_process_history","arguments":{"ocid":"ocds-xqjsxa-30947049"}}}'
TypeScript (@pipeworx/sdk)
import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();
const result = await pipeworx.call('oc_process_history', {
"ocid": "ocds-xqjsxa-30947049"
});
Connect
Add this to your MCP client config — every tool in the catalog, including this one — or use one-click install buttons:
{
"mcpServers": {
"pipeworx": {
"url": "https://pipeworx.io/mcp"
}
}
}
Connect to just the open-contracting pack
{
"mcpServers": {
"open-contracting": {
"url": "https://gateway.pipeworx.io/open-contracting/mcp"
}
}
}
See Getting Started for client-specific install steps.