Procurement Evidence MCP Server avatar

Procurement Evidence MCP Server

Pricing

from $50.00 / 1,000 tool calls

Go to Apify Store
Procurement Evidence MCP Server

Procurement Evidence MCP Server

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.

Pricing

from $50.00 / 1,000 tool calls

Rating

0.0

(0)

Developer

NexGen Watch

NexGen Watch

Maintained by Community

Actor stats

0

Bookmarked

1

Total users

0

Monthly active users

2 days ago

Last modified

Categories

Share

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

toolwhat it answers
list_jurisdictionsWhat is covered and what each source can actually tell you. Read this first.
search_procurementNotices and awards across all three systems, each with an official URL
search_by_supplierContracts associated with a named supplier, with the match basis stated
get_record_urlTurn a record id into its official URL

Sources — public, logged-out, no key

jurisdictionsourcewhat it carries
UKFind a Tender Service (OCDS)notices and award values
EUTenders Electronic Daily (TED)the notice and its official URL — not award values inline
USUSAspendingfederal 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.

  • 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

EventPrice
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.