Tender MCP
NPM · TENDER-MCP · 2 COMPONENTS · SCANNED AUG 3
Government tender search for AI agents. UK, EU and US procurement opportunities.
Available components
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 →
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 1 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · tender-mcp
claude mcp add ojaskord-tender-mcp -- npx -y tender-mcp
codex mcp add ojaskord-tender-mcp -- npx -y tender-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ojaskord-tender-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"tender-mcp"
],
"enabled": true
}
}
} openclaw mcp add ojaskord-tender-mcp --command npx --arg -y --arg tender-mcp
mcp_servers:
ojaskord-tender-mcp:
command: "npx"
args: ["-y", "tender-mcp"] {
"mcpServers": {
"ojaskord-tender-mcp": {
"command": "npx",
"args": [
"-y",
"tender-mcp"
]
}
}
} 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.
- 2 Aug 26 +15
- Malware scan: unverified → pass ▲ security
- 1 Aug 26 −12
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −18
- Malware scan: pass → unverified ▼ security
- 27 Jul 26 +31
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: excellent functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 100 functional
- First check of Tool coverage: 100 functional
- First check of Schema quality: fail functional
- 26 Jul 26 47
First indexed and scored.
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 3 Aug 2026 · Analysed npm/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 0 packages
0 packages in the resolved dependency tree.
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.
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.