find_a_tender_recent
Pack: uk-contracts · 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/find_a_tender_recent for the schema, then POST the same URL with its arguments for the data.
Recent OR HISTORICAL high-value UK government tenders and contract awards from the Find a Tender Service (find-tender.service.gov.uk) — the UK’s above-threshold procurement portal (the post-Brexit replacement for EU TED, for larger public contracts). Use for “high value UK tenders”, “above threshold UK government contracts”, “Find a Tender notices”, “large UK public sector contract opportunities”, or a historical window like “FTS notices from 2023”. Returns notices newest-first within the window days reaches back. An optional keyword is matched over title, description, award title and AWARDED SUPPLIER — client-side, because the FTS API has no text search (it rejects a keyword parameter outright, allowing only stages/limit/cursor/updatedFrom/updatedTo). ALWAYS READ window_complete: false means the walk stopped at the page cap (8 pages/call) with more feed left, so a zero means “absent from the notices examined”, not “not published” — narrow days or stage until it is true, or repeat the call from where it stopped. For a proper full-corpus keyword SEARCH of UK procurement with real historical date filtering (not just a bounded walk), and for lower-value notices, use search_notices (Contracts Finder), which does have a real server-side index. Keyless.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
keyword | string | no | Optional keyword to filter recent notices by title/description, e.g. “cloud”, “construction”. Omit to list all recent. |
stage | string | no | Notice stage: “tender” (open opportunities, default), “award” (results), or “planning”. |
days | number | no | How many days back to scan, 1–3660 (~10 years; FTS itself accepts any historical date, verified live). Default 7 when listing, 30 when a keyword is given (the 7-day feed is only ~30 notices, too few for a keyword to match). A wide window still walks at most 8 pages per call (see window_complete) — narrow with stage/keyword for a window the walk can finish in one call. |
limit | number | no | Max notices to return, 1–100 (default 20). |
Example call
Arguments
{
"stage": "tender",
"days": 7,
"limit": 20
}
curl
curl -X POST https://gateway.pipeworx.io/uk-contracts/mcp \
-H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"find_a_tender_recent","arguments":{"stage":"tender","days":7,"limit":20}}}'
TypeScript (@pipeworx/sdk)
import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();
const result = await pipeworx.call('find_a_tender_recent', {
"stage": "tender",
"days": 7,
"limit": 20
});
More examples
{
"keyword": "MRI",
"stage": "tender",
"days": 30
}
{
"keyword": "MRI",
"stage": "award",
"days": 3
}
{
"stage": "award",
"days": 400
}
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 uk-contracts pack
{
"mcpServers": {
"uk-contracts": {
"url": "https://gateway.pipeworx.io/uk-contracts/mcp"
}
}
}
See Getting Started for client-specific install steps.