Remote MCP · Endpoint

Winquill MCP server

No. Winquill answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://mcp.tenda.eshmere.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.eshmere/tenda
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
237 ms
Tools exposed
44 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Public tenders and contract awards in the UK, US, Canada and EU, and help preparing bids.
Website
https://winquill.com/
Listing
From the official MCP registry (active).
Recent checks of Winquill
CheckedResultHandshake
2 hours agoHandshake completed237 ms
1 day agoHandshake completed225 ms
2 days agoHandshake completed183 ms
2 days agoHandshake completed217 ms
4 days agoHandshake completed156 ms
7 days agoHandshake completed181 ms
9 days agoHandshake completed179 ms
12 days agoHandshake completed180 ms
14 days agoHandshake completed215 ms
16 days agoHandshake completed244 ms
18 days agoHandshake completed149 ms
20 days agoHandshake completed148 ms
22 days agoHandshake completed134 ms
24 days agoHandshake completed302 ms

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

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