Remote MCP · Endpoint

ecomdly MCP server

No. ecomdly answered an MCP handshake 7 hours ago.

UpLast checked 7 hours ago

Server URL

https://ecomdly.com/mcp

The last check completed an MCP handshake.

Registry name
com.ecomdly/ecomdly
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
661 ms
Tools exposed
15 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
E-commerce skills for AI agents: feeds, Google Shopping, GA4. Your private Brain when signed in.
Listing
From the official MCP registry (active).
Recent checks of ecomdly
CheckedResultHandshake
7 hours agoHandshake completed661 ms
4 days agoHandshake completed1.04 s
14 days agoHandshake completed583 ms
15 days agoHandshake completed685 ms
15 days agoHandshake completed619 ms
17 days agoHandshake completed962 ms
18 days agoHandshake completed631 ms
19 days agoHandshake completed501 ms
20 days agoHandshake completed775 ms
21 days agoHandshake completed524 ms
23 days agoHandshake completed787 ms
26 days agoHandshake completed584 ms
28 days agoHandshake completed506 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 ecomdly and makes no claim about it beyond what these checks measured.