Remote MCP · Endpoint

Ex2 catalogue MCP server

No. Ex2 catalogue answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://www.ex2.com/mcp

The last check completed an MCP handshake.

Registry name
com.ex2/catalogue
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
394 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Plans, prices and domain names of Ex2, web host from Québec: compare plans, check domains.
Listing
From the official MCP registry (active).
Recent checks of Ex2 catalogue
CheckedResultHandshake
1 hour agoHandshake completed394 ms
11 hours agoHandshake completed391 ms
1 day agoHandshake completed422 ms
2 days agoHandshake completed380 ms
4 days agoHandshake completed236 ms
7 days agoHandshake completed426 ms
9 days agoHandshake completed413 ms
12 days agoHandshake completed422 ms
14 days agoHandshake completed428 ms
16 days agoHandshake completed528 ms
18 days agoHandshake completed178 ms
20 days agoHandshake completed400 ms
22 days agoHandshake completed383 ms
23 days agoHandshake completed372 ms

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

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