Remote MCP · Endpoint

io.engineeringleaders/elc-toolkit MCP server

No. io.engineeringleaders/elc-toolkit answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://www.engineeringleaders.io/mcp

The last check completed an MCP handshake.

Registry name
io.engineeringleaders/elc-toolkit
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
680 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 19 checks
Described by its publisher as
Leadership-ratio benchmark, partnership ROI builder, community-launch readiness test. ELC data.
Listing
From the official MCP registry (active).
Recent checks of io.engineeringleaders/elc-toolkit
CheckedResultHandshake
1 hour agoHandshake completed680 ms
10 hours agoHandshake completed1.08 s
1 day agoHandshake completed999 ms
2 days agoHandshake completed593 ms
4 days agoHandshake completed639 ms
4 days agoHandshake completed985 ms
5 days agoHandshake completed562 ms
6 days agoHandshake completed660 ms
8 days agoHandshake completed1.36 s
11 days agoHandshake completed813 ms
13 days agoHandshake completed657 ms
16 days agoHandshake completed638 ms
18 days agoHandshake completed640 ms
20 days agoHandshake completed682 ms
22 days agoHandshake completed730 ms
24 days agoHandshake completed1.01 s
26 days agoHandshake completed526 ms
27 days agoHandshake completed794 ms
29 days agoHandshake completed722 ms

The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 31 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.

Listing data comes from the official MCP registry. Glide is not affiliated with io.engineeringleaders/elc-toolkit and makes no claim about it beyond what these checks measured.