Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Tender MCP

REMOTE · TENDER-MCP-PRODUCTION.UP.RAILWAY.APP · 2 COMPONENTS · SCANNED SEP 21

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

0 this week 73 Trust /100
Trust breakdown (7 categories)

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 Security57
Transport & Reachability100
Schema Quality & AI Usability65
  • AI-judged instruction clarity (excellent).Pass
  • 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. 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
Install

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

# add to Claude Code
claude mcp add --transport http ojaskord-tender-mcp 'https://tender-mcp-production.up.railway.app/'
// .cursor/mcp.json
{
  "mcpServers": {
    "ojaskord-tender-mcp": {
      "url": "https://tender-mcp-production.up.railway.app/"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "ojaskord-tender-mcp": {
      "type": "http",
      "url": "https://tender-mcp-production.up.railway.app/"
    }
  }
}
# ~/.codex/config.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
    }
  }
}
# add to OpenClaw
openclaw mcp add ojaskord-tender-mcp --url 'https://tender-mcp-production.up.railway.app/' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  ojaskord-tender-mcp:
    url: "https://tender-mcp-production.up.railway.app/"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "ojaskord-tender-mcp": {
      "Transport": "http",
      "Url": "https://tender-mcp-production.up.railway.app/"
    }
  }
}
# add to Vellum
assistant mcp add ojaskord-tender-mcp -t streamable-http -u 'https://tender-mcp-production.up.railway.app/'
// mcp.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 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.

  • 8 Sept 26 0
    • Server version: 1.3.8 → 1.3.10 functional
  • 26 Aug 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 +1
    • Stability: 0.97 → pass security
  • 24 Aug 26 0
    • Server version: 1.3.6 → 1.3.8 functional
  • 23 Aug 26 +1

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

  • 19 Aug 26 0
    • Server version: 1.3.5 → 1.3.6 functional
  • 11 Aug 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
  • 1 Aug 26 0
    • Server version: 1.3.4 → 1.3.5 functional
Diagnostics

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 20 Sept 2026 · Probed https://tender-mcp-production.up.railway.app

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.up.railway.app CN=YE1,O=Let's Encrypt,C=US 29 Jul 2026 27 Oct 2026 ECDSA 256 ECDSA-SHA384 6da79bb561da3efeb0e751ca21abd3999fe
SANs: *.up.railway.app, up.railway.app
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

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 No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

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 Verified 200
http (plaintext) http://tender-mcp-production.up.railway.app HTTPS enforced 301 https://tender-mcp-production.up.railway.app/
MCP tools · 2 exposed · ~628 tokens

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 →

Tool Tokens
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.

NameTypeReqDescription
keywordstringKeyword for award history search. Required for AWARD_HISTORY.
keywordsarrayKeywords to monitor or search (e.g. ["cybersecurity", "cloud infrastructure"]). Required for DAILY_DIGEST.
limitnumberMax results per source for AWARD_HISTORY (default 10)
modestringyesDAILY_DIGEST: new tenders in last 24hrs. AWARD_HISTORY: past contract winners.
sourcesarraySources to search. Defaults to all three.
NameTypeReqDescription
_disclaimerstring
checked_atstring
messagestring
modestringyes
statusstringPresent on the free-tier preview path
upgrade_urlstring

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.

NameTypeReqDescription
company_profilestringDescription 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_oldnumberOnly return tenders published in the last N days (default 30)
keywordstringyesSearch keyword — company capability, product type, or service (e.g. "cybersecurity", "catering", "IT support")
limitnumberMax results per source (default 10, max 25)
min_scorenumberOnly return tenders scoring above this threshold (default 50). Only applies when company_profile is provided.
sourcesarrayWhich sources to search. Defaults to all three: ["uk","eu","us"]
NameTypeReqDescription
_disclaimerstringyes
_intelligenceobjectAlways-present upsell hook -- not gated by tier
checked_atstringyes
errorsarray
keywordstringyes
scoringobject|nullPresent only when company_profile was provided
sources_searchedarrayyes
tendersarrayyes
total_foundintegeryes

No examples provided.

Common questions

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?

No. We connected to Tender MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Tender MCP server still maintained?

Tender MCP is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.