Remote MCP · Endpoint

xyz.trusteed/mcp-gateway MCP server

Yes, as of 1 hour ago: the server returned an HTTP error.

DownLast checked 1 hour ago

Server URL

https://trusteed.xyz/demo-store/mcp

The last check failed: the server returned an HTTP error.

Registry name
xyz.trusteed/mcp-gateway
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
27 tools
Uptime, last 30 days
52.6% from 19 checks
Described by its publisher as
Agentic commerce gateway: discovery, search, checkout across Shopify/Woo/Odoo/PrestaShop.
Website
https://trusteed.xyz/
Repository
https://github.com/trusteed/mcpwebstore
Listing
From the official MCP registry (active).
Recent checks of xyz.trusteed/mcp-gateway
CheckedResultHandshake
1 hour agoFailed - the server returned an HTTP error—
10 hours agoFailed - the server returned an HTTP error—
1 day agoFailed - the server returned an HTTP error—
2 days agoFailed - the server returned an HTTP error—
4 days agoFailed - the server returned an HTTP error—
4 days agoFailed - the server returned an HTTP error—
5 days agoFailed - the server returned an HTTP error—
6 days agoFailed - the server returned an HTTP error—
8 days agoFailed - the server returned an HTTP error—
11 days agoHandshake completed324 ms
13 days agoHandshake completed590 ms
16 days agoHandshake completed329 ms
18 days agoHandshake completed343 ms
20 days agoHandshake completed343 ms
22 days agoHandshake completed326 ms
24 days agoHandshake completed339 ms
26 days agoHandshake completed317 ms
27 days agoHandshake completed325 ms
29 days agoHandshake completed328 ms

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

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 xyz.trusteed/mcp-gateway and makes no claim about it beyond what these checks measured.