Remote MCP · Endpoint

Tanatasa Beauty MCP server

No. Tanatasa Beauty answered an MCP handshake 34 minutes ago.

UpLast checked 34 minutes ago

Server URL

https://tanatasa.sg/mcp

The last check completed an MCP handshake.

Registry name
sg.tanatasa/tanatasa
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
485 ms
Tools exposed
17 tools
Uptime, last 30 days
91.7% from 12 checks
Described by its publisher as
Search Singapore skincare and beauty, build guest carts, and prepare buyer checkout links.
Listing
From the official MCP registry (active).
Recent checks of Tanatasa Beauty
CheckedResultHandshake
34 minutes agoHandshake completed485 ms
3 days agoHandshake completed393 ms
13 days agoHandshake completed377 ms
13 days agoHandshake completed770 ms
15 days agoFailed - the server returned an HTTP error—
16 days agoHandshake completed468 ms
17 days agoHandshake completed482 ms
18 days agoHandshake completed768 ms
18 days agoHandshake completed660 ms
20 days agoHandshake completed469 ms
22 days agoHandshake completed474 ms
25 days agoHandshake completed458 ms

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

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