# Tender MCP MCP server

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

## Links
- Registry page: https://www.getdrio.com/mcp/io-github-ojaskord-tender-mcp
- Repository: https://github.com/OjasKord/tender-mcp
- Website: https://kordagencies.com

## Install
- Command: `npx -y tender-mcp`
- Endpoint: https://tender-mcp-production.up.railway.app
- Auth: Auth required by registry metadata

## Setup notes
- Package: Npm tender-mcp v1.2.6
- Environment variable: ANTHROPIC_API_KEY (required; secret)
- The upstream registry signals required auth or secrets.
- Remote endpoint: https://tender-mcp-production.up.railway.app

## Tools
- search_tenders - 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. Endpoint: https://tender-mcp-production.up.railway.app
- get_tender_intelligence - 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. Endpoint: https://tender-mcp-production.up.railway.app

## Resources
Not captured

## Prompts
Not captured

## Metadata
- Owner: io.github.OjasKord
- Version: 1.2.6
- Runtime: Npm
- Transports: STDIO, HTTP
- License: Not captured
- Language: Not captured
- Stars: Not captured
- Updated: May 2, 2026
- Source: https://registry.modelcontextprotocol.io