Tender MCP
REMOTE · TENDER-MCP-PRODUCTION.UP.RAILWAY.APP · 2 COMPONENTS
Government tender search for AI agents. UK, EU and US procurement opportunities.
Available components
Last scanned (21 hours ago)
Scores higher than 60% of remote servers
Unreachable for 1 day in a row. Last reached 3 Nov 2026.
Category Search and Retrieval
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 4 Nov 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- Stability: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: fail → unverified ▼ functional
- 31 Oct 26 0
- Stability: 0.97 → pass security
- 30 Oct 26 0
- Stability: pass → 0.97 functional
- 1 Oct 26 +50
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- 30 Sept 26 23
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: fail → unverified ▼ functional
- First check of Schema quality: unverified functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 8 Sept 26 0
- Server version: 1.3.8 → 1.3.10 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 4 Nov 2026 · Probed https://tender-mcp-production.up.railway.app
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of tender-mcp-production.up.railway.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| railway.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://tender-mcp-production.up.railway.app | Unreachable | ||
| http (plaintext) | http://tender-mcp-production.up.railway.app | HTTPS enforced |
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 ~265
Retrieves tender intelligence including award history and daily digest. 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 the history of who has won similar contracts or new opportunities since yesterday. AWARD_HISTORY: past contract winners for a keyword. DAILY_DIGEST: all new tenders last 24h for monitored keywords. Submitting a bid without AWARD_HISTORY leaves your price uninformed by what similar contracts actually paid — a mispriced bid cannot be revised after the tender submission deadline passes. 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 ~363
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. Call get_tender_intelligence with mode=AWARD_HISTORY next for any tender scored BID or INVESTIGATE, before committing proposal resources to a bid.
| 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 is a hosted endpoint at https://tender-mcp-production.up.railway.app/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · tender-mcp-production.up.railway.app
claude mcp add --transport http ojaskord-tender-mcp 'https://tender-mcp-production.up.railway.app/'
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 hosted endpoint (https://tender-mcp-production.up.railway.app).
Is the Tender MCP server safe to use?
Tender MCP scores 73 out of 100 on VerifyMCP. 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 628 tokens of context every time the server is loaded.
Does the Tender MCP server require authentication?
Its publisher declares no required credentials for Tender MCP. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Tender MCP server still maintained?
Tender MCP is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 3 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.