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.

askTender

REMOTE · ASKTENDER.ORG

Government tenders in about 200 countries: who can bid, what each requires, and the bid kit.

Available components

+3 this week 69 Trust /100

Last scanned (17 hours ago)

Scores higher than 59% of remote servers

Reachable. Last reached 22 Oct 2026.

Category CRM and Sales

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 Security77
Transport & Reachability100
Schema Quality & AI Usability68
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 1547 tokens (~85/item across 18 items; 18 tools + 0 resources), lean.Pass
  • 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 Coverage84
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 52% of tool parameters carry a description.Partial
Tool Safety50
  • Injection-marker check failed: the server instructions contains an instruction to conceal the call from the user, the text "do not tell the user", at byte 1516 of that field. See how to fix → Fail
  • We read all 18 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 19 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.

  • 22 Oct 26 +1

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

  • 19 Oct 26 +1

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

  • 17 Oct 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.

  • 15 Oct 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 14 Oct 26 65

    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 22 Oct 2026 · Probed https://asktender.org/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=asktender.org CN=YE2,O=Let's Encrypt,C=US 28 Sept 2026 27 Dec 2026 ECDSA 256 ECDSA-SHA384 62211a772cf2f8a4016b1cfa6f328c88e13
SANs: asktender.org
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
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 secure

Validation of asktender.org. — Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
org. present 26974 8 Verified
asktender.org. present 48271 8 Verified
asktender.org. Verified address RRset verified with the apex keys
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://asktender.org/mcp Verified 200
http (plaintext) http://asktender.org/mcp HTTPS enforced 308 https://asktender.org/mcp
MCP tools · 18 exposed · ~1,197 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
can_company_bid ~140

Whether a company based in one country may bid for public tenders in another country (trade agreements, foreign-bidder rules, registrations needed). Give a tender_id or the tender's country. Use when the user asks whether a company from one country can bid on, or take part in, public tenders in another country.

NameTypeReqDescription
company_countrystringyesWhere the bidding company is based: name or ISO code.
tender_countrystring–Country of the tenders: name or ISO code (not needed if tender_id is given).
tender_idinteger–Optional askTender tender id; its country and scope are used.

No output schema declared.

No examples provided.

check_my_eligibility ~89

For the user's own company (askTender account): whether it can bid on a tender and qualifies, which requirements it meets, what is missing and how to close each gap. Needs the askTender account connected. Use when the user asks whether their own company qualifies for, or can bid on, a specific askTender tender.

NameTypeReqDescription
tender_idintegeryesThe askTender tender id.

No output schema declared.

No examples provided.

compare_plans ~104

askTender's plans (Pro, Intelligence, Business): prices, what each includes, who each is for, and which fits the user's situation. Use when the user asks about pricing, which plan to choose, or what askTender can do for them.

NameTypeReqDescription
situationstring–Optional: the user's situation in their words, e.g. 'small IT firm, first tender, no time to do paperwork' or 'we bid often and want to know who wins'.

No output schema declared.

No examples provided.

find_guides ~96

askTender's guides on how public procurement works: registering on portals (SAM.gov, GeM, Find a Tender...), digital signatures, bid security, foreign bidders, consortiums. Returns titles, summaries and links.

NameTypeReqDescription
countrystring–Optional country to focus on: name or ISO code.
querystringyesThe question or topic, e.g. 'register on SAM.gov', 'foreign companies bidding in India'.

No output schema declared.

No examples provided.

get_bid_kit ~54

The submission checklist for a tender against the user's company: documents they already have, drafts askTender prepares for signature, and items to obtain with lead times. Pro plan and above.

NameTypeReqDescription
tender_idintegeryes–

No output schema declared.

No examples provided.

get_requirements ~53

Every requirement of a tender in the tender's own words (financial, experience, certifications, registrations, bid security, documents), routed to who handles each. Pro plan and above.

NameTypeReqDescription
tender_idintegeryes–

No output schema declared.

No examples provided.

get_tender ~69

The facts of one tender by its askTender id: title, buyer, country, deadline, value, status, and a plain-English brief where available, with its askTender link.

NameTypeReqDescription
tender_idintegeryesThe askTender tender id (from search_tenders or an askTender link).

No output schema declared.

No examples provided.

my_account ~18

The user's askTender plan and what it includes.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

my_bids ~21

The user's bids being prepared with askTender and their status.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

my_matching_tenders ~69

Open tenders for the user's company: found by what its askTender profile says the company does (its capabilities), or by a search phrase if given. Use when the user asks which tenders suit or match their company.

NameTypeReqDescription
limitinteger––
querystring––

No output schema declared.

No examples provided.

my_saved_tenders ~24

The tenders the user has saved on askTender, with deadlines.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

my_watchlist ~27

The buyers and competitors the user watches, with their recent activity. Intelligence plan and above.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

save_tender ~32

Save a tender to the user's askTender list (deadline reminders and tracking).

NameTypeReqDescription
tender_idintegeryes–

No output schema declared.

No examples provided.

search_tenders ~178

Find open government tenders (calls for bids) by what is being bought and, optionally, the country. Returns up to 10 live tenders from official procurement portals (refreshed daily) with buyer, deadline, value and an askTender link. Use when the user asks to find tenders, calls for bids or public contracts to bid on.

NameTypeReqDescription
closing_within_daysinteger–Only tenders whose deadline is within this many days.
countrystring–Country whose tenders to search: a name or ISO code, e.g. 'United Kingdom', 'IN', 'Germany'. Leave empty for all countries.
limitinteger––
querystringyesWhat the company sells or the work wanted, e.g. 'school cleaning services', 'LED street lights', 'cloud migration'.

No output schema declared.

No examples provided.

start_managed_bid ~53

Hand a tender to the askTender Desk, which prepares the bid with the user and coordinates askTender Partners (accountants, professionals) for certificates and filing. Business plan.

NameTypeReqDescription
tender_idintegeryes–

No output schema declared.

No examples provided.

tender_incumbent ~66

For a tender: who holds or last won this buyer's similar contracts, the buyer's closest past contracts (winner, value, date) and a price guide from them, useful when the notice publishes no value. Intelligence plan and above.

NameTypeReqDescription
tender_idintegeryes–

No output schema declared.

No examples provided.

upcoming_renewals ~31

Contracts in the user's markets that are ending soon (the next tender is coming). Intelligence plan and above.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

watch ~73

Add a public buyer or a supplier (competitor) to the user's watchlist, to follow their tenders and awards. Intelligence plan and above.

NameTypeReqDescription
countrystring––
kindstringyes–
namestring––
tender_idinteger–Optional: watch this tender's buyer.

No output schema declared.

No examples provided.

Install

How do I install the askTender MCP server?

askTender is a hosted endpoint at https://asktender.org/mcp, 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 · asktender.org

# add to Claude Code
claude mcp add --transport http org-asktender-asktender 'https://asktender.org/mcp'
Common questions

What is the askTender MCP server?

askTender is an MCP server listed in the public MCP registry as org.asktender/asktender. Government tenders in about 200 countries: who can bid, what each requires, and the bid kit. This page covers its hosted endpoint (https://asktender.org/mcp).

Is the askTender MCP server safe to use?

askTender scores 69 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 askTender MCP server expose?

askTender exposes 18 tools: search_tenders, get_tender, can_company_bid, find_guides, compare_plans, and 13 more. Their descriptions and schemas cost roughly 1,197 tokens of context every time the server is loaded.

Does the askTender MCP server require authentication?

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

Is the askTender MCP server still maintained?

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