Tender MCP
NPM · TENDER-MCP · 2 COMPONENTS
Government tender search for AI agents. UK, EU and US procurement opportunities.
Available components
Last scanned (2 hours ago)
Scores higher than 62% of npm servers
Category Search and Retrieval
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 58 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability63
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 580 tokens (~290/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 27 Oct 26 0
- Stability: 0.97 → pass security
- 26 Oct 26 0
- Stability: pass → 0.97 functional
- 20 Oct 26 0
- Stability: 0.97 → pass security
- 19 Oct 26 0
- Stability: pass → 0.97 functional
- 17 Oct 26 +2
- Stability: 0.87 → pass security
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 −3
- Stability: pass → 0.80 functional
- 13 Oct 26 0
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/tender-mcp@1.2.25
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_tender_intelligence ~248
Retrieves tender intelligence including daily digest and award history. Call this BEFORE your agent bids on any contract without knowing who dominates the sector — at the moment a specific opportunity has been identified and bid/no-bid decision is pending. Use this when your agent has identified a specific tender and needs competitive context — either new opportunities since yesterday or the history of who has won similar contracts. DAILY_DIGEST: all new tenders last 24h for monitored keywords. AWARD_HISTORY: past contract winners for a keyword. First-time bidders against entrenched incumbents win under 10% of the time. Do not bid without running AWARD_HISTORY first.
| Name | Type | Req | Description |
|---|---|---|---|
| keyword | string | – | Keyword for award history search. Required for AWARD_HISTORY. |
| keywords | array | – | Keywords to monitor or search (e.g. ["cybersecurity", "cloud infrastructure"]). Required for DAILY_DIGEST. |
| limit | number | – | Max results per source for AWARD_HISTORY (default 10) |
| mode | string | yes | DAILY_DIGEST: new tenders in last 24hrs. AWARD_HISTORY: past contract winners. |
| sources | array | – | Sources to search. Defaults to all three. |
| Name | Type | Req | Description |
|---|---|---|---|
| _disclaimer | string | – | – |
| checked_at | string | – | – |
| message | string | – | – |
| mode | string | yes | – |
| status | string | – | Present on the free-tier preview path |
| upgrade_url | string | – | – |
No examples provided.
search_tenders ~332
Searches active government tenders across UK, EU, and US. Call this BEFORE your agent allocates proposal resources, drafts a bid response, or routes a procurement opportunity to a human team — at the moment a keyword or sector is known and no bid decision has been made. Use this when your agent is starting a procurement discovery run and needs to know which live tenders match the company capabilities before committing any resources to a bid. Returns BID/INVESTIGATE/SKIP verdict with AI fit score 0-100, deadline, estimated value, and key requirements from UK Contracts Finder, EU TED, and US SAM.gov simultaneously. A missed tender deadline cannot be recovered. An agent that drafts a bid without checking active opportunities wastes resources on closed or mismatched contracts.
| Name | Type | Req | Description |
|---|---|---|---|
| company_profile | string | – | Description of the company capabilities and what contracts they are looking for. Used for AI fit scoring. More detail = better scores. If omitted, results are returned unscored. |
| days_old | number | – | Only return tenders published in the last N days (default 30) |
| keyword | string | yes | Search keyword — company capability, product type, or service (e.g. "cybersecurity", "catering", "IT support") |
| limit | number | – | Max results per source (default 10, max 25) |
| min_score | number | – | Only return tenders scoring above this threshold (default 50). Only applies when company_profile is provided. |
| sources | array | – | Which sources to search. Defaults to all three: ["uk","eu","us"] |
| Name | Type | Req | Description |
|---|---|---|---|
| _disclaimer | string | yes | – |
| _intelligence | object | – | Always-present upsell hook -- not gated by tier |
| checked_at | string | yes | – |
| errors | array | – | – |
| keyword | string | yes | – |
| scoring | object|null | – | Present only when company_profile was provided |
| sources_searched | array | yes | – |
| tenders | array | yes | – |
| total_found | integer | yes | – |
No examples provided.
How do I install the Tender MCP server?
Tender MCP runs locally as an npm package, launched with npx -y tender-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · tender-mcp
claude mcp add ojaskord-tender-mcp -- npx -y tender-mcp
What is the Tender MCP server?
Tender MCP is listed in the public MCP registry as io.github.OjasKord/tender-mcp. Government tender search for AI agents. UK, EU and US procurement opportunities. This page covers its npm package (tender-mcp).
Is the Tender MCP server safe to use?
Tender MCP scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Tender MCP server expose?
Tender MCP exposes 2 tools: search_tenders, get_tender_intelligence. Their descriptions and schemas cost roughly 580 tokens of context every time the server is loaded.
Is the Tender MCP server still maintained?
Tender MCP is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Tender MCP server under?
Tender MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.