# Tender MCP (remote · tender-mcp-production.up.railway.app)

Government tender search for AI agents. UK, EU and US procurement opportunities.

- Trust score: 60/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `tender-mcp-production.up.railway.app`: 60/100 (this document), [markdown](https://verifymcp.io/servers/ojaskord-tender-mcp/tender-mcp-production.md), [page](https://verifymcp.io/servers/ojaskord-tender-mcp/tender-mcp-production)
- npm · `tender-mcp`: 63/100, [markdown](https://verifymcp.io/servers/ojaskord-tender-mcp/tender-mcp.md), [page](https://verifymcp.io/servers/ojaskord-tender-mcp/tender-mcp)

## Channel facts

- Endpoint: `https://tender-mcp-production.up.railway.app`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.2.25`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 62/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 628 tokens (~314/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http ojaskord-tender-mcp https://tender-mcp-production.up.railway.app/
```

### Codex

```toml
[mcp_servers.ojaskord-tender-mcp]
url = "https://tender-mcp-production.up.railway.app/"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ojaskord-tender-mcp": {
      "type": "remote",
      "url": "https://tender-mcp-production.up.railway.app/",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ojaskord-tender-mcp --url https://tender-mcp-production.up.railway.app/ --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ojaskord-tender-mcp:
    url: "https://tender-mcp-production.up.railway.app/"
```

### Other

```json
{
  "mcpServers": {
    "ojaskord-tender-mcp": {
      "type": "http",
      "url": "https://tender-mcp-production.up.railway.app/"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 60, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 59, 0)

- [functional] Server version: 1.3.4 → 1.3.5

### 2026-07-31 (score 59, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 58, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 58, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 57, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 56)

First indexed and scored.

## MCP tools (2)

### `search_tenders` (~363 tokens)

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.

Input parameters:

- `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, required): 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"]

Output parameters:

- `_disclaimer` (string)
- `_intelligence` (object): Always-present upsell hook -- not gated by tier
- `checked_at` (string)
- `errors` (array)
- `keyword` (string)
- `scoring` (object|null): Present only when company_profile was provided
- `sources_searched` (array)
- `tenders` (array)
- `total_found` (integer)

### `get_tender_intelligence` (~265 tokens)

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.

Input parameters:

- `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, required): DAILY_DIGEST: new tenders in last 24hrs. AWARD_HISTORY: past contract winners.
- `sources` (array): Sources to search. Defaults to all three.

Output parameters:

- `_disclaimer` (string)
- `checked_at` (string)
- `message` (string)
- `mode` (string)
- `status` (string): Present on the free-tier preview path
- `upgrade_url` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ojaskord-tender-mcp/tender-mcp-production#diagnostics

## Score history

- 2026-08-03: 60
- 2026-08-02: 60
- 2026-08-01: 59
- 2026-07-31: 59
- 2026-07-30: 58
- 2026-07-29: 58
- 2026-07-28: 57
- 2026-07-27: 57
- 2026-07-26: 56

## Links

- Remote endpoint: https://tender-mcp-production.up.railway.app/
- Repository: https://github.com/OjasKord/tender-mcp
- Website: https://kordagencies.com/
- Changelog RSS feed: https://verifymcp.io/servers/ojaskord-tender-mcp/tender-mcp-production/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/ojaskord-tender-mcp/tender-mcp-production/changelog.json
- HTML version of this page: https://verifymcp.io/servers/ojaskord-tender-mcp/tender-mcp-production