Remote MCP · Endpoint

India Tenders MCP server

No. India Tenders answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://gateway.pipeworx.io/india-tenders/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/india-tenders
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.73 s
Tools exposed
49 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
India Government Tenders MCP — active public tenders from India's official e-procurement portals…
Listing
From the official MCP registry (active).
Recent checks of India Tenders
CheckedResultHandshake
1 hour agoHandshake completed1.73 s
2 days agoHandshake completed4.03 s
5 days agoHandshake completed1.25 s
7 days agoHandshake completed963 ms
9 days agoHandshake completed3.07 s
11 days agoHandshake completed2.82 s
13 days agoHandshake completed730 ms
16 days agoHandshake completed101 ms
17 days agoHandshake completed58 ms
19 days agoHandshake completed977 ms
20 days agoHandshake completed1.73 s
21 days agoHandshake completed1.30 s
23 days agoHandshake completed872 ms

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

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 India Tenders and makes no claim about it beyond what these checks measured.