# Procurement Evidence MCP Server (`nexgenwatch/procurement-evidence-mcp`) Actor

Locate the public procurement record behind a claim across the UK, EU and US. Every row carries the awarding body's own record id and a direct public URL.

- **URL**: https://apify.com/nexgenwatch/procurement-evidence-mcp.md
- **Developed by:** [NexGen Watch](https://apify.com/nexgenwatch) (community)
- **Categories:** Agents, Business
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $50.00 / 1,000 tool calls

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Procurement Evidence MCP Server

Locate the public procurement record behind a claim, across **the UK, the EU and the US**. Every
row carries the awarding body's **own record id and a direct public URL**, so "who won this
contract" is checkable at source.

An **evidence locator**, not an analyst. It does not score suppliers, rank bids, or infer
relationships between contracts — it tells you which record to open.

### Tools

| tool | what it answers |
|---|---|
| `list_jurisdictions` | What is covered and what each source can actually tell you. Read this first. |
| `search_procurement` | Notices and awards across all three systems, each with an official URL |
| `search_by_supplier` | Contracts associated with a named supplier, with the match basis stated |
| `get_record_url` | Turn a record id into its official URL |

### Sources — public, logged-out, no key

| jurisdiction | source | what it carries |
|---|---|---|
| **UK** | Find a Tender Service (OCDS) | notices **and** award values |
| **EU** | Tenders Electronic Daily (TED) | the notice and its official URL — **not** award values inline |
| **US** | USAspending | federal contract awards with amounts and recipients (types A–D, **not grants**) |

**The three do not answer the same question equally well**, and every response says so. A
cross-jurisdiction search reports which systems were searched, which failed, and
`coverage_complete` — because a "no results" produced by a partial search is the failure that
would matter most here.

UK Contracts Finder was probed live and works; it is deliberately not wired, because it covers
the same jurisdiction as Find a Tender and two overlapping UK sources would be duplication
rather than coverage. It is the natural addition if below-threshold UK notices are wanted.

### Match honesty on supplier search

- **US** matches are the awarding system's **own recipient field**.
- **UK / EU** matches are name occurrences in the record. A match resting only on a **title**
  is returned with `requires_human_review: true` and labelled a candidate.

There is no similarity score. A number would read as a probability and it is not one.

### Pacing

None of these three publish a hard request cap, so there is no number to comply with — but a
standby server answering several agents at once can still hammer a public service. Every
outbound call goes through one shared token bucket at **5 requests/second with strict pacing**
(burst 1), the shape ratified in Section 3: a bucket that starts full passes its whole capacity
instantly, and the burst is the moment that matters.

### Pricing

| Event | Price |
|---|---|
| Server start (`apify-actor-start`) | $0.05, charged once per server run by the platform |
| Tool call (`mcp-tool-call`) | **$0.05 flat per completed tool call** |

No other events. **Errors and notices are not charged** — an unknown jurisdiction, a malformed
date, or every source failing returns without billing. A sourced answer, including a
well-evidenced "no records match", **is** charged.

If a tool call cannot be billed correctly, **the call fails** rather than serving free.

# Actor input Schema

## `note` (type: `string`):

This Actor runs as an MCP server in Standby mode. Connect an MCP client to the server URL with path /mcp; there is no batch input to fill in.

## Actor input object example

```json
{
  "note": "standby"
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "note": "standby"
};

// Run the Actor and wait for it to finish
const run = await client.actor("nexgenwatch/procurement-evidence-mcp").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "note": "standby" }

# Run the Actor and wait for it to finish
run = client.actor("nexgenwatch/procurement-evidence-mcp").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "note": "standby"
}' |
apify call nexgenwatch/procurement-evidence-mcp --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,nexgenwatch/procurement-evidence-mcp"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/8ZeO3pfW47bkWZT0o/builds/k4TrWpj4zIdL8Kv0e/openapi.json