Open Tender and RFP Finder MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIFY_TOKEN | Yes | Your Apify API token from console.apify.com/account/integrations. The server can list its tool without a token, but calls require one. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| find_open_tendersA | Find open public tender and RFP notices that match keywords, CPV codes, and buyer countries, read from four official portals with no key: UK Contracts Finder, UK Find a Tender, EU TED (Tenders Electronic Daily), and CanadaBuys. Returns one row per notice with portal, notice_id, notice_url, title, description_excerpt, buyer_name, buyer_country, published_at, deadline_at, days_to_deadline, estimated_value, currency, category_codes (CPV or UNSPSC), contract_type, procedure, sme_suitable (UK), buyer_contact_email, matched_keywords, and match_source. Filters run before billing. When nothing matches, one free no_results row says why. A run that does not succeed is returned as an error with its run ID. Read-only; requires an APIFY_TOKEN; Apify charges per notice row returned plus a run start. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
There is only one tool, so there is no possibility of confusing it with another. Its purpose (finding open tenders matching keywords, CPV/UNSPSC codes, and countries) is unambiguous and fully self-contained.
The single name find_open_tenders follows a clear snake_case verb_noun convention. With only one tool there is no mixing of conventions, and the name maps directly to the described action.
A one-tool surface is borderline thin for a server, even though this tool is unusually rich (multi-portal search, many output fields, filtering). A single tool leaves no seam for narrower operations like fetching a specific notice or listing portals, but it is not a trivial wrapper either.
For a 'finder' domain the tool covers the core discovery workflow well: multi-source search, filtering, rich result rows, no_results handling, and error reporting. Minor gaps exist, such as fetching or re-querying a specific notice by ID and explicit pagination controls, but agents can largely work around these.