Remote MCP · Endpoint

TenderAPI MCP server

No. TenderAPI answered an MCP handshake 13 minutes ago.

UpLast checked 13 minutes ago

Server URL

https://api.tenderapi.eu/mcp

The last check completed an MCP handshake.

Registry name
eu.tenderapi/tenderapi
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
319 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Search EU public tenders from TED and national portals by CPV code, country, buyer or value.
Listing
From the official MCP registry (active).
Recent checks of TenderAPI
CheckedResultHandshake
13 minutes agoHandshake completed319 ms
9 days agoHandshake completed321 ms
9 days agoHandshake completed311 ms
11 days agoHandshake completed299 ms
12 days agoHandshake completed309 ms
13 days agoHandshake completed378 ms
14 days agoHandshake completed305 ms
15 days agoHandshake completed328 ms
16 days agoHandshake completed434 ms
19 days agoHandshake completed304 ms
21 days agoHandshake completed312 ms
24 days agoHandshake completed318 ms
26 days agoHandshake completed332 ms
28 days agoCredentials required—

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

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