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
379 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
teas.co.uk, a UK tea shop, in four tools: Ask Lee, the shop as a mini site, basket, account.
Listing
From the official MCP registry (active).
Recent checks of teas.co.uk
CheckedResultHandshake
1 hour agoHandshake completed379 ms
4 days agoCredentials required—
14 days agoHandshake completed327 ms
15 days agoHandshake completed528 ms
15 days agoHandshake completed395 ms
17 days agoHandshake completed368 ms
18 days agoHandshake completed347 ms
19 days agoHandshake completed329 ms
20 days agoHandshake completed595 ms
21 days agoHandshake completed802 ms
23 days agoHandshake completed500 ms
25 days agoHandshake completed367 ms
28 days agoHandshake completed358 ms

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

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