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

Tender MCP

REMOTE · TENDER-MCP-PRODUCTION.UP.RAILWAY.APP · 2 COMPONENTS · SCANNED AUG 3

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

+3 this week 60 Trust /100
Trust breakdown (6 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 →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability62
  • 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 Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Install

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.

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/
# ~/.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/"
// 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.

  • 2 Aug 26 +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.

  • 1 Aug 26 0
    • Server version: 1.3.4 → 1.3.5 functional
  • 31 Jul 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
  • 30 Jul 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
  • 29 Jul 26 +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.

  • 27 Jul 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
  • 26 Jul 26 56

    First indexed and scored.

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 3 Aug 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
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
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.

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.