Remote MCP · Endpoint

SAMOS e-commerce MCP server

No. SAMOS e-commerce answered an MCP handshake 39 minutes ago.

UpLast checked 39 minutes ago

Server URL

https://samos-e.com/api/mcp

The last check completed an MCP handshake.

Registry name
com.samos-e/samos
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
307 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Track SAMOS parcels, estimate UK shipping, return and duty costs, and search SAMOS help.
Listing
From the official MCP registry (active).
Recent checks of SAMOS e-commerce
CheckedResultHandshake
39 minutes agoHandshake completed307 ms
3 days agoHandshake completed454 ms
13 days agoHandshake completed294 ms
13 days agoHandshake completed421 ms
15 days agoHandshake completed283 ms
16 days agoHandshake completed299 ms
17 days agoHandshake completed313 ms
18 days agoHandshake completed295 ms
18 days agoHandshake completed321 ms
20 days agoHandshake completed323 ms
22 days agoHandshake completed307 ms
25 days agoHandshake completed312 ms
27 days agoHandshake completed288 ms
29 days agoHandshake completed289 ms

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

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