Remote MCP · Endpoint

teas.co.uk MCP server

No. teas.co.uk answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://teas.co.uk/mcp

The last check completed an MCP handshake.

Registry name
uk.co.teas/shop
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
500 ms
Tools exposed
26 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Find, compare and buy tea, coffee and hot chocolate from teas.co.uk, a UK online tea shop.
Website
https://teas.co.uk/ai/
Listing
From the official MCP registry (active).
Recent checks of teas.co.uk
CheckedResultHandshake
1 hour agoHandshake completed500 ms
2 days agoHandshake completed367 ms
5 days agoHandshake completed358 ms
7 days agoHandshake completed380 ms
9 days agoHandshake completed364 ms
11 days agoHandshake completed366 ms
13 days agoHandshake completed378 ms
15 days agoHandshake completed353 ms
17 days agoHandshake completed367 ms
19 days agoHandshake completed420 ms
20 days agoHandshake completed398 ms
21 days agoHandshake completed341 ms
22 days agoHandshake completed916 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.

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