Remote MCP · Endpoint

askTender MCP server

No. askTender answered an MCP handshake 35 minutes ago.

UpLast checked 35 minutes ago

Server URL

https://asktender.org/mcp

The last check completed an MCP handshake.

Registry name
org.asktender/asktender
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
693 ms
Tools exposed
18 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Government tenders in about 200 countries: who can bid, what each requires, and the bid kit.
Listing
From the official MCP registry (active).
Recent checks of askTender
CheckedResultHandshake
35 minutes agoHandshake completed693 ms
9 days agoHandshake completed810 ms
10 days agoHandshake completed917 ms
11 days agoHandshake completed939 ms
12 days agoHandshake completed843 ms
14 days agoHandshake completed289 ms
14 days agoHandshake completed875 ms
15 days agoHandshake completed887 ms
17 days agoHandshake completed890 ms
19 days agoHandshake completed297 ms
21 days agoHandshake completed241 ms
24 days agoHandshake completed768 ms
26 days agoHandshake completed643 ms
28 days agoHandshake completed628 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 16 responding of 16.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with askTender and makes no claim about it beyond what these checks measured.